open-index/open-npm huggingface dataset:
npm package: @runly/bootstrap
Description: Bootstrap-styled react components to connect to Runly
Author: Runly LLC
Latest version: 0.2.0

# Runly.js React Bootstrap Integration

> Bootstrap-styled react components to connect to Runly

This package provides a number of [React](https://reactjs.org/) components styled with [Bootstrap](https://getbootstrap.com/) that can be used in your application.

[Learn how to use `@runly/bootstrap`](https://www.runly.io/docs/integration/js/react-bootstrap/) in your application.
npm package: @runly/core
Description: Core components to connect to Runly
Author: Runly LLC
Latest version: 0.5.33

<img src="logo.svg" width="350" alt="runly.js" />

> Easy multi-threaded batch processing for Node.js

![terminal](hello.svg)

## :rocket: Get Started

Install with npm:

```
$ npm install @runly/core
```

Create a job, `jobs/hello.js`:

```js
exports.getItems = ({ names }) => names;

const delay = ms => new Promise(resolve => setTimeout(resolve, ms));

exports.process = async (name, { greeting = "Hello" }) => {
	await delay(1500); // simulate some long-running work

	console.log(`${greeting}, ${name}`);
};
```

Add an `index.js` entry point for your app:

```js
const run = require("@runly/core");

run();
```

This gives you a CLI for your job for free and allows you to easily run your job multi-threaded without changing your code:

```
node index.js run hello --names Rick --names Morty --names Summer
```

This will reproduce the terminal animation above.

## :gear: How It Works

Job:
* config (input params)
  * from json file
* `getItems` async
* `process`
* `init`
* `finalize`

Job discovery:
* from jobs folder, show how to override
* show list command

## Examples

* csv parsing with async generator function
* sending emails

## Reference


## Publishing to your Runly Organization

1. In your `package.json` file, use the org name in the name of the package:
```json
{
  "name": "@orgname/pkgname"
}
```

2. Create a `.npmrc` file in package root, with the following contents, replacing `orgname` with the name of your org:
```
@orgname:registry=https://api.runly.io/npm/
```

3. On the [dashboard](https://www.runly.io/dashboard/), go to your [apps](https://www.runly.io/dashboard/account/apps) and create a new app named `npm` (or any name not in use), and copy the secret key.

4. Run the following command in a terminal:

```
npm login --registry=https://api.runly.io/npm/
```

Enter any value for the username and email and paste the secret key copied above for the password.

5. Run `npm publish` to publish your package to your Runly org.

## :ledger: Release Notes

See the [Releases](https://github.com/runlyio/corejs/releases).

## :memo: License

Licensed under the [MIT License](./LICENSE).
npm package: @runly/eslint-config
Description: Shareable ESLint configuration used in Runly client applications
Author: Runly LLC
Latest version: 4.3.0

# Runly Javascript Style Guide

> Shareable [ESLint](https://eslint.org/), [Prettier](https://prettier.io/), and [TypeScript](https://www.typescriptlang.org/) configuration used in Runly javascript applications.

## Usage

```
npm install @runly/eslint-config @runly/prettier-config prettier @runly/tsconfig typescript --save-dev
```

Add to your `.eslintrc.js`:

```js
module.exports = {
	extends: ["@runly"],
	parserOptions: {
		project: "tsconfig.json"
	},
	root: true
};
```

Add a `prettier` field to your `package.json` to use the shared prettier config:

```json
{
	"name": "my-cool-app",
	"version": "1.0.0",
	"prettier": "@runly/prettier-config"
}
```

Add a `tsconfig.json` to the root of your project with contents similar to the folowing:

```json
{
	"extends": "@runly/tsconfig",
	"include": ["src", "test"],
	"compilerOptions": {
		"outDir": "dist"
	}
}
```

## Editor Integration

You should be able to use your favorite editor's (\*cough\* [VS Code](https://code.visualstudio.com/)) [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) and/or [Prettier plugin](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) to easily format your code on save or with the [_Format_ command](https://code.visualstudio.com/docs/editor/codebasics#_formatting).

## Contributing

When adding rules or plugins, put them into the correct js file based on category (e.g. add react rules to `react.js`). Make sure to add a small comment explaining what the rule does (feel free to be as snarky as possible) along with a link to the rule documentation.

### Versioning

When making changes, be sure to [follow semantic versioning](http://semver.org/).

- Any new _error_ rules you add should be a major version bump.
- Any more restrictive changes to existing _error_ rules should be a major version bump.
- Any easing of restrictions to existing _error_ rules can be a minor version bump.
- Any new fixable _error_ rules can be a minor version bump.
- Any addition or changes to _warning_ rules should be a minor version bump.
- Any bug fixes should be a patch version bump.
- Anytime you realize you broke one of these rules, fixing it should be a patch version bump.
npm package: @runly/material
Description: Runly react components implemented with Material UI
Author: Runly LLC
Latest version: 0.1.5

# Runly.js React Material UI Integration

> Bootstrap-styled react components to connect to Runly

This package provides a number of [React](https://reactjs.org/) components implemented with [Material UI](https://material-ui.com/) that can be used in your application.

[Learn how to use `@runly/material`](https://www.runly.io/docs/integration/js/react-material/) in your application.
npm package: @runly/prettier-config
Description: Common prettier config for Runly javascript applications
Author: Runly LLC
Latest version: 4.3.1

# Runly Javascript Style Guide

> Shareable [ESLint](https://eslint.org/), [Prettier](https://prettier.io/), and [TypeScript](https://www.typescriptlang.org/) configuration used in Runly javascript applications.

## Usage

```
npm install @runly/eslint-config @runly/prettier-config prettier @runly/tsconfig typescript --save-dev
```

Add to your `.eslintrc.js`:

```js
module.exports = {
	extends: ["@runly"],
	parserOptions: {
		project: "tsconfig.json"
	},
	root: true
};
```

Add a `prettier` field to your `package.json` to use the shared prettier config:

```json
{
	"name": "my-cool-app",
	"version": "1.0.0",
	"prettier": "@runly/prettier-config"
}
```

Add a `tsconfig.json` to the root of your project with contents similar to the folowing:

```json
{
	"extends": "@runly/tsconfig",
	"include": ["src", "test"],
	"compilerOptions": {
		"outDir": "dist"
	}
}
```

## Editor Integration

You should be able to use your favorite editor's (\*cough\* [VS Code](https://code.visualstudio.com/)) [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) and/or [Prettier plugin](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) to easily format your code on save or with the [_Format_ command](https://code.visualstudio.com/docs/editor/codebasics#_formatting).

## Contributing

When adding rules or plugins, put them into the correct js file based on category (e.g. add react rules to `react.js`). Make sure to add a small comment explaining what the rule does (feel free to be as snarky as possible) along with a link to the rule documentation.

### Versioning

When making changes, be sure to [follow semantic versioning](http://semver.org/).

- Any new _error_ rules you add should be a major version bump.
- Any more restrictive changes to existing _error_ rules should be a major version bump.
- Any easing of restrictions to existing _error_ rules can be a minor version bump.
- Any new fixable _error_ rules can be a minor version bump.
- Any addition or changes to _warning_ rules should be a minor version bump.
- Any bug fixes should be a patch version bump.
- Anytime you realize you broke one of these rules, fixing it should be a patch version bump.
npm package: @runly/react-bootstrap
Description: Bootstrap-styled react components to connect to Runly
Author: Runly LLC
Latest version: 0.3.1

# Runly.js React Bootstrap Integration

> Bootstrap-styled react components to connect to Runly

This package provides a number of [React](https://reactjs.org/) components styled with [Bootstrap](https://getbootstrap.com/) that can be used in your application.

[Learn how to use `@runly/react-bootstrap`](https://www.runly.io/docs/integration/js/react-bootstrap/) in your application.
npm package: @runly/react-material
Description: Runly react components implemented with Material UI
Author: Runly LLC
Latest version: 0.1.3

# Runly.js React Material UI Integration

> Bootstrap-styled react components to connect to Runly

This package provides a number of [React](https://reactjs.org/) components implemented with [Material UI](https://material-ui.com/) that can be used in your application.

[Learn how to use `@runly/react-material`](https://www.runly.io/docs/integration/js/react-material/) in your application.
npm package: @runly/tsconfig
Description: Shareable TypeScript configuration used in Runly projects
Author: Runly LLC
Latest version: 4.3.1

# Runly Javascript Style Guide

> Shareable [ESLint](https://eslint.org/), [Prettier](https://prettier.io/), and [TypeScript](https://www.typescriptlang.org/) configuration used in Runly javascript applications.

## Usage

```
npm install @runly/eslint-config @runly/prettier-config prettier @runly/tsconfig typescript --save-dev
```

Add to your `.eslintrc.js`:

```js
module.exports = {
	extends: ["@runly"],
	parserOptions: {
		project: "tsconfig.json"
	},
	root: true
};
```

Add a `prettier` field to your `package.json` to use the shared prettier config:

```json
{
	"name": "my-cool-app",
	"version": "1.0.0",
	"prettier": "@runly/prettier-config"
}
```

Add a `tsconfig.json` to the root of your project with contents similar to the folowing:

```json
{
	"extends": "@runly/tsconfig",
	"include": ["src", "test"],
	"compilerOptions": {
		"outDir": "dist"
	}
}
```

## Editor Integration

You should be able to use your favorite editor's (\*cough\* [VS Code](https://code.visualstudio.com/)) [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) and/or [Prettier plugin](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) to easily format your code on save or with the [_Format_ command](https://code.visualstudio.com/docs/editor/codebasics#_formatting).

## Contributing

When adding rules or plugins, put them into the correct js file based on category (e.g. add react rules to `react.js`). Make sure to add a small comment explaining what the rule does (feel free to be as snarky as possible) along with a link to the rule documentation.

### Versioning

When making changes, be sure to [follow semantic versioning](http://semver.org/).

- Any new _error_ rules you add should be a major version bump.
- Any more restrictive changes to existing _error_ rules should be a major version bump.
- Any easing of restrictions to existing _error_ rules can be a minor version bump.
- Any new fixable _error_ rules can be a minor version bump.
- Any addition or changes to _warning_ rules should be a minor version bump.
- Any bug fixes should be a patch version bump.
- Anytime you realize you broke one of these rules, fixing it should be a patch version bump.
npm package: @runly/ui
Description: Core components to connect to Runly
Author: Runly LLC
Latest version: 0.1.5

# Runly.js Core

> Core components to connect to Runly

This package provides a number of [React Hooks](https://reactjs.org/docs/hooks-intro.html) that can be used to retrieve data from the Runly HTTP API.

[Learn how to use `@runly/ui`](https://www.runly.io/docs/integration/js/core/) in your application.