open-index/open-npm huggingface dataset:
npm package: @landonschropp/generate
Description: A collection of generators for setting up JavaScript/TypeScript projects
Author: Landon Schropp
Latest version: 0.3.1

# JavaScript/TypeScript Generators

This is a collection of generators for setting up JavaScript/TypeScript projects. It's built with
[plop](https://plopjs.com/).

## TL/DR

```bash
pnpx @landonschropp/generate
pnpx @landonschropp/generate initialize
pnpx @landonschropp/generate prettier
pnpx @landonschropp/generate only-allow
pnpx @landonschropp/generate eslint
pnpx @landonschropp/generate typescript
pnpx @landonschropp/generate jest
pnpx @landonschropp/generate husky
```

## Generators

These are the generators included with this project:

- `initialize`: Creates a package.json file. This is similar to `pnpm init`, but includes
  different options.
- `prettier`: Installs and configures [Prettier](https://prettier.io/).
- `only-allow`: Configures [only-allow](https://github.com/pnpm/only-allow).
- `eslint`: Installs and configures [ESLint](https://eslint.org/).
- `typescript`: Installs and configures [TypeScript](https://typescriptlang.org/).
- `jest`: Installs and sets up [Jest](https://jestjs.io/).
- `husky`: Installs and configures [Husky](https://typicode.github.io/husky/) and
  [lint-staged](https://www.npmjs.com/package/lint-staged).

You can run a specific generator via [pnpx](https://pnpm.io/cli/dlx) like this:

```sh
pnpx @landonschropp/generate <generator>
```

You can run any of these generators independently, but if you're running more than one do so in the
order listed above.

## Development

Executing this project is as simple as calling `./src/index.js`, which is executable.

```sh
./src/index.js
```

## Deployment

First, set the version using `pnpm version <major|minor|patch>`. Then run `pnpm publish` to publish
the new version.
npm package: @landonschropp/promise-pipe
Description: A pipe function that works with promises instead of functors
Author: Lanodn Schropp
Latest version: 0.0.3
Deprecated: This package is no longer being maintained.

# promisePipe

`promisePipe` is a nifty little pipe library along the same lines as Ramda's
[`pipe`](http://ramdajs.com/docs/#pipe) method. Unlike `pipe`, `promisePipe` operates on promises
instead of functors.

## Installation

To install the package:

```
yarn add @landonschropp/promise-pipe
```

Alternative, you can use NPM:

```
npm install @landonschropp/promise-pipe
```

## Why Does This Exist?

Ramda's [`pipe`](http://ramdajs) allows you to combine multiple functions together in a
[point-free](https://en.wikipedia.org/wiki/Tacit_programming) style like this:

``` js
let averageHeight = R.pipe(
  R.map(R.prop('height')),
  R.median
);

averageHeight([
  { height: 7 },
  { height: 6 },
  { height: 5 }
]); // => 6
```

This style allows you to *compose* functions. It gives you the ability to think declaratively rather
than imperatively.

This works great for pure functions, but it starts to get a little tedious when you need to deal
with side effects and asynchronicity. Let's extend the example above to call an API operate on the
result using [Fluture](https://github.com/fluture-js/Fluture).

``` js
function fetchPokemon(id) {
  return Future((reject, resolve) => {
    fetch(`http://pokeapi.co/api/v2/pokemon/${ id }`)
      .then(response => response.json())
      .then(resolve, reject);
  });
}

let averagePokemonHeight = R.pipe(
  R.map(fetchPokemon),
  R.curry(Future.parallel)(Infinity),
  R.map(R.map(R.prop('height'))),
  R.map(R.median)
);

averagePokemonHeight([1, 4, 7]).fork(console.log, console.log);
// => 6
```

JavaScript already has a built in alternative to containers: promises! While promises are not
technically functors, they're still a really convenient way to pass data through applications. The
example above can be rewritten to use `promisePipe`:

``` js
function fetchPokemon(id) {
  return fetch(`http://pokeapi.co/api/v2/pokemon/${ id }`)
    .then(response => response.json());
}

let averagePokemonHeight = promisePipe(
  R.map(fetchPokemon),
  R.bind(Promise.all, Promise),
  R.map(R.prop('height')),
  R.median
);

averagePokemonHeight([1, 4, 7]).then(console.log);
// => 6
```

This allows you to build piped functions as you normally would. If the function returns a promise,
that promise's value is piped into the next function. If it doesn't, it's value is automatically
wrapped in a promise.

A `promisePipe` function is even cleaner when called inside of a `async` function.

``` js
async function averagePokemonHeight() {
  return await averagePokemonHeight([1, 4, 7]);
}
```
npm package: @landra_sistemas/cypress-parallel-runner
Description: A tool to run Cypress tests in parallel across multiple processes
Author: Landra Sistemas
Latest version: 0.0.14

# Cypress Parallel

🚀 A powerful tool to run Cypress tests in parallel across multiple processes, significantly reducing test execution time.

## Quick Start

### CLI Usage

# Run all tests with default settings

npx cypress-parallel-runner

# Run with 4 parallel processes

npx cypress-parallel-runner --concurrency 4

# Run specific test pattern

npx cypress-parallel-runner --spec "cypress/e2e/auth/\*_/_.cy.js"

# Run in Chrome browser with headed mode

npx cypress-parallel-runner --browser chrome --headed

# See what would run without executing

npx cypress-parallel-runner --dry-run

## CLI Options

| Option                         | Description                  | Default                |
| ------------------------------ | ---------------------------- | ---------------------- |
| \`-c, --concurrency <number>\` | Number of parallel processes | CPU cores              |
| \`-s, --spec <pattern>\`       | Spec file pattern to run     | From cypress.config.js |
| \`-e, --exclude <pattern>\`    | Pattern to exclude           | None                   |
| \`-b, --browser <browser>\`    | Browser to run tests in      | electron               |
| \`--config-file <file>\`       | Cypress config file          | cypress.config.js      |
| \`--headed\`                   | Run tests in headed mode     | false                  |
| \`--timeout <ms>\`             | Timeout per test file        | 300000                 |
| \`--cypress-command <cmd>\`    | Cypress command to use       | npx cypress            |
| \`--dry-run\`                  | Show files without running   | false                  |
npm package: @landrik/ui
Description: A collection of landrik's React UI Components Library
Author: Rutwaza Karege
Latest version: 0.1.3

# A bunch of React Components

A library of React components and patterns for Landrik Design System

## Including in your project

```bash
npm install @landrik/ui

```

```bash
@import { Button } from '@landrik/ui'

```


## Quick Start

```tsx
import { ThemeProvider, Button, TextField } from '@landrik/ui';

function App() {
  return (
    <ThemeProvider>
      <Button variant="primary">Click me</Button>
      <TextField label="Email" type="email" />
    </ThemeProvider>
  );
}
```

## Running Storybook

```bash
npm run storybook

```

## Documentation

Visit our [Storybook documentation](https://landrik.github.io/landrik-ui) for live examples.

## Adding new Components

Add new components by using the `create:component` npm task. It will prompt you for a name for the Component.
Please follow the Standard ReactNamingConventions, and name the component the singular form.

```
Good: TextField Button CheckBox

Bad: TextField text-input text input Buttons

```

A new directory will be created in the `./src/components` directory with the following files:

```
.
├── src
|   ├── Component
|   |   ├── Component.tsx
|   |   ├── Component.styled.ts
|   |   ├── Component.stories.tsx
|   |   ├── Component.test.ts
|   |   ├── Component.types.ts
|   |   ├── index.ts
```
## License

## Contributing

We welcome contributions! Please see our email us for details on contributing for:

- Setting up your development environment
- Creating new components
- Testing and code style
- Submitting pull requests

For advanced topics like testing in external applications and publishing, see our [Developer Guide](./DEVELOPER.md).

## License

The source files in this repository are made available under the terms of the MIT License.
npm package: @lands-pro/antd-react-components
Description: Lands Pro-后台开发常用的react组件
Author: 兰涛
Latest version: 1.0.3

## 介绍

本仓库是一个文档与组件集于一体的仓库，里面包含了一些常用的 react 组件，便于快速开发。
@lands-pro/antd-react-components 分别发布在了 npm 公有库和私有库，可自行决定安装的地址

## 相关文档

[组件文档](https://procomponents.lantao.work/)

[GitHub](https://github.com/Lands-1203/antd-react-components)

## Development

```bash
# install dependencies
$ pnpm install

# develop library by docs demo
$ pnpm start

# build library source code
$ pnpm run build

# build library source code in watch mode
$ pnpm run build:watch

# build docs
$ pnpm run docs:build

# check your project for potential problems
$ pnpm run doctor
```

## 效果演示

![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-55-13.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-59-28.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-58-24.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-57-46.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-57-10.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-56-49.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-56-35.png)
![alt text](https://static.lantao.work/assets/20240327/Snipaste_2024-03-27_11-55-31.png)

## LICENSE

MIT