open-index/open-npm huggingface dataset:
npm package: @svsgestione/environment
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.0.0

# Environment

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 environment` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project environment`.
> Note: Don't forget to add `--project environment` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build environment` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build environment`, go to the dist folder `cd dist/environment` and run `npm publish`.

## Running unit tests

Run `ng test environment` 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: @svsgestione/login
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.1.0

# Login

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 login` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project login`.
> Note: Don't forget to add `--project login` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build login` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build login`, go to the dist folder `cd dist/login` and run `npm publish`.

## Running unit tests

Run `ng test login` 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: @svsgestione/models
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.1.0

# Models

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 models` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project models`.
> Note: Don't forget to add `--project models` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build models` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build models`, go to the dist folder `cd dist/models` and run `npm publish`.

## Running unit tests

Run `ng test models` 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: @svsgestione/version-app
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.0.0

# VersionApp

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 version-app` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project version-app`.
> Note: Don't forget to add `--project version-app` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build version-app` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build version-app`, go to the dist folder `cd dist/version-app` and run `npm publish`.

## Running unit tests

Run `ng test version-app` 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: @svsh/pocketbase
Description: Everything you need to build a Svelte library, powered by [`sv`](https://npmjs.com/package/sv).
Latest version: 0.0.46

# Svelte library

Everything you need to build a Svelte library, powered by [`sv`](https://npmjs.com/package/sv).

Read more about creating a library [in the docs](https://svelte.dev/docs/kit/packaging).

## Creating a project

If you're seeing this, you've probably already done this step. Congrats!

```bash
# create a new project in the current directory
npx sv create

# create a new project in my-app
npx sv create my-app
```

## Developing

Once you've created a project and installed dependencies with `npm install` (or `pnpm install` or `yarn`), start a development server:

```bash
npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open
```

Everything inside `src/lib` is part of your library, everything inside `src/routes` can be used as a showcase or preview app.

## Building

To build your library:

```bash
npm run package
```

To create a production version of your showcase app:

```bash
npm run build
```

You can preview the production build with `npm run preview`.

> To deploy your app, you may need to install an [adapter](https://svelte.dev/docs/kit/adapters) for your target environment.

## Publishing

Go into the `package.json` and give your package the desired name through the `"name"` option. Also consider adding a `"license"` field and point it to a `LICENSE` file which you can create from a template (one popular option is the [MIT license](https://opensource.org/license/mit/)).

To publish your library to [npm](https://www.npmjs.com):

```bash
npm publish
```