open-index/open-npm huggingface dataset:
npm package: @findnlink/neuro-ui
Description: Findnlink design system
Latest version: 1.0.41

# Neuro-UI

## Project on Findnlink (soon public roadmap/kanban): [Neuro UI](https://www.findnlink.com/de/project/Neuro_UI)

Gifs

UI kit and component builder made with react

Build with: react, vite, scss, typescript

Live component props generator.
Value/ props -> copy code.
npm package: @findoctave/eslint-config
Description: Base ESLint configuration for JavaScript/TypeScript projects
Author: Kyle Ross
Latest version: 1.2.1

# @findoctave/eslint-config
Base ESLint configuration for JavaScript/TypeScript projects. This config is ESM only and only supports ESLint 9+ (flat file config).

> [!NOTE]
> If you are using TypeScript, you should also use the `@findoctave/eslint-config-typescript` package in addition to this package.

## Installation

```bash
npm install -D @findoctave/eslint-config
pnpm add -D @findoctave/eslint-config
```

## Usage
This config provides multiple exports to support different use cases.

### For Node.js or general JS/TS projects
```javascript
import { defineConfig } from 'eslint/config';
import octaveConfig from '@findoctave/eslint-config';

export default defineConfig([
  ...octaveConfig,
  // your other configs...
]);
```

### For browser projects
```javascript
import { defineConfig } from 'eslint/config';
import octaveBrowserConfig from '@findoctave/eslint-config/browser';

export default defineConfig([
  ...octaveBrowserConfig,
  // your other configs...
]);
```

### JSON linting support
```javascript
import { defineConfig } from 'eslint/config';
import octaveConfig from '@findoctave/eslint-config';
import octaveJsonConfig from '@findoctave/eslint-config/json';

export default defineConfig([
  ...octaveConfig,
  ...octaveJsonConfig,
  // your other configs...
]);
```

## Features

- Modern JavaScript/TypeScript support
- Sensible defaults for code quality
- Strict error handling
- Consistent code style
- No unnecessary dependencies
- Browser and Node.js code linting support
- Optional JSON linting support

## License

MIT
npm package: @findoctave/eslint-config-mdx
Description: ESLint configuration for MDX projects
Author: Kyle Ross
Latest version: 1.1.1

# @findoctave/eslint-config-mdx
ESLint configuration for MDX files. This config is ESM only and only supports ESLint 9+ (flat file config).

> [!NOTE]
> It is recommended to use this alongside `@findoctave/eslint-config`.

## Installation

```bash
npm install -D @findoctave/eslint-config-mdx
pnpm add -D @findoctave/eslint-config-mdx
```

## Usage
This package includes multiple exports to support different use cases. **Only use one of these exports at a time.**

### Base MDX linting

```javascript
import octaveMdxConfig from '@findoctave/eslint-config-mdx';

export default [
  ...octaveMdxConfig,
  // your other configs...
];
```

### MDX code block linting
This export will also lint MDX code blocks. It includes the base MDX linting rules as well.

```javascript
import { codeBlocks as octaveMdxCodeBlocksConfig } from '@findoctave/eslint-config-mdx';

export default [
  ...octaveMdxCodeBlocksConfig,
  // your other configs...
];
```

## Features

- MDX-specific linting rules
- JSX support for MDX files
- Markdown and JavaScript linting

## License

MIT
npm package: @findoctave/eslint-config-react
Description: ESLint configuration for React projects
Author: Kyle Ross
Latest version: 1.2.1

# @findoctave/eslint-config-react

ESLint configuration for React projects. This config is ESM only and only supports ESLint 9+ (flat file config).

> [!NOTE]
> It is recommended to use this alongside `@findoctave/eslint-config`.

## Installation

```bash
npm install -D @findoctave/eslint-config-react
pnpm add -D @findoctave/eslint-config-react
```

## Usage

```javascript
import reactConfig from '@findoctave/eslint-config-react';

export default [
  ...reactConfig,
  // your other configs...
];
```

## Features

- React-specific linting rules
- React Hooks rules
- JSX accessibility rules
- TypeScript-friendly (prop-types disabled)

## License

MIT
npm package: @findoctave/eslint-config-storybook
Description: ESLint configuration for Storybook projects
Author: Kyle Ross
Latest version: 1.1.1

# @findoctave/eslint-config-storybook

ESLint configuration for Storybook projects. This config is ESM only and only supports ESLint 9+ (flat file config).

>  [!NOTE]
> It is recommended to use this alongside `@findoctave/eslint-config`.

## Installation

```bash
npm install -D @findoctave/eslint-config-storybook
pnpm add -D @findoctave/eslint-config-storybook
```

## Usage

```javascript
import storybookConfig from '@findoctave/eslint-config-storybook';

export default [
  ...storybookConfig,
  // your other configs...
];
```

## Features

- Storybook-specific linting rules
- Story file validation
- Best practices for Storybook development

## License

MIT
npm package: @findoctave/eslint-config-typescript
Description: ESLint configuration for TypeScript projects
Author: Kyle Ross
Latest version: 1.1.1

# @findoctave/eslint-config-typescript

ESLint configuration for TypeScript projects. This config is ESM only and only supports ESLint 9+ (flat file config).

> [!NOTE]
> It is recommended to use this alongside `@findoctave/eslint-config`.

## Installation

```bash
npm install -D @findoctave/eslint-config-typescript
pnpm add -D @findoctave/eslint-config-typescript
```

## Usage

### Basic Usage

```javascript
import octaveTypescriptConfig from '@findoctave/eslint-config-typescript';

export default [
  ...octaveTypescriptConfig,
  // your other configs...
];
```

### Customize Options

Since various settings can be set to ensure your TypeScript environment is appropriately linted, this package exports a `configure` function that allows adjusting the settings.

```ts
import { configure as configureTypeScriptConfig } from '@findoctave/eslint-config-typescript';

export default [
  ...configureTypeScriptConfig({
    // options to pass to typescript-eslint parser
  }, {
    // options to pass to import-x's resolver
  }),
  // your other configs...
];
```

## Features

- TypeScript-specific linting rules
- Strict type checking
- Modern TypeScript best practices
- Disables conflicting JavaScript rules

## License

MIT
npm package: @findoctave/eslint-config-vitest
Description: ESLint configuration for Vitest projects
Author: Kyle Ross
Latest version: 1.1.1

# @findoctave/eslint-config-vitest

ESLint configuration for Vitest projects. This config is ESM only and only supports ESLint 9+ (flat file config).

> [!NOTE]
> It is recommended to use this alongside `@findoctave/eslint-config`.

## Installation

```bash
npm install -D @findoctave/eslint-config-vitest
pnpm add -D @findoctave/eslint-config-vitest
```

## Usage

### Basic Usage

```javascript
import vitestConfig from '@findoctave/eslint-config-vitest';

export default [
  ...vitestConfig,
  // your other configs...
];
```

### Without Vitest Globals

By default, Vitest globals are included in the config. If you do not use the globals, you can use the `base` export instead.

```ts
import { base as vitestBaseConfig } from '@findoctave/eslint-config-vitest';

export default [
  ..vitestBaseConfig,
  // your other configs...
];
```

## Features

- Vitest-specific linting rules
- Testing globals configuration
- Best practices for test writing
- Validates test structure and expectations

## License

MIT
npm package: @findplay/find-play-registration
Description: Webcomponent find-play-registration following open-wc recommendations
Author: find-play-registration
Latest version: 0.0.1-beta.7

# \<find-play-registration>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

## Installation

```bash
npm i find-play-registration
```

## Usage

```html
<script type="module">
  import 'find-play-registration/find-play-registration.js';
</script>

<find-play-registration></find-play-registration>
```

## Linting with ESLint, Prettier, and Types

To scan the project for linting errors, run

```bash
npm run lint
```

You can lint with ESLint and Prettier individually as well

```bash
npm run lint:eslint
```

```bash
npm run lint:prettier
```

To automatically fix many linting errors, run

```bash
npm run format
```

You can format using ESLint and Prettier individually as well

```bash
npm run format:eslint
```

```bash
npm run format:prettier
```

## Testing with Karma

To run the suite of karma tests, run

```bash
npm run test
```

To run the tests in watch mode (for <abbr title="test driven development">TDD</abbr>, for example), run

```bash
npm run test:watch
```

## Demoing with Storybook

To run a local instance of Storybook for your component, run

```bash
npm run storybook
```

To build a production version of Storybook, run

```bash
npm run storybook:build
```

## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `es-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @findplay/findplay-react-scripts
Description: Fork of facebookincubator/create-react-app@3.1.1 with some additional features.
Latest version: 3.1.10

# findplay-scripts

This is a fork of the
[react-scripts](https://github.com/facebook/create-react-app/tree/master/packages/react-scripts)
package from the
[facebook/create-react-app](https://github.com/facebook/create-react-app)
monorepo.
You can refer to its documentation:

- [Getting Started](https://facebook.github.io/create-react-app/docs/getting-started) – How to create a new app.
- [User Guide](https://facebook.github.io/create-react-app/) – How to develop apps bootstrapped with Create React App.

This package is published as
[@findplay/findplay-react-scripts](https://www.npmjs.com/package/@findplay/findplay-react-scripts)
in NPM.

See the `description` field in [package.json](package.json) to see
which version of `react-scripts` this fork is built from.

## Differences to `react-scripts`

- Use [CSS Modules](https://github.com/css-modules/css-modules) on every css file
- Use [postcss-preset-env](https://github.com/csstools/postcss-preset-env)
- Use [postcss-import](https://github.com/postcss/postcss-import)
- Use [postcss-apply](https://github.com/pascalduez/postcss-apply)
- Build an UMD module in production mode to support server side rendering

## Development

### Setup

To update the fork to use a new version of the upstream repository:

1. If you haven't already, configure the upstream repository as a remote:

   ```
   git remote add upstream https://github.com/facebookincubator/create-react-app
   ```

1. [Sync the fork](https://help.github.com/articles/syncing-a-fork/)
   to a branch, making sure you merge from a specific version/tag that
   you want to base your changes on

   ```
   git fetch upstream
   git checkout master
   git checkout -b update-from-upstream
   git merge <tag_to_be_merged_here_eg_v1.1.2>
   ```

1. Make your changes, test them (see below), make a PR, release

### Making changes and testing

To test your local changes, link the local repository to the application:

1. In the `create-react-app/packages/react-scripts` directory, install
   dependencies and make a link of the package:

   ```
   yarn install # ignore the yarn.lock file
   yarn link
   ```

   **NOTE:** if other packages have changed too, you might need to run
   `yarn install # ignore the yarn.lock file` on the root folder too.

1. In the application remove the old `sharetribe-scripts` package and
   use the linked version ([read more](https://yarnpkg.com/lang/en/docs/cli/link/)):

   ```
   yarn remove sharetribe-scripts
   yarn link sharetribe-scripts
   ```

1. Now you changes to the fork are usable as a symlicked dependency in
   the application

### Publishing

1. Make sure you have updated the version also in the `description`
   field in [package.json](package.json). Try to sync the package
   version with the original package, if possible.

1. Publish to NPM:

   ```
   npm login
   # Check credentials from password manager
   npm publish
   ```

1. Tag the commit with released version: `sharetribe-scripts@x.x`
npm package: @findq/gulp-jcson-merge
Description: Merge JSON and CSON into a singular JSON file
Author: FindQ UF
Latest version: 0.0.2
Deprecated: @findq/gulp-jcson-merge has been deprecated since it's no longer maintained

# gulp-jcson-merge

> Merge JSON and CSON to a singular JSON file.

_All options are passed to [CSON](https://github.com/bevry/cson) any output issues should be reported on the CSON [issue tracker](https://github.com/bevry/cson/issues)._

## Install

#### Using npm:

```bash
$ npm install @findq/gulp-jcson-merge
```

#### Using yarn:

```bash
$ yarn add @findq/gulp-jcson-merge
```

## Usage

#### Indentation: none (default)
```javascript
var gulp = require("gulp");
var jcsonMerge = require("@findq/gulp-jcson-merge");

gulp.task("jcson-merge", () => {
  gulp.src([ "./input/**.json", "./input/**.cson" ])
      .pipe(jcsonMerge())
      .pipe(gulp.dest("./output/"));
});
```

#### Indentation: 2 spaces
```javascript
var gulp = require("gulp");
var jcsonMerge = require("@findq/gulp-jcson-merge");

gulp.task("jcson-merge", () => {
  gulp.src([ "./input/**.json", "./input/**.cson" ])
      .pipe(jcsonMerge({
        indent: 2,
      }))
      .pipe(gulp.dest("./output/"));
});
```

#### Indentation: tab
```javascript
var gulp = require("gulp");
var jcsonMerge = require("@findq/gulp-jcson-merge");

gulp.task("jcson-merge", () => {
  gulp.src([ "./input/**.json", "./input/**.cson" ])
      .pipe(jcsonMerge({
        indent: "\t"
      }))
      .pipe(gulp.dest("./output/"));
});
```

## LICENSE
MIT &copy; [FindQ](https://findquf.com) and [contributors](https://github.com/FindQ/gulp-jcson-merge/graphs/contributors)
npm package: @findqin/auto-view-plugin-check
Description: 查看打点数据的 [auto-view](https://github.com/find-qin/auto-view) 插件，支持检测当前上报 mv/mc
Latest version: 0.1.0

# auto-view-plugin-check   
查看打点数据的 [auto-view](https://github.com/find-qin/auto-view) 插件，支持检测当前上报 mv/mc

### notice  
- 插件使用 ES2015 语法，包含 Map 使用，如果需要 ES5 环境运行，请自行做好 Polyfill
- 插件会改变文档流中的元素样式，插入元素节点

### Usage
``` javascript

import autoView from '@findqin/auto-view'
import autoViewPluginCheck from '@findqin/auto-view-plugin'

autoView({
    onElemView: (vid, vdata) => {},
    onElemClick: (vid, vdata) => {},
    plugins: [
        autoViewPluginCheck()
    ]
})
```

### demo

<img src="./docs/pic/demo.png" width="375" height="667" />

V - 曝光量
C - 点击量(下面模块手动点了20次 🙂)

上图展示了打点数据情况：  
- 1. 可以用来查看页面每个点的数据是多少 - 支持单位 K M T
- 2. 可以用来开发时测试当前打点情况 - 一目了然
npm package: @findrobbrodie/find-rob-brodie-common
Description: Component library with for FindRobBrodie apps
Author: Rob Brodie
Latest version: 0.1.1

# find-rob-brodie-common

> Component library with for FindRobBrodie apps

[![NPM](https://img.shields.io/npm/v/find-rob-brodie-common.svg)](https://www.npmjs.com/package/find-rob-brodie-common) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save find-rob-brodie-common
```

## Usage

```tsx
import React, { Component } from 'react'

import MyComponent from 'find-rob-brodie-common'
import 'find-rob-brodie-common/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
```

## License

MIT © [FindRobBrodie](https://github.com/FindRobBrodie)
npm package: @findsoft/vue-fluctuation
Description: a simple vue-component for the fluctuation of data
Author: yanggoing
Latest version: 1.0.6

# vue-fluctuation
一个基于vue&vue-digital-transform的数值波动效果组件
## Demo
[vue-fluctuation]("https://yanggoing.github.io/#/vue-fluctuation")

## Install
```
npm install @findsoft/vue-fluctuation
```

## Quick Start
```html
<template>
<fluctuation :value="value" 
             :seperator="isSep"
             :unit="unit"                       
             :interval="interval"
>
    <template>
        <i>可以选择插入以i标签包裹的icon</i>
    </template>
</fluctuation>
</template>
```
```js
import Fluctuation from "vue-fluctuation";

export default {
  components: {
    Fluctuation
  },
  data() {
    return {
      value: 666666,
      isSep: false,
      unit: '个',
      interval: 1000,
      precision:1
    };
  }
};
```
## Slot
可以选择插入一个icon，以i标签包裹，自带默认样式
```vue
<fluctuation :value="value">
    <template>
        <i>可以选择插入以i标签包裹的icon</i>
    </template>
</fluctuation>
```

## Props

| prop                  | type          | description                                   | default   |
| --------------------- | ------------- | --------------------------------------------- | --------- |
| value                 | Number        | 需要监听数值波动的值                             | 0 |
| separator             | Boolean       | 是否开启千分位分隔符                             | false     |
| unit                  | String        | 数值单位，可以是任何你认为正确的单位                | ''        |
| interval              | Number        | 数字滚动过渡时间（ms）                            | 500       |
| precision             | Number        | 有小数时，精确到某一位                            | 1       |
npm package: @findthebrink/responsive-images
Description: create a set of responsive, optimized images from a single source
Author: Brink Technology LTD.
Latest version: 0.1.1

# Responsive Images

## Install
`npm i -g @findthebrink/responsive-images`

## Usage
`responsive-images` is a CLI tool that will generate a set of responsive images from a single source

```
Usage: responsive-images [options] <image>

Options:
  -V, --version                       output the version number
  -d, --debug                         Enable debugging (default: false)
  -o, --output-directory <directory>  The directory to output to (default:
                                      "/home/derek/developer/responsive-images/images__output")
  -w, --widths [px]                   The widths required, separated by commas,
                                      in pixels. E.g., 1024,640,320 (default:
                                      ["original",1024,640,320])
  -f, --formats [format]              The file formats to output, separated by
                                      commas. E.g., jpg,jp2,webp (default:
                                      ["jpg","jp2","webp"])
  -h, --help                          output usage information

```
npm package: @findtools/mock-server
Description: based on express to serve mock data
Latest version: 1.1.0

一直觉得 UmiJS 默认支持的 [Mock 数据](https://umijs.org/zh-CN/docs/mock) 这个功能挺好用的，那如果项目不是用 UmiJS 创建的呢？所以就想写一个工具来启动 mock 服务。

## 我的需求

1. 默认根据 mock 文件夹中文件内容来返回接口数据
2. 默认接口响应时间为 100 到 300 ms
3. 默认所有接口都会成功，这样 mock 文件夹中就只用写希望模拟的请求的数据，比如删除啊编辑啊就不用写了，因为这种一般只关心是否成功

## 大概思路

1. 使用 [Express](http://expressjs.com/) 来启动一个后端服务，当有请求过来时，就根据 mock 文件夹内容去返回响应数据
2. 使用 [chokidar](https://github.com/paulmillr/chokidar) 来监听 mock 文件夹变动
3. 由于需要考虑接口路径中带参数的场景，可以用 [path-to-regexp](https://github.com/pillarjs/path-to-regexp) 来看路径是否匹配

## How to use

After `npm i @findtools/mock-server` , add a script `"mock": "mock-server"` to your `package.json` , and then `npm run mock` to start the mock server. If you want to see all options, run `npm run mock -- --help` .

The server default watches `mock` folder. Following is a mock file example. you can use [Mock.js](http://mockjs.com/examples.html) to generate random data.

```js
// mock/user.js
const { mock } = require('mockjs')

module.exports = {
  'GET /api/current-user': (req, res) => {
    res.send(
      mock({
        username: '@string(6,12)',
      })
    )
  },
}
```

## How to add custom response header

You can add a key `mock-server` in your `package.json` , following is an example. Besides, other options can be configured in `package.json` too.

```json
"mock-server": {
  "responseHeader": {
    "Access-Control-Allow-Headers": "content-type,authorization,others-xxx-in-request-header",
    "Access-Control-Expose-Headers": "xxx-in-response-header-need-to-tell-frontend"
  }
}
```

## How to ignore specific files

For example, `mock-server -i **/mock/**/*.generated.js` will ignore all `*.generated.js` .
npm package: @findtools/swagger2mock
Description: parse swagger.json to generate mock files
Latest version: 0.2.1

swagger2mock is a tool to translate swagger.json to mock files.

Now it only translates GET requests. You can use [@findtools/mock-server](https://github.com/findxc/mock-server) as mock server, it will return 200 to unconfigured mock requests.

## How to use

Use `npx @findtools/swagger2mock -h` to see all options.

Use `npx @findtools/swagger2mock --url https://petstore.swagger.io/v2/swagger.json` to see an example. For local swagger.json file, use `npx @findtools/swagger2mock --path root-relative-path/swagger.json` instead. It will generate mock files. And check https://petstore.swagger.io/ to see the swagger ui.

The generated mock files are formated by prettier. If you want to custom prettier options, add a key `swagger2mock` in your `package.json` , following is an example. Besides, other options can be configured in `package.json` too.

```json
"swagger2mock": {
  "prettier": {
    "parser": "babel",
    "semi": false
  }
}
```
npm package: @findtools/sync-iconfont-files
Description: a tool to download iconfont files in iconfont.cn
Latest version: 0.1.0

A tool to download iconfont files in https://www.iconfont.cn .

## About EGG_SESS_ICONFONT

`EGG_SESS_ICONFONT` is a cookie and you can get the value in dev tools after login into https://www.iconfont.cn . `@findtools/sync-iconfont-files` uses `process.env.EGG_SESS_ICONFONT` to read the value, so you need to set it in your environment variables.

For safety concern, it is better that the login user only has check auth but no modify or delete auth.

PS: In dev tools cookies section, we can find that `EGG_SESS_ICONFONT` expires after 1 year. But I haven't waited for 1 whole year, so I don't know when it will really expire.

## How to use

1. add `EGG_SESS_ICONFONT` to your environment variables
2. run `npm i @findtools/sync-iconfont-files`
3. add a script, for example, `"iconfont": "sync-iconfont-files --projectId=xxx --directory src/iconfont"` to your `package.json` . In your iconfont project page url, you can get the value of projectId
4. run `npm run iconfont` to download files
npm package: @findupworks/commitlint-config
Description: Shareable commitlint config used by FindUP
Latest version: 0.0.1

# @findupworks/commitlint-config

<p>
  <img src="https://img.shields.io/npm/v/@findupworks/commitlint-config?style=flat-square&color=8257E5&labelColor=0086d6" alt="npm version" />
  <img alt="License" src="https://img.shields.io/github/license/findupworks/commitlint-config?style=flat-square&color=8257E5&labelColor=0086d6">
</p>

Shareable [`commitlint`](https://github.com/conventional-changelog/commitlint) config used by FindUP.

## Install

You can install it with npm or Yarn.

```sh
# npm
npm i -D @findupworks/commitlint-config @commitlint/cli

# Yarn
yarn add -D @findupworks/commitlint-config @commitlint/cli
```

## Usage

After installing it, apply the config to `commitlint` by running the following command:

```sh
echo "module.exports = { extends: ['@findupworks/commitlint-config'] };" > .commitlintrc.js
```

## Bonus

To lint commits before they are created, install Husky and use the 'commit-msg' hook.

```sh
# Npm
npm i -D husky

# Yarn
yarn add -D husky
```

After that, you can create a `.huskyrc` file or add to your `package.json` the following code for

Husky v4:

```json
{
  "husky": {
    "hooks": {
      "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
    }
  }
}
```

Husky v5:

```
# .husky/commit-msg
# ...
npx --no-install commitlint --edit $1
# or
yarn commitlint --edit $1
```

## Version Support

- Node.js [LTS](https://github.com/nodejs/LTS#lts-schedule) `>= 10.21.0`
- git `>= 2.13.2`

## License

MIT License © [FindUP](https://github.com/findupworks)
npm package: @findupworks/eslint-config
Description: ESLint configuration used by FindUP.
Latest version: 2.2.3

# FindUP ESLint config

## Whats included?

- Standard config base;
- React plugin;
- React Hooks plugin;
- JSX a11y plugin;
- Prettier;

## Setup

### React (with Next.js)

Install dependencies:
```
npm i -D eslint @findupworks/eslint-config
```
Inside `.eslintrc.json`
```
{
  "extends": [
    "@findupworks/eslint-config/next", 
    "next/core-web-vitals"
  ]
}
```

### React (without Next.js)

Install dependencies:
```
npm i -D eslint @findupworks/eslint-config
```
Inside `.eslintrc.json`
```
{
  "extends": "@findupworks/eslint-config/react"
}
```

### Node.js

Install dependencies:
```
npm i -D eslint @findupworks/eslint-config
```
Inside `.eslintrc.json`
```
{
  "extends": "@findupworks/eslint-config/node"
}
```
npm package: @findupworks/react-native-zendesk-chat
Description: React Native Zendesk Chat
Author: Erick
Latest version: 1.0.0


# IN PROGRESS DEV - react-native-zendeskchat

## Getting started

`$ npm install react-native-zendeskchat --save`

### Mostly automatic installation

`$ react-native link react-native-zendeskchat`

### Manual installation


#### iOS

1. In XCode, in the project navigator, right click `Libraries` ➜ `Add Files to [your project's name]`
2. Go to `node_modules` ➜ `react-native-zendeskchat` and add `RNZendeskchat.xcodeproj`
3. In XCode, in the project navigator, select your project. Add `libRNZendeskchat.a` to your project's `Build Phases` ➜ `Link Binary With Libraries`
4. Run your project (`Cmd+R`)<

#### Android

1. Open up `android/app/src/main/java/[...]/MainActivity.java`
  - Add `import com.reactlibrary.RNZendeskchatPackage;` to the imports at the top of the file
  - Add `new RNZendeskchatPackage()` to the list returned by the `getPackages()` method
2. Append the following lines to `android/settings.gradle`:
  	```
  	include ':react-native-zendeskchat'
  	project(':react-native-zendeskchat').projectDir = new File(rootProject.projectDir, 	'../node_modules/react-native-zendeskchat/android')
  	```
3. Insert the following lines inside the dependencies block in `android/app/build.gradle`:
  	```
      compile project(':react-native-zendeskchat')
  	```

#### Windows
[Read it! :D](https://github.com/ReactWindows/react-native)

1. In Visual Studio add the `RNZendeskchat.sln` in `node_modules/react-native-zendeskchat/windows/RNZendeskchat.sln` folder to their solution, reference from their app.
2. Open up your `MainPage.cs` app
  - Add `using Zendeskchat.RNZendeskchat;` to the usings at the top of the file
  - Add `new RNZendeskchatPackage()` to the `List<IReactPackage>` returned by the `Packages` method


## Usage
```javascript
import RNZendeskchat from 'react-native-zendeskchat';

// TODO: What to do with the module?
RNZendeskchat;
```