open-index/open-npm huggingface dataset:
npm package: @logo-software/doc-prsr
Description: This package is an extended version of Akveo doc-prsr, for Typescript. It contains interface, type, and other declarations for objects and methods.
Author: Akveo
Latest version: 2.2.46

This package is an extended version of Akveo doc-prsr, for Typescript. It contains interface, type, and other declarations for objects and methods.

### Usage: prsr [options]

### Options:

- -h, --help               output usage information
- -V, --version            output the version number
- -g, --generator <value>  Generator:
- -f, --framework <value>  Framework:
- -i, --input <value>      Path to input file:
- -o, --output <value>     Path to output file: 

### You have to specify:
- generator (can be 2 types: typedoc, docjs)
- framework (can be 2 types: angular, react)
- pathes to input and output file (output file will be created)
### For example: 

```
prsr -g typedoc -f angular -i input.json -o output.json
```
npm package: @logofx/aurelia2-mvvm-plugin
Description: An Aurelia 2 plugin.
Latest version: 0.1.1

# aurelia2-mvvm-plugin

This project is bootstrapped by [aurelia/new](https://github.com/aurelia/new).

## Start dev web server

    npm start

Note this plugin project comes with a dev-app. The above command starts the dev app in `dev-app/` folder. The plugin source code is in `src/` folder.

## Build the plugin in production modern

    npm run build

It builds plugin into `dist/index.js` file.

Note when you do `npm publish` or `npm pack` to prepare the plugin package, it automatically run the above build command by the `prepare` script defined in your package.json `"scripts"` section.

## Consume the plugin

If your plugin is published to npm or a private registry, just install the plugin package.json

    npm install aurelia2-mvvm-plugin

If you want to directly use plugin's git repo.

    npm install git@github.com:username/aurelia2-mvvm-plugin.git

or

    npm install https://some.git.server/username/aurelia2-mvvm-plugin.git

If you want to install from local folder, don't do "npm install ../local/aurelia2-mvvm-plugin/" as the folder's `node_modules/` will cause webpack to complain about duplicated dependency like "@aurelia/metadata".

In this plugin's folder, do

    npm pack

This will pack the plugin into aurelia2-mvvm-plugin
In an application project's main file.

```js
import * as myPlugin from 'aurelia2-mvvm-plugin';
Aurelia
  // Load all exports from the plugin
  .register(myPlugin)
  .app(MyApp)
  .start();
```

## Unit Tests

    npm run test

Run unit tests in watch mode.

    npm run test:watch


## Analyze webpack bundle

    npm run analyze
npm package: @logohub/core
Description: Core functionality for LogoHub - Open-source brand logo repository
Author: LogoHub Team
Latest version: 0.2.0

# @logohub/core

Core TypeScript client for LogoHub API.

## Install

```bash
npm install @logohub/core
```

## Usage

```typescript
import { LogoHubClient } from '@logohub/core';

const client = new LogoHubClient();

// Get all logos
const logos = await client.getLogos();

// Get specific logo
const logo = await client.getLogo('google');

// Generate logo URL
const url = client.getLogoUrl({
  id: 'google',
  format: 'png',
  size: 128,
  color: 'ff0000'
});
```

## API

- `getLogos(params)` - List logos with search/filter
- `getLogo(id)` - Get logo details  
- `getLogoUrl(config)` - Generate logo URL
- `downloadLogo(config)` - Download as blob
- `logoExists(id)` - Check if logo exists

## License

MIT - See [LICENSE](../../LICENSE) for details.

## Contributing

See [CONTRIBUTING.md](../../guidelines/CONTRIBUTING.md) for contribution guidelines.
npm package: @logohub/react
Description: React components and hooks for LogoHub - An open-source brand logo repository for front-end developers
Author: LogoHub Team
Latest version: 0.2.0

# @logohub/react

React components for LogoHub.

## Install

```bash
npm install @logohub/react @logohub/core
```

## Usage

### Logo Component

```jsx
import { Logo } from '@logohub/react';

<Logo name="google" />
<Logo name="microsoft" format="png" size={128} />
<Logo name="stripe" color="#ff0000" />
```

### LogoGrid Component

```jsx
import { LogoGrid } from '@logohub/react';

// Specific logos
<LogoGrid logos={['google', 'microsoft', 'stripe']} />

// Fetch all logos
<LogoGrid fetchAll />

// With search
<LogoGrid fetchAll search="tech" />
```

### Hooks

```jsx
import { useLogos, useLogo } from '@logohub/react';

const { data, loading, error } = useLogos();
const { data: logo } = useLogo('google');
```

## Props

### Logo
- `name` - Logo ID (required)
- `format` - 'svg' | 'png' | 'webp' (default: 'svg')
- `size` - Number (default: 64)
- `color` - Hex color without #

### LogoGrid
- `logos` - Array of logo IDs
- `fetchAll` - Fetch from API
- `search` - Search term
- `format`, `size`, `color` - Applied to all logos
npm package: @logojoy/lint
Description: ## Usage
Author: Yazan Medanat
Latest version: 0.0.0

# @logojoy/lint

## Usage

### For all JS environments
```
npm i --save-dev eslint @logojoy/eslint-config
```

In your local `.eslintrc`

```
{
  "extends": ["@logojoy"]
}
```

### For React environments
```
npm i --save-dev eslint babel-eslint @logojoy/eslint-config @logojoy/eslint-config-react
```

In your local `.eslintrc`

```
{
  "extends": ["@logojoy", "@logojoy/react"]
}
```

### For mocha environments
```
npm i --save-dev eslint @logojoy/eslint-config @logojoy/eslint-config-mocha
```

In your local `.eslintrc`

```
{
  "extends": ["@logojoy", "@logojoy/mocha"]
}
```

## Developing
- Once you download the repo to your machine, run `npm install` in the root folder, then run `npm run bootstrap` to install the dependencies for each package.

- When adding a new package to the `packages` folder, you will need to add `eslint` as a devDependency in order to run the tests successfully. You should also ensure that the new package's `package.json` has the following configuration added in order to be published as a public package:

```json
"publishConfig": {
    "access": "public"
}
```

## Publishing to npm
- Once your pull request has been approved and merged into the master branch, run `npm run publish` and select whether it will be a major, minor, or patch update.