open-index/open-npm huggingface dataset:
npm package: @k8soft/user-admin-sdk
Description: OpenAPI client for @k8soft/user-admin-sdk
Author: K8Soft
Latest version: 1.0.0

# AdminApi

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

## Code scaffolding

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

## Build

Run `ng build user-admin-sdk` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

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

## Running unit tests

Run `ng test user-admin-sdk` 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: @k8soft/user-client-sdk
Description: OpenAPI client for @k8soft/user-client-sdk
Author: K8Soft
Latest version: 1.0.0

# AdminApi

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

## Code scaffolding

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

## Build

Run `ng build user-client-sdk` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

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

## Running unit tests

Run `ng test user-client-sdk` 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: @k8stack/react-lib
Description: A template for creating React libraries w/ Rslib
Latest version: 1.1.0

# react.lib

This is a template for creating React libraries, based on [Rslib](https://lib.rsbuild.dev/).  
It includes a basic setup with TypeScript, ESLint, Prettier, and Vitest for testing.  
It also uses [semantic-release](https://semantic-release.gitbook.io/semantic-release/) for automated versioning and publishing.

## Requirements

- [nvm](https://www.freecodecamp.org/news/node-version-manager-nvm-install-guide/) (for managing Node.js versions)
- [corepack](https://github.com/nodejs/corepack) (for pnpm management)

## Getting Started

### Setting up GitHub Token (GH_TOKEN)

1. [GitHub Personal Access Token](https://github.com/settings/tokens)
2. Click `Generate new token`
3. Generate a new token with the following permissions:
   - Actions - read and write
   - Commit statuses - read and write
   - Contents - read and write
   - Deployments - read and write
   - Issues - read and write
4. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `GH_TOKEN

### Setting up NPM Token (NPM_TOKEN)

1. Go to [npmjs.com](https://www.npmjs.com/)
2. Navigate to your profile settings
3. Select "Access Tokens"
4. Create a new access token (Publish)
5. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `NPM_TOKEN`

### Scripts (used in dev workflow)

- `setup` - install dependencies and required node- and pnpm-version
- `dev` - start development server for the example app and watch for changes on the library and example app
- `lint` - run ESLint on the library
- `test` - run tests using Vitest

### Release Process

This template uses semantic-release for automated versioning and publishing.  
The release process is triggered automatically when changes are pushed to the main branch.

Commit messages should follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:

- `fix: ...` - patch release
- `feat: ...` - minor release
- `BREAKING CHANGE: ...` at the footer - major release
npm package: @k8stack/react-lib-ui
Description: A template for creating React UI-libraries w/ Rslib
Latest version: 1.1.2

# react.lib.ui

This is a template for creating React libraries, based on [Rslib](https://lib.rsbuild.dev/).  
It includes a basic setup with TypeScript, ESLint, Prettier, and Vitest for testing.  
It also uses [semantic-release](https://semantic-release.gitbook.io/semantic-release/) for automated versioning and publishing.

## Requirements

- [nvm](https://www.freecodecamp.org/news/node-version-manager-nvm-install-guide/) (for managing Node.js versions)
- [corepack](https://github.com/nodejs/corepack) (for pnpm management)

## Getting Started

### Setting up GitHub Token (GH_TOKEN)

1. [GitHub Personal Access Token](https://github.com/settings/tokens)
2. Click `Generate new token`
3. Generate a new token with the following permissions:
   - Actions - read and write
   - Commit statuses - read and write
   - Contents - read and write
   - Deployments - read and write
   - Issues - read and write
4. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `GH_TOKEN

### Setting up NPM Token (NPM_TOKEN)

1. Go to [npmjs.com](https://www.npmjs.com/)
2. Navigate to your profile settings
3. Select "Access Tokens"
4. Create a new access token (Publish)
5. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `NPM_TOKEN`

### Scripts (used in dev workflow)

- `setup` - install dependencies and required node- and pnpm-version
- `dev` - start development server for the example app and watch for changes on the library and example app
- `lint` - run ESLint on the library
- `test` - run tests using Vitest

### Release Process

This template uses semantic-release for automated versioning and publishing.  
The release process is triggered automatically when changes are pushed to the main branch.

Commit messages should follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:

- `fix: ...` - patch release
- `feat: ...` - minor release
- `BREAKING CHANGE: ...` at the footer - major release
npm package: @k8stack/react-rest-client
Description: This is a rest-client based on `@k8stack/react.lib`(for creating React libraries, based on [Rslib](https://lib.rsbuild.dev/)).
Latest version: 1.1.0

# react.lib.rest-client

This is a rest-client based on `@k8stack/react.lib`(for creating React libraries, based on [Rslib](https://lib.rsbuild.dev/)).

It provides a simple and efficient way to caching and managing REST API requests in your React applications (via TanStack-Query)
and checking incoming DTO (via Zod).

It includes:

- TypeScript,
- ESLint,
- Prettier,
- Vitest.

It also uses [semantic-release](https://semantic-release.gitbook.io/semantic-release/) for automated versioning and publishing.

## Requirements

- [nvm](https://www.freecodecamp.org/news/node-version-manager-nvm-install-guide/) (for managing Node.js versions)
- [corepack](https://github.com/nodejs/corepack) (for pnpm management)

## Getting Started

### Setting up GitHub Token (GH_TOKEN)

1. [GitHub Personal Access Token](https://github.com/settings/tokens)
2. Click `Generate new token`
3. Generate a new token with the following permissions:
   - Actions - read and write
   - Commit statuses - read and write
   - Contents - read and write
   - Deployments - read and write
   - Issues - read and write
4. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `GH_TOKEN

### Setting up NPM Token (NPM_TOKEN)

1. Go to [npmjs.com](https://www.npmjs.com/)
2. Navigate to your profile settings
3. Select "Access Tokens"
4. Create a new access token (Publish)
5. Copy the token and add it to your repository's secrets:
   - Go to your repository settings
   - Navigate to Secrets and variables > Actions
   - Create a new secret named `NPM_TOKEN`

### Scripts (used in dev workflow)

- `setup` - install dependencies and required node- and pnpm-version
- `dev` - start development server for the example app and watch for changes on the library and example app
- `lint` - run ESLint on the library
- `test` - run tests using Vitest
- ~~`publish`~~ - don't run this manually,
  it's handled by semantic-release (it publish the library to npm
  and GitHub Packages and creates a release on GitHub)

### Release Process

This template uses semantic-release for automated versioning and publishing.  
The release process is triggered automatically when changes are pushed to the main branch.

Commit messages should follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:

- `fix: ...` - patch release
- `feat: ...` - minor release
- `BREAKING CHANGE: ...` at the footer - major release