open-index/open-npm huggingface dataset:
npm package: @pawcode/cli
Description: Paw Cli
Author: Paw Team
Latest version: 0.0.12

# PawCode CLI

PawCode CLI is a Command-Line Interface tool designed to streamline the creation and management of Paw projects, a lightweight frontend framework. With a simple set of commands, users can quickly set up a new Paw project, complete with essential files and configurations.

## Features

- **Easy Project Creation**: Quickly scaffold a new Paw project with a simple command.
- **Verbose Output**: Option to display additional messages during the execution for detailed feedback.
- **Automated Git Operations**: Automatically clones the necessary repository to set up the project structure.

## Installation

To install Paw CLI, you need to have Node.js and npm installed on your machine. Once these prerequisites are met, install Paw CLI globally using npm:

```bash
npm install -g @pawcode/cli
```

## Usage

### Creating a New Project

To create a new Paw project, use the `create` command followed by the name of your project:

```bash
paw create <projectName>
```

This will create a new directory named my-paw-project and set up the initial project structure.

### Verbose Mode

If you need more detailed output during the creation process, use the --verbose option:

```bash
paw create <projectName> --verbose
```

### Checking the Installed Version

To check the version of Paw CLI installed on your system, use:

```bash
paw --version
```

### Troubleshooting

If you encounter any issues:

- Ensure you have the latest version of Node.js and npm installed.
- Check if Git is installed, as it's required for the cloning process.
- For detailed error messages, use the `--verbose` option.

## Contributing

Contributions to Paw CLI are welcome. Please refer to the project's repository for contribution guidelines.

## License

Paw CLI is open-source software, released under the [MIT License](LICENSE).
npm package: @pawel-gnat/design-tokens
Description: Design tokens collection for Paweł Gnat Design System
Latest version: 0.3.0

# @pawel-gnat/design-tokens

Design Tokens are the smallest pieces of the design system — such as colors, typography, spacing, and more. They are used in place of hard-coded values to maintain a scalable and consistent visual system for UI development.

## Installation

```bash
npm install @pawel-gnat/design-tokens
```

## Usage

We provide tokens in three formats: CSS, JS and TS. You can import them in your project as needed.

### CSS

To use the CSS Custom Properties from our package, add the following import to the main CSS file or to the `<head>` of your HTML page:

```css
@import 'path_to_node_modules/@pawel-gnat/design-tokens/dist/css/tokens.css';
```

Or in JavaScript, if you use a bundler that supports CSS imports:

```js
import '@pawel-gnat/design-tokens/dist/css/tokens.css'
```

### JS/TS

```js
import { ButtonTextColor } from '@pawel-gnat/design-tokens'
```
npm package: @pawel-kuznik/esmify
Description: parse and handle import/export for browserify
Author: Matt DesLauriers
Latest version: 2.1.1

# esmify

A dead-simple tool to add `import` / `export` ES Module syntax to your [browserify](https://www.npmjs.com/package/browserify) builds.

The plugin makes the following changes to your bundler:

- Adds `.mjs` extension to module resolution (which take precedence over `.js` files)
- Resolves to `"module"` field in `package.json` when a `"browser"` field is not specified
- Transforms ES Module syntax (static `import` / `export` statements) into CommonJS

Use it with the `--plugin` or `-p` flags in browserify:

```js
browserify index.js -p esmify > bundle.js
```

Also works with [budo](https://www.npmjs.com/package/budo) and similar tools, for example:

```js
budo index.js --live -- -p esmify
```

Files that don't contain `import` / `export` syntax are ignored, as are dynamic import expressions. The plugin runs across your bundle (including `node_modules`) in order to support ESM-authored modules on npm.

## Install

Use [npm](https://npmjs.com/) to install.

```sh
npm install esmify --save-dev
```

Also can be used via API like so:

```js
browserify({
  plugin: [
    [ require('esmify'), { /* ... options ... */ } ]
  ]
});
```

## Usage

#### `plugin = esmify(bundler, opt = {})`

Returns a browswerify plugin function that operates on `bundler` with the given options:

- `mainFields` which describes the order of importance of fields in package.json resolution, defaults to `[ 'browser', 'module', 'main' ]`
- `nodeModules` (default `true`) to disable the transform on your `node_modules` tree, set this to `false`. This will speed up bundling but you may run into issues when trying to import ESM-published code from npm.
- `plainImports` (Experimental) this feature will map named imports *directly* to their CommonJS counterparts, without going through Babel's inter-op functions. This is generally needed for static analysis of `fs`, `path` and other tools like `glslify` in browserify. Defaults to `[ 'fs', 'path', 'glslify' ]`.

Under the hood, this uses Babel and `plugin-transform-modules-commonjs` to provide robust inter-op that handles a variety of use cases.

#### `require('esmify/resolve')(id, opts, cb)`

Resolve the given `id` using the module resolution algorithm from `esmify`, accepting `{ mainFields }` array to opts as well as other options passed to [resolve](https://www.npmjs.com/package/resolve) and [browser-resolve](https://www.npmjs.com/package/browser-resolve).

Works like so:

- If mainFields includes a `"browser"` field, use `browser-resolve`, otherwise use `resolve`
- Look for package.json fields in order of `mainFields`, the first field that exists will be used

## License

MIT, see [LICENSE.md](http://github.com/mattdesl/esmify/blob/master/LICENSE.md) for details.
npm package: @pawel-mat/randomid-generator
Description: This paskage generates a unique ID from random characters.
Latest version: 1.0.1

## id-generator

This paskage generates a unique ID from random characters.

## Install

npm install @pawel-mat/id-generator

or

yarn add @pawel-mat/id-generator

## Usage

Import the package :

import randomID from '@pawel-mat/id-generator';

or

const randomID = require('@pawel-mat/id-generator');

You can now define the length of generated ID through the method attribute.

example:

randomID(10);

console.log(randomID(10)); // cw5SuwIWzk
npm package: @pawel-up/data-mock
Description: No-dependency, ESM, in browser data generator
Author: Pawel Uchida-Psztyc
Latest version: 0.4.4

# Data mock

A data generation library that helps mocking different schemes.

## Usage

### Installation

```sh
npm install --save @pawel-up/data-mock
```

### Origin

This library started as a fork and a combination of two other great libraries: chance.js and faker.js. The basic data generation part is based on the two libraries. The difference is that this library is an ES module and it's goal is to mock well defined data structures.

### When to use?

Most likely you want to use any of the original libraries as they have a getter support and community. This can be a **not** in-drop replacement if you need support for ESM. Also this project aims to generate mocked schemas and not just random basic values.

## Development

```sh
git clone https://github.com/jarrodek/data-mock
cd data-mock
npm install
```

### Running the demo locally

```sh
npm start
```

### Running the tests

```sh
npm test
```