open-index/open-npm huggingface dataset:
npm package: @pulkitmittal/vue-simple-toast
Description: ## Project setup ``` yarn install ```
Latest version: 0.1.0

# vue-simple-toast

## Project setup
```
yarn install
```

### Compiles and hot-reloads for development
```
yarn serve
```

### Compiles and minifies for production
```
yarn build
```

### Run your unit tests
```
yarn test:unit
```

### Lints and fixes files
```
yarn lint
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
npm package: @pull-it-off/pull-it-off-basic
Description: This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.0.3.
Latest version: 0.0.2

# PullItOffBasic

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

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

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

## Running unit tests

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

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

## 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: @pull-it-off/pull-it-off-common
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.2.0.
Latest version: 0.0.4

# Common

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test common` 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: @pull-up/cli
Description: Collect scattered config files from your monorepo and generate them where your systems expect.
Author: Hoyeon Lee
Latest version: 0.0.3

# pull-up

Collect scattered config files from your monorepo and generate them where your systems expect.

## The Problem

Many tools require config files in specific locations:

- GitHub reads `CODEOWNERS` from `.github/CODEOWNERS`
- GitHub Actions workflows must live in `.github/workflows/`
- And more...

In a monorepo, each package has its own context. But these systems only look at root-level paths. You end up with a single massive file that every team has to edit, leading to merge conflicts and unclear ownership.

## The Solution

**pull-up** lets you keep config files next to the code they describe, then collects and generates them to the locations your systems expect.

```
packages/
  core/
    CODEOWNERS        # * @core-team
  web/
    CODEOWNERS        # * @frontend-team
  api/
    CODEOWNERS        # * @backend-team

↓ pullup sync

.github/
  CODEOWNERS          # All entries merged with correct paths
```

## Installation

```bash
npm install -D @pull-up/cli
# or
yarn add -D @pull-up/cli
# or
pnpm add -D @pull-up/cli
```

## Configuration

Create a config file in your project root:

```ts
import { defineConfig, codeownersJob } from "@pull-up/cli";

export default defineConfig(codeownersJob());
// or export default defineConfig([codeownersJob()]);
```

### Built-in Jobs

#### `codeownersJob`

Collects `CODEOWNERS` files from your monorepo and merges them into a single file.

```ts
codeownersJob({
  from: ["**/CODEOWNERS"], // default
  output: ".github/CODEOWNERS", // default
});
```

### Custom Jobs

You can define custom jobs using `defineJob`:

```ts
import { defineConfig, defineJob } from "@pull-up/cli";

const myJob = defineJob({
  name: "my-job",
  from: ["packages/*/config.json"],
  output: "merged-config.json",
  transform: (sources, context) => {
    // sources: array of { path, contents }
    // context: { root, outputPath, existingContents }
    return JSON.stringify(sources.map((s) => JSON.parse(s.contents)));
  },
});

export default defineConfig([myJob()]);
```

## Usage

### Sync

Generate files from scattered sources:

```bash
pullup sync
```

Preview changes without writing:

```bash
pullup sync --dry-run
```

### Check

Verify generated files are up to date (useful in CI):

```bash
pullup check
```

## CLI Options

| Option          | Description                         |
| --------------- | ----------------------------------- |
| `--root <path>` | Repository root path                |
| `--cwd <path>`  | Working directory                   |
| `--dry-run`     | Preview without writing (sync only) |