open-index/open-npm huggingface dataset:
npm package: @petrichorjs/config
Description: All the common config files for petrichor js.
Latest version: 1.0.2

# @petrichorjs/config

All the common config files for petrichor js.

## Setup

How to set up the config.

1. Install dependacies.

```shell
$ npm i -D typescript prettier prettier-plugin-jsdoc eslint @eslint/js @types/eslint__js  typescript-eslint
```

2. Prettier

```js
// .prettierrc.js
//@ts-check

import base from "@petrichorjs/config/prettier";

/**
 * @type {import("prettier").Config}
 * @see https://prettier.io/docs/en/configuration.html
 */
const config = {
    ...base,
};

export default config;
```

2. Eslint

```js
// eslint.config.mjs
// @ts-check

import base from "@petrichorjs/config/eslint";

export default [...base];
```

3. Tsconfig

```json
// tsconfig.json
{
    "extends": "@petrichorjs/config/tsconfig",
    "compilerOptions": {
        "rootDir": "./src",
        "outDir": "./dist"
    }
}
```
npm package: @petrichorjs/validator-vinejs
Description: Validate request bodies or query parameters with [vinejs](https://vinejs.dev/docs/introduction).
Latest version: 1.0.1

# @petrichorjs/validator-vinejs

Validate request bodies or query parameters with [vinejs](https://vinejs.dev/docs/introduction).

## Installation

This package requires that you have [vinejs](https://vinejs.dev/docs/introduction) installed.

```shell
$ npm i @vinejs/vine @petrichorjs/validator-vinejs
```

## Docs

To use this validator you just have to pass the `validator` function to either the body or query validator depending on what you want to validate. You also have to pass the vinejs schema to the validator function.

```ts
router
    .post("/users")
    .validate({
        body: validator(
            vine.object({
                id: vine.number().withoutDecimals(),
                email: vine.string().email(),
                profile: vine.object({
                    username: vine.string(),
                }),
            })
        ),
    })
    .handle(async ({ request, response }) => {
        const data = await request.json();
        data; // { id: number, email: string, profile: { username: string }}
    });
```
npm package: @petrick-ribeiro/lib-test
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 21.2.0.
Latest version: 1.4.1

# LibTest

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 21.2.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 lib-test
```

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/lib-test
   ```

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.