open-index/open-npm huggingface dataset:
npm package: @nazifcand/deneme-paket
Description: #### Avatar Stack
Latest version: 0.0.12

### COMPONENTS

#### Avatar Stack

| Props | Required | Default | Type                                                 |
| ----- | -------- | ------- | ---------------------------------------------------- |
| list  | True     | []      | `Array<{label: string,url?: string,image?: string}>` |
| max   | False    | null    | 5                                                    |
npm package: @nazimmertbilgi/angular-react-dates
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.0.2.
Latest version: 0.0.41

# AngularReactDates

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.0.2.

## Code scaffolding

Run `ng generate component component-name --project angular-react-dates` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular-react-dates`.
> Note: Don't forget to add `--project angular-react-dates` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build angular-react-dates` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build angular-react-dates`, go to the dist folder `cd dist/angular-react-dates` and run `npm publish`.

## Running unit tests

Run `ng test angular-react-dates` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @nazimmertbilgi/first-lib
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.0.2.
Latest version: 0.0.1

# FirstLib

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.0.2.

## Code scaffolding

Run `ng generate component component-name --project first-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project first-lib`.
> Note: Don't forget to add `--project first-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build first-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build first-lib`, go to the dist folder `cd dist/first-lib` and run `npm publish`.

## Running unit tests

Run `ng test first-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @nazmudin/ait-core-ui
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Latest version: 0.1.16

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:

```js
export default tseslint.config([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...

      // Remove tseslint.configs.recommended and replace with this
      ...tseslint.configs.recommendedTypeChecked,
      // Alternatively, use this for stricter rules
      ...tseslint.configs.strictTypeChecked,
      // Optionally, add this for stylistic rules
      ...tseslint.configs.stylisticTypeChecked,

      // Other configs...
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
])
```

You can also install [eslint-plugin-react-x](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-x) and [eslint-plugin-react-dom](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-dom) for React-specific lint rules:

```js
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'

export default tseslint.config([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...
      // Enable lint rules for React
      reactX.configs['recommended-typescript'],
      // Enable lint rules for React DOM
      reactDom.configs.recommended,
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
])
```
npm package: @nazmul_hasan/my-library
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.0.1

# MyLibrary

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.

## Code scaffolding

Run `ng generate component component-name --project my-library` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project my-library`.
> Note: Don't forget to add `--project my-library` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build my-library` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build my-library`, go to the dist folder `cd dist/my-library` and run `npm publish`.

## Running unit tests

Run `ng test my-library` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.