open-index/open-npm huggingface dataset:
npm package: @ngverse/icons-ad
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Ant Design icons
Latest version: 0.0.10

# @ngverse/icons-ad

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Ant Design icons

## install

`npm install @ngverse/icons-ad`

# use

```ts
// ts
import { ArrowDownOutlinedIcon } from '@ngverse/icons-ad'; 
// html
<arrow-down-outlined-icon></arrow-down-outlined-icon>
```
npm package: @ngverse/icons-bs
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Bootstrap Icons
Latest version: 0.0.4

# @ngverse/icons-absd

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Bootstrap Icons

## install

`npm install @ngverse/icons-bs`

# use

```ts
// ts
import { ZoomInIcon } from '@ngverse/icons-bs';
// html
<zoom-in-icon></zoom-in-icon>
```
npm package: @ngverse/icons-fa
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Font Awesome icons
Latest version: 0.0.8

# @ngverse/icons-fa

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Font Awesome icons

## install
`npm install @ngverse/icons-fa`

# use
```ts
   // ts
  import { ArrowRotateRightSolidIcon } from '@ngverse/icons-fa';
   ...
   // html
 <arrow-rotate-right-solid-icon></arrow-rotate-right-solid-icon>
 ```
npm package: @ngverse/icons-hi
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Hero icons
Latest version: 0.0.8

# @ngverse/icons-hi

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Hero icons

## install

`npm install @ngverse/icons-hi`

# use

```ts
   // ts
  import { ChevronDownOutlineIcon } from '@ngverse/icons-hi';
   // html
  <chevron-down-outline-icon></chevron-down-outline-icon>
```
npm package: @ngverse/icons-lu
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Lucide icons
Latest version: 0.0.12

# @ngverse/icons-lu

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Lucide icons

## install
`npm install @ngverse/icons-lu`

# use
```ts
   // ts
   import { ChevronRightIcon } from '@ngverse/icons-lu';
   ...
   // html
 <chevron-right-icon></chevron-right-icon>
 ```
npm package: @ngverse/icons-md
Description: this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Material Design icons
Latest version: 0.0.7

# @ngverse/icons-md

this package is part of [@ngverse/icons](https://ngverse.github.io/icons/) library. It provides Material Design icons

## install
`npm install @ngverse/icons-md`

# use
```ts
   // ts
   import { ChevronLeftIcon } from '@ngverse/icons-md';
   ...
   // html
 <chevron-left-icon></chevron-left-icon>
 ```
npm package: @ngverse/icons-ri
Description: this package is part of [@ngverse/icons](https://nginf.github.io/iconic/) library. It provides Remix Icons
Latest version: 0.0.3

# @ngverse/icons-ri

this package is part of [@ngverse/icons](https://nginf.github.io/iconic/) library. It provides Remix Icons

## install

`npm install @ngverse/icons-ri`

# use

```ts
   // ts
import { WindyIcon } from '@ngverse/icons-ri';
   ...
   // html
<windy-icon></windy-icon>
```
npm package: @ngverse/motion
Description: <p align="center">    <img src="https://github.com/ngverse/motion/blob/main/apps/docs/public/logo.png?raw=true" alt="Logo" width="200px" /> </p> `@ngverse/motion` is an Angular animations library, see more info on [link](https://motion-eosin.vercel.app)
Latest version: 1.0.0

# @ngverse/motion

<p align="center">
   <img src="https://github.com/ngverse/motion/blob/main/apps/docs/public/logo.png?raw=true" alt="Logo" width="200px" />
</p>
`@ngverse/motion` is an Angular animations library, see more info on [link](https://motion-eosin.vercel.app)
npm package: @ngverse/ui
Description: NgVerse is a collection of feature-rich Angular components, directives, and pipes. Unlike traditional libraries, it requires no installation—just copy and paste what you need into your project and fly 🚀.
Latest version: 4.1.0
Deprecated: This package is deprecated. Please use ngverse instead.

# NgVerse

NgVerse is a collection of feature-rich Angular components, directives, and pipes. Unlike traditional libraries, it requires no installation—just copy and paste what you need into your project and fly 🚀.

For more info visit the [docs](https://ui.ngverse.dev)

# Announcement

Thank you all for your feedback! The huge stable release is
coming—stay tuned!

[![npm](https://img.shields.io/npm/v/@ngverse/ui?label=npm&logo=npm)](https://www.npmjs.com/package/@ngverse/ui)

<p align="center">
   <img src="logo.png" alt="Logo" width="200px" />
</p>

## Creators

|                                                           |                                                                |
| --------------------------------------------------------- | -------------------------------------------------------------- |
| ![Luka Onikadze](https://github.com/lukonik.png?size=150) | ![Nikolay Lazarov](https://github.com/nikolaylaz.png?size=150) |
| **Luka Onikadze**                                         | **Nikolay Lazarov**                                            |
| [lukonik](https://github.com/lukonik)                     | [nikolaylaz](https://github.com/nikolaylaz)                    |
npm package: @ngvip/analytics
Description: This library is for gathering metrics. # MixPanel To use mixPanel you added the following into your AppModule under provider: [], its best practice to have dev analytics and prod analytics you can put those keys in environment.ts and environment.prod.
Latest version: 0.1.0

# Analytics

This library is for gathering metrics.
# MixPanel
To use mixPanel you added the following into your AppModule under provider: [],
its best practice to have dev analytics and prod analytics you can put those keys in
environment.ts and environment.prod.ts of your Angular application.
[Documentation](https://developer.mixpanel.com/docs/javascript#track-events)
>{provide: MixPanelConfig, useClass: MixPanelConfig, useValue: {
userId: AppData.getUser().id, apiToken: environment.mixpanel
}},
MixPanelService,

To override the config inside a given component you can do the follwing
>{provide: MixPanelConfig, useClass: MixPanelConfig, useValue: {
userId: AppData.getUser().id, apiToken: environment.mixpanel
}},
MixPanelService,

## Code scaffolding

Run `ng generate component component-name --project analytics` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project analytics`.
> Note: Don't forget to add `--project analytics` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build analytics` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build analytics`, go to the dist folder `cd dist/analytics` and run `npm publish`.

## Running unit tests

Run `ng test analytics` 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.
npm package: @ngvip/common-table
Description: | parameter     | required | default                           | type                       | description                         | |---------------|----------|-----------------------------------|----------------------------|------------------------------
Latest version: 0.6.0

### <vip-common-table> Component inputs

| parameter     | required | default                           | type                       | description                         |
|---------------|----------|-----------------------------------|----------------------------|-------------------------------------|
| `config`      | :heavy_check_mark: | N/A                               | CommonTableConfig          | link to common table config section |
| `rowData`     | :heavy_check_mark: | N/A                               | Array or Observable<Array> | provides data to the table          |
| `disabled`    | :x: | false                             | true / false               | disables the grid (view only)       |
| `gridLoading` | :x: | false                             | true / false               | sets the grid loading mask          |
| `gridError`   | :x: | "Error occurred retrieving data." | string                     | Error message to show               |



### CommonTableConfig 
| parameter     | required | default                           | type                       | description                         |
|---------------|----------|-----------------------------------|----------------------------|-------------------------------------|
| `columns`      | :heavy_check_mark: | N/A                      |  CommonTableColumn[]           | Array of (Link to common table column) |
| `disableSort`    | optional | false                             | true / false               | disables the grid (view only)       |
| `gridLoading` | optional | false                             | true / false               | sets the grid loading mask          |
| `gridError`   | optional | "Error occurred retrieving data." | string                     | Error message to show               |
npm package: @ngvip/service
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.1.0.
Latest version: 0.2.3-alpha.0

# Service

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test service` 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: @ngviz/diagram
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 14.2.0.
Latest version: 0.0.15

# Diagram

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test diagram` 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.
npm package: @ngwam/alert
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.17

# Alert

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build alert
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/alert
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/alert-manager
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.3

# AlertManager

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build alert-manager
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/alert-manager
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/components
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.
Latest version: 3.0.5

# Components

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build components
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/components
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/contact
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.10

# Contact

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build contact
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/contact
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/controls
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.22

# Controls

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build controls
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/controls
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/dexie
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.4

# Dexie

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build dexie
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/dexie
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/functions
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.5

# Functions

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build functions
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/functions
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/loading
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.7

# Loading

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build loading
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/loading
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/loading-status-manager
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.3

# LoadingStatusManager

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build loading-status-manager
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/loading-status-manager
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/menu
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.2.12

# Menu

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build menu
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/menu
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/menu-manager
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.5

# MenuManager

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build menu-manager
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/menu-manager
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/modals
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.13

# Modals

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build modals
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/modals
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/network
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.8

# Network

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build network
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/network
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @ngwam/network-status-reporter
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.
Latest version: 1.0.4

# NetworkStatusReporter

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.0.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build network-status-reporter
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/network-status-reporter
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.