open-index/open-npm huggingface dataset:
npm package: @rtlnederland/eslint-config-rtlnl-react
Description: ESLint base configuration file for @rtlnederland React applications
Author: rtl.nl
Latest version: 2.0.0

# eslint-config-rtlnl-react

https://www.npmjs.com/package/@rtlnederland/eslint-config-rtlnl-react

## Introduction

This is the base ESLint configuration file used at rtlnederland for React projects.

It is based on [Airbnb's config](https://www.npmjs.com/package/eslint-config-airbnb) and [Prettier](https://www.npmjs.com/package/prettier).

## Installation

### NPM

```
npm install --save-dev @rtlnederland/eslint-config-rtlnl-react
```

### Yarn

```
yarn add --exact --dev @rtlnederland/eslint-config-rtlnl-react
```

### Your `.eslintrc`

To add the rules to your `.eslintrc`, extend the file with the package in the following manner:

```
{
  "extends": ["@rtlnederland/rtlnl-react"]
}
```

Example:
```
.eslintrc.js
{
  "extends": [
    "@rtlnederland/rtlnl-react"
  ],
  "env": {
    "node": true,
    "jest": true
  }
}


.prettierrc.js
module.exports = {
  ...require('@rtlnederland/eslint-config-rtlnl-react/.prettierrc.js'),
  ...customParams
};


```
npm package: @rtlnl/conventional-changelog
Description: Commitizen adapter following the conventional-changelog format.
Author: rtl.nl
Latest version: 2.2.0

# rtlnl-conventional-changelog
Forked from cz-conventional-changelog
Status:
[![npm version](https://img.shields.io/npm/v/cz-conventional-changelog.svg?style=flat-square)](https://www.npmjs.org/package/cz-conventional-changelog)
[![npm downloads](https://img.shields.io/npm/dm/cz-conventional-changelog.svg?style=flat-square)](http://npm-stat.com/charts.html?package=cz-conventional-changelog&from=2015-08-01)
[![Build Status](https://img.shields.io/travis/commitizen/cz-conventional-changelog.svg?style=flat-square)](https://travis-ci.org/commitizen/cz-conventional-changelog)

Part of the [commitizen](https://github.com/commitizen/cz-cli) family. Prompts for [conventional changelog](https://github.com/conventional-changelog/conventional-changelog) standard.

## Configuration

### package.json

Like commitizen, you specify the configuration of cz-conventional-changelog through the package.json's `config.commitizen` key.

```json5
{
// ...  default values
    "config": {
        "commitizen": {      
            "path": "./node_modules/cz-conventional-changelog",
            "maxHeaderWidth": 100,
            "maxLineWidth": 100,
            "defaultType": "",
            "defaultScope": "",        
            "defaultSubject": "",
            "defaultBody": "",
            "defaultIssues": ""
        }
    }
// ...    
}
``` 
### Environment variables

The following environment varibles can be used to override any default configuration or package.json based configuration.

* CZ_TYPE = defaultType 
* CZ_SCOPE = defaultScope
* CZ_SUBJECT = defaultSubject
* CZ_BODY = defaultBody
* CZ_MAX_HEADER_WIDTH = maxHeaderWidth
* CZ_MAX_LINE_WIDTH = maxLineWidth

### Commitlint

If using the [commitlint](https://github.com/conventional-changelog/commitlint) js library, the "maxHeaderWidth" configuration property will default to the configuration of the "header-max-length" rule instead of the hard coded value of 100.  This can be ovewritten by setting the 'maxHeaderWidth' configuration in package.json or the CZ_MAX_HEADER_WIDTH environment variable.
npm package: @rtlnl/eslint-config-rtlnl-base
Description: ESLint base configuration file for @rtlnl
Author: rtl.nl
Latest version: 2.1.3

# eslint-config-rtlnl-base

https://www.npmjs.com/package/@rtlnl/eslint-config-rtlnl-base

## Introduction

This is the base ESLint configuration file used at rtlnederland.

It is based on [Airbnb's base config](https://www.npmjs.com/package/eslint-config-airbnb-base) and [Prettier](https://www.npmjs.com/package/prettier).

## Installation

### NPM

```
npm install --save-dev eslint@latest @rtlnl/eslint-config-rtlnl-base prettier
```

### Yarn

```
yarn add --exact --dev eslint@latest @rtlnl/eslint-config-rtlnl-base prettier
```

### Your `.eslintrc`

To add the rules to your `.eslintrc`, extend the file with the package in the following manner:

```
{
  "extends": ["@rtlnl/rtlnl-base"]
}
```

Example:
```
.eslintrc.js
{
  "extends": [
    "@rtlnl/rtlnl-base"
  ],
  "env": {
    "node": true,
    "jest": true
  }
}


.prettierrc.js
module.exports = {
  ...require('@rtlnl/eslint-config-rtlnl-base/.prettierrc.js'),
  ...customParams
};


```
npm package: @rtlnl/eslint-config-rtlnl-react
Description: ESLint base configuration file for @rtlnl React applications
Author: rtl.nl
Latest version: 1.1.1

# eslint-config-rtlnl-base

https://www.npmjs.com/package/@rtlnl/eslint-config-rtlnl-react

## Introduction

This is the base ESLint configuration file used at rtlnederland.

It is based on [Airbnb's config](https://www.npmjs.com/package/eslint-config-airbnb) and [Prettier](https://www.npmjs.com/package/prettier).

## Installation

### NPM

```
npm install --save-dev eslint@latest@rtlnl/eslint-config-rtlnl-react prettier
```

### Yarn

```
yarn add --exact --dev eslint@latest @rtlnl/eslint-config-rtlnl-react prettier
```

### Your `.eslintrc`

To add the rules to your `.eslintrc`, extend the file with the package in the following manner:

```
{
  "extends": ["@rtlnl/rtlnl-base"]
}
```

Example:
```
.eslintrc.js
{
  "extends": [
    "@rtlnl/rtlnl-react"
  ],
  "env": {
    "node": true,
    "jest": true
  }
}


.prettierrc.js
module.exports = {
  ...require('@rtlnl/eslint-config-rtlnl-base/.prettierrc.js'),
  ...customParams
};


```
npm package: @rtm/human-css-colors
Description: CSS classes for specifying colors in a human-friendly way
Author: rtm@gol.com
Latest version: 0.2.3

HUMAN CSS COLORS
======

`human-css-colors` provides a set of micro-attributes to easily specify and control CSS color styling.
It is a sister repo to `human-css-numbers` and `human-css-classes`
(and used by the latter).

It exposes a single custom property on designated elements named `--color` which you may use as you see fit.

Summary
-------

```
<span dark red color>
```

Colors are specified using the flexible HSL model.
This allows you to easily think of colors in terms of their hue, lightness, and saturation.
The standard hues are red, orange, yellow, lime, green, aquamarine, cyan, azure, blue, purple, magenta, and pink.
The hues can then be adjusted with additional micro-classes for saturation,
including `pure`, `x-bright`, `bright`, `dull`, `x-dull`, and `gray`,
and with additional micro-classes for lightness,
including `white`, `x-light`, `light`, `dark`, `x-dark`, and `black`.

In addition, any HTML color, such as `steelblue`, can be used as an attribute to specify the desired color.
To distinguish HTML colors from hues of the same name, add the attribute `html`, as in `html red`.

Global HSL values
-----------------

The actual application of a color to a specific element is triggered by the presence of the `color` attribute.
Without that, you are setting the hue, saturation, lightness, or alpha value for child elements.
For example, in conjunction with a micro-class/attribute library  such as `human-css-classes`,
the following will yield a red bordered div, with lighter red text:

```
<div hue red>
  <div thick border color>
    <div lighter text color>
```

The global HSL values may be modified for a particular element by the attributes
`purer` or `brighter`, `duller` or `grayer`, `whiter` or `lighter`, and `darker` or `blacker`,
or corresponding versions prefixed with `x-`.

usage
------------

    npm install --save-dev rtm@human-css-colors
    yarn add rtm@human-css-colors

Then, in some file that a CSS processor will process:

    @import "@rtm/human-css-colors";

### Caveat

This repo uses CSS custom properties, also known as CSS variables, in its implementation.
This excludes IE11 from consideration.
npm package: @rtm/human-css-numbers
Description: Human-friendly CSS attributes for numbers and lengths
Author: rtm@gol.com
Latest version: 0.2.1

Human CSS Numbers
======

Human CSS Numbers is a set of CSS micro-attributes for specifying numbers of lengths in human-friendly form.

Summary
-------

`human-css-numbers` is a set of attributes for specifying numbers of lengths,
designed for use in micro-class frameworks such as `human-css-classes`.

It exposes two CSS variables: `--number` and `--length` which you can use in your own CSS micro-attribute or micro-class rules.

It allows numbers to be specified using English words such as "two",
or Arabic numerals such as "2",
and percents as in "ten percent" or "half width",
and fractions such as "1/2".
and lengths as in "five rem".

### Caveat

`human-css-numbers` uses CSS custom properties, also known as CSS variables, in its implementation.
This excludes IE11 from consideration.

### Units and measures

Many micro-class frameworks suffer from a proliferation of classes such as `width-75`.
This limits the user to only the classes the designer provides.
In contrast, we provide individual micro-attributes for numbers, lengths, and units,
so we can write

```
<div 50% width>
<div two rem border>
<div three columns>
```

THe special keyword `size` indicates a ratio to a current size of 100%.
For instance, the following might specify a `flex-basis` of one-third the screen width:

```
<div flex>
  <div basis one third size>
```

All standard CSS units are provided as micro-attributes.
including lengths such as `px`, `em`, and `rem`.
Common numbers and percentages may also be used as micro-attributes,
in addition to built-in classes such as `1/2`.

Installation
------------

    npm install --save-dev @rtm/human-css-numbers

Then, in some file that a CSS pre-processor will process:

    @import "@rtm/human-css-numbers";
npm package: @rtn263net/cloudhub-electron-sdk
Description: cloudhub-electron-sdk
Author: CloudHub
Latest version: 3.7.11

### cloudhub-electron-sdk

<!-- ### 目录结构：

demo: 简单的功能实现，调试 sdk 用

sdk: sdk 源码

sdk 由 js 和 C++ 混合开发，在 npm 下载 cloudhub-electron-sdk 时，sdk/scripts 目录下的代码会自动下载依赖 C++ 部分的代码，并放在 addon 目录下，并与 scripts 目录同级

### 常用调试步骤：

- cd demo

- npm i

- npm run dev

- 调试已发布到npm上的 cloudhub-electron-sdk，直接在 demo 目录下下载对应版本的 sdk 即可

  ```shell
  
  npm install @rtn263net/cloudhub-electron-sdk@XXX
  
  ```
  
- 如需调试本地 sdk 源码：

  - 在 sdk 目录下执行 npm i, npm run build  打包源码生成 build 目录

  - 在 oss （sdkversion/cloudhub-x.x.x目录下）找到对应 C++ 已编译好的文件，将解压后的文件都放在 sdk/addon/Release 下

  - 在 demo/src/main.js 里将 @rtn263net/cloudhub-electron-sdk 的引入改为引入 sdk/build 

    ```javascript
    // require('../sdk').default 会寻找 package.json 里 main 对应的路径文件
    const rtcEngine = require('../sdk').default
    ``` -->

### 常见问题：

1.  下载 electron 太慢，解决：

   - 在终端执行 npm config edit 打开 npm 配置文件

   - 配置electron淘宝镜像：

     disturl=https://npm.taobao.org/dist

     electron_mirror=https://npm.taobao.org/mirrors/electron/

   - 安装依赖： npm i

2. window 环境打包安装包时失败，解决：注释掉下载 electron 的淘宝镜像
npm package: @rtn263net/cloudhub-liveroom-electron-sdk
Description: cloudhub liveroom electron sdk
Author: CloudHub
Latest version: 1.1.9

### @rtn263net/cloudhub-liveroom-electron-sdk

<!-- ### 目录结构：

demo: 简单的功能实现，调试 sdk 用

sdk: sdk 源码

sdk 由 js 和 C++ 混合开发，在 npm 下载 @rtn263net/cloudhub-liveroom-electron-sdk 时，sdk/scripts 目录下的代码会自动下载依赖 C++ 部分的代码，并放在 addon 目录下，并与 scripts 目录同级

### 常用调试步骤：

- cd demo-formal

- npm i

- npm run dev

- 调试已发布到npm上的 @rtn263net/cloudhub-liveroom-electron-sdk，直接在 demo 目录下下载对应版本的 sdk 即可

  ```shell
  
  npm install @rtn263net/cloudhub-liveroom-electron-sdk@XXX
  
  ```
  
- 如需调试本地 sdk 源码：

  - 在 sdk 目录下执行 npm i, npm run build  打包源码生成 build 目录

  - 在 oss （sdkversion/cloudhub-x.x.x目录下）找到对应 C++ 已编译好的文件，将解压后的文件都放在 sdk/addon/Release 下

  - 在 demo-formal/src/js/pusher/pusher.js和demo-formal/src/js/puller/puller.js 里将@rtn263net/cloudhub-liveroom-electron-sdk 的引入改为引入 sdk/build 
    ```javascript
    // require('../sdk').default 会寻找 package.json 里 main 对应的路径文件
    const RtsEngine = require("../../../sdk").default;
    ``` -->


### 常见问题：

1.  下载 electron 太慢，解决：

   - 在终端执行 npm config edit 打开 npm 配置文件

   - 配置electron淘宝镜像：

     disturl=https://npm.taobao.org/dist

     electron_mirror=https://npm.taobao.org/mirrors/electron/

   - 安装依赖： npm i

2. window 环境打包安装包时失败，解决：注释掉下载 electron 的淘宝镜像


3.更新内容
 1.0.8  修改了startScreenCaptureByDisplayId与startScreenCaptureByWindowId的传参个数
npm package: @rtns/core
Description: Reusable Technical Node Services (RTNS): Shared types, utilities, and middleware for building scalable microservices.
Author: UMP Team
Latest version: 1.0.0

# @ump/shared

Shared types, utilities, and middleware for UMP microservices platform.

## What's included

- **Types**: `DatabaseType`, `JwtPayload`, `ApiResponse`, common interfaces
- **Utils**: `ResponseUtil`, `JwtUtil`, `CacheService`, `logger`
- **Middleware**: `authenticate`, `authorize`, `departmentScope`, `selfOrAdmin`, security middleware
- **Database**: Multi-DB connection manager

## Installation

```bash
npm install @ump/shared
```

## Usage

```typescript
import { ResponseUtil, authenticate, DatabaseType } from '@ump/shared';

// In controllers
return ResponseUtil.success(res, data);

// In routes
router.get('/protected', authenticate, controller.method);

// In services
import { JwtPayload } from '@ump/shared';
```

## Publishing (maintainers only)

```bash
# Bump version
npm version patch   # or minor / major

# Build and publish to npm
npm publish

# Or publish to GitHub Packages
npm publish --registry=https://npm.pkg.github.com
```

## Development

```bash
# Build
npm run build

# Watch mode
npm run build:watch

# Link locally for development
npm link
cd ../auth-service && npm link @ump/shared
```

## Version History

- `1.0.0` — Initial release with all core utilities
npm package: @rtobon/app-config
Description: Cascading configuration for web application
Author: Oleg Orlov
Latest version: 1.3.1

# @eagle/app-config

> Cascading configuration for web application

## Install

```
npm install --save @eagle/app-config
```

## Repository

https://github.com/Graf009/app-config.git

## Usage

Loads configuration files from a `config` folder in your project root.

- `default` is always loaded if it exists
- If you specify `NODE_ENV=production` then both `production` and `default` are loaded, with `production` taking precedence.
- Any valid JS extension can be used for config - JS, json, etc.
  - To load another extension, register it before you require this module

```js
import config from '@eagle/app-config'
```

For working in browser add AppConfigPlugin in webpack config.

```js
import AppConfigPlugin from '@eagle/app-config/webpack'

var webpackConfig = {
  plugins: [
    new AppConfigPlugin(),
  ]
}
```
npm package: @rtobon/babel-preset-eagle
Description: Babel preset used by Eagle
Author: Oleg Orlov
Latest version: 1.1.0

# @eagle/babel-preset-eagle

This package includes the Babel preset used by Eagle

## Usage

If you want to use this Babel preset in a project, you can install it with following steps.

First, [install Babel](https://babeljs.io/docs/setup/).

Then create a file named `.babelrc` with following contents in the root folder of your project:

  ```js
  {
    "presets": ["eagle"]
  }
  ```
## Repository

https://github.com/Graf009/babel-preset-eagle.git
npm package: @rtobon/eslint-config-eagle
Description: Shared ESLint config
Author: Oleg Orlov
Latest version: 1.4.2

# @eagle/eslint-config-eagle

Shared ESLint config.

## Usage

Our default export contains all of our ESLint rules, including EcmaScript 6+
and React. It requires `eslint`, `eslint-plugin-react`, `eslint-plugin-jsx-a11y`, and `eslint-plugin-import`.

1. `npm install --save-dev @eagle/eslint-config-eagle eslint-plugin-react eslint-plugin-import eslint-plugin-jsx-a11y eslint`
2. add `"extends": "@eagle/eslint-config-eagle"` to your .eslintrc

## Repository

https://github.com/Graf009/eslint-config-eagle.git
npm package: @rtobon/glob-loader
Description: webpack loader to load files at once with glob
Author: Ryohei Ikegami
Latest version: 0.4.0

# @eagle/glob-loader

webpack loader to load files at once with glob

## Install

```
npm install --save-dev @eagle/glob-loader
```

## Repository

Change: export object instead of an array

https://github.com/Graf009/glob-loader.git

## Use

* Create a glob pattern file (example: `dir.pattern`)
* Write the pattern of the files that you want to require
* Require it with `glob-loader`

### `dir.pattern` file

Pattern is relative to the file directory.

```
./dir/**/*.js
```

### Require patterns

```js
var modules = require("glob-loader!./dir.pattern");
```

## TODO

* source map
npm package: @rtobon/jetpack
Description: Nifty convenience wrappers that speed up your daily work
Author: Oleg Orlov
Latest version: 1.1.0

# @eagle/jetpack

> Nifty convenience wrappers that speed up your daily work

## Install

```sh
npm install --save @eagle/jetpack
```

## Repository

https://github.com/Graf009/jetpack.git

## Pack

- `linkState` - A helper function to use LinkedStateMixin for ES6 React Components
- `d3` - for d3.js
- `ExecutionEnvironment` - detect available features
npm package: @rtobon/jetpack-dom
Description: Nifty convenience wrappers that speed up your daily work
Author: Oleg Orlov
Latest version: 2.0.1

# @eagle/jetpack-dom

> Nifty convenience wrappers that speed up your daily work

`ExecutionEnvironment` - detect available features

## Install

```sh
npm install --save @eagle/jetpack-dom
```

## Repository

https://github.com/Graf009/jetpack-dom.git
npm package: @rtobon/tango
Description: Toolkit for building redux/react applications
Author: Oleg Orlov
Latest version: 1.3.6

# @rtobon/tango

> Toolkit for building redux/react applications

## Install

```js
npm install --save @rtobon/tango react react-dom
```

## Repository

https://github.com/Graf009/tango.git

## Core Ideals

- Everything should be immutable
- Everything should work easily and be simple to understand
- Spend time building applications rather than wiring modules together

## Implementation

- Use ES6
- Central store is completely immutable via Immutable.js
  - And PropTypes include Immutable.js types by default
- Easy to understand objects instead of crazy functional composition
  - Before: `createStore(combineReducers(reducers), {}, compose(applyMiddleware(middleware), devtools))`
  - After: `createStore({middleware: middleware, reducers: reducers, initialState: {}})`
- Bundle groups of middleware, enhancers, and reducers together as "plugins"
  - One line of code to add a router and etc. to your project
  - High quality ecosystem of modules guaranteed to work well with eachother
- Namespaced/nested actions and reducers
  - `todos.create` as an action corresponds to a `todos.create` reducer and `todos` in the store
- Default enhancers
  - redux-batched-subscribe
- Default middleware
  - redux-thunk
  - devtools
- Dead simple Component API
  - Use ES6 classes
  - Bring back sane behavior
    - Bind component functions scope to class (like old react)
  - Never write mapDispatchToProps or mapStateToProps

## Documentation

**Now**, check out the [documentation](https://github.com/Graf009/tango/tree/master/docs) to get started!
npm package: @rtobon/tango-data-view
Description: Lightweight data view abstraction for managing fetching/loaded/errored states for remote data
Author: Oleg Orlov
Latest version: 1.2.0

# @eagle/tango-data-view

Simple component for managing asynchronous data dependency states. If you have a view with 3 base states: fetching, loaded, and errored - this will help you clean up a lot of boilerplate.
Works out of the box with `@eagle/rumba` for doing API stuff.

## Install

```js
npm install --save @eagle/tango-data-view
```

## Repository

https://github.com/Graf009/tango-data-view.git

## API

You can define three functions:

- `resolveData`
  - Defaults to doing nothing
  - Triggered on mount/update when any `storeProps` (what you give to tango's connect function) are not fulfilled
  - Responsible for dispatching any actions to fetch data
- `renderData`
  - Defaults to displaying nothing
  - Triggered when all storeProps are resolved
  - Receives a data object as an argument
  - Responsible for rendering the data
- `renderLoader`
  - Defaults to displaying nothing
  - Triggered when all storeProps are not resolved
  - Responsible for rendering a loader
- `renderErrors`
  - Defaults to displaying nothing
  - Triggered when any storeProp value has an `error` attribute
  - Receives an errors Map as an argument
    - Key is the storeProp
    - Value is the error object
  - Responsible for rendering any errors that happened while fetching data

## Example

```js
import React from 'react'
import { PropTypes, connect } from '@eagle/tango'
import DataComponent from '@eagle/tango-data-view'
import actions from 'core/actions'

@connect({
  users: 'subsets.users'
})
export default class UserList extends DataComponent {
  static propTypes = {
    users: PropTypes.iterable
  }

  resolveData() {
    actions.api.users.find({ subset: 'users' })
  }

  renderData({ users }) {
    return (
      <div>
        <div>Users</div>
        {
          users.map(user =>
            <Media key={user.get('id')} align="center" img={user.get('image')}>
              <Heading level={3}>{user.get('name')}</Heading>
            </Media>
          )
        }
      </div>
    )
  }

  renderErrors(errors) {
    return (
      <div>
        <div>Users</div>
        <div>Failed to Load!</div>
        {
          errors.map((err, field) =>
            <Media key={field} align="center">
              <Heading level={3}>{field}</Heading>
              <Text>{err.message}</Text>
            </Media>
          ).toArray()
        }
      </div>
    )
  }
}
```
npm package: @rtobon/tango-router
Description: Dead simple router for @rtobon/tango
Author: Oleg Orlov
Latest version: 1.4.1

# @eagle/tango-router

> Dead simple router for @rtobon/tango

Wraps react-router + react-router-redux and provides the simplest API possible. Built for @eagle/tango, but will work in any redux application.

## Install

```
npm install --save @rtobon/tango-router
```

## Repository

https://github.com/rtobon/tango-router.git

## Get Started

- Import in the module
- Add it to your store's plugins
- Router state is now under `router` in your store

### Example

```js
import { createStore } from '@rtobon/tango'
import * as router from '@rtobon/tango-router'

// you get the point
let store = createStore({
  plugins: [ router ]
})
```

## API

- history
- actions
- reducers
- middleware
- hook

### Components

These are all re-exported from react-router, the behavior is exactly the same. See the [react-router documentation](https://github.com/reactjs/react-router/tree/master/docs) if you haven't used these before.

- Router
- Route
- Link
- Redirect
- IndexRoute
- IndexLink
- IndexRedirect

#### Auth

   handling authentication

##### Props

- `store` - Redux store
- `options` - Options Object

##### Options Object Keys

- `authSelector(state): authData` \(*Function*): A state selector for the auth data.
- `redirectAction` \(*Function*): action for redirecting the user.
- `[failureRedirectPath]` \(*String*): Optional path to redirect the browser to on a failed check. Defaults to `/login`
- `[predicate(authData): Bool]` \(*Function*): Optional function to be passed the result of the `authSelector` param.
If it evaluates to false the browser will be redirected to `failureRedirectPath`.
- `[allowRedirectBack]` \(*Bool*): Optional bool on whether to pass a `redirect` query parameter to the `failureRedirectPath`