open-index/open-npm huggingface dataset:
npm package: @gocorus/material-ui-color-picker
Description: <ColorInput> component for material-ui
Author: Loic Mahieu
Latest version: 3.5.4

# `<ColorPicker>` for material-ui

![`<ColorPicker>` example](./doc/screenshot.png)

ColorPicker based on [`<TextField />`](http://www.material-ui.com/#/components/text-field) and `<ChromePicker />` from [`react-color`](https://github.com/casesandberg/react-color/) and its [redux-form](https://redux-form.com) field component.

## Demo

[https://material-ui-color-picker.now.sh/](https://material-ui-color-picker.now.sh/)

## Installation

For material-ui (v1):

```sh
npm install --save material-ui-color-picker
```

## Usage

```js
import React from 'react'
import ColorPicker from 'material-ui-color-picker'

<ColorPicker
  name='color'
  defaultValue='#000'
  // value={this.state.color} - for controlled component
  onChange={color => console.log(color)}

/>
```
[Redux-form](https://redux-form.com) field
```js
import React, { Component } from 'react';
import { reduxForm, Field } from 'redux-form';
import { ColorPickerField } from 'material-ui-color-picker';

...
<Field
  name="color"
  component={ColorPickerField}
/>
...

```

There is not so much properties at this time. The was very quickly designed for my needs. Feel free to submit a PR with new features ;)

## License

This library is licensed under the [MIT Licence](LICENSE), and sponsored by [iGLOO](https://igloo.be).
npm package: @gocorus/socket-apollo-link
Description: Absinthe Socket Apollo Link
Author: Mauro Titimoli
Latest version: 0.2.7
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @gocorus/socket-apollo-link > Absinthe Socket Apollo Link

<!-- START doctoc -->
<!-- END doctoc -->

## Installation ### Using [npm](https://docs.npmjs.com/cli/npm) ``` $ npm
install --save @gocorus/socket-apollo-link ``` ### Using [yarn](https://yarnpkg.com) ``` $ yarn
add @gocorus/socket-apollo-link ``` ## Examples 1. Create AbsintheSocketLink
(`absinthe-socket-link.js`) ```javascript // @flow import * as AbsintheSocket
from "@gocorus/socket"; import {createAbsintheSocketLink} from
"@gocorus/socket-apollo-link"; import {Socket as PhoenixSocket} from "phoenix";
export default createAbsintheSocketLink(AbsintheSocket.create( new
PhoenixSocket("ws://localhost:4000/socket") )); ``` 2. Send all the operations
using AbsintheSocketLink ```javascript // @flow import ApolloClient from
"apollo-client"; import {InMemoryCache} from "apollo-cache-inmemory"; // see
example 1 import absintheSocketLink from "./absinthe-socket-link"; const client
= new ApolloClient({ link: absintheSocketLink, cache: new InMemoryCache() });
``` 3. Subscribe using AbsintheSocketLink and send queries and mutations using
HttpLink ```javascript // @flow import ApolloClient from "apollo-client"; import
{createHttpLink} from "apollo-link-http"; import {hasSubscription} from
"@jumpn/utils-graphql"; import {InMemoryCache} from "apollo-cache-inmemory";
import {split} from "apollo-link"; // see example 1 import absintheSocketLink
from "./absinthe-socket-link"; const link = split( operation =>
hasSubscription(operation.query), absintheSocketLink, createHttpLink({uri:
"/graphql"}) ); const client = new ApolloClient({ link, cache: new
InMemoryCache() }); ``` ## API ## References - [Absinthe Phoenix
Socket](https://github.com/absinthe-graphql/absinthe-socket/tree/master/packages/socket)
- **Apollo Link** - [Apollo
Client](http://apollo-link-docs.netlify.com/docs/link/#apollo-client) -
[Terminating
Links](http://apollo-link-docs.netlify.com/docs/link/overview.html#terminating)
- [Directional
Composition](http://apollo-link-docs.netlify.com/docs/link/composition.html#directional)
- [Http Link](http://apollo-link-docs.netlify.com/docs/link/links/http.html) ##
License [MIT](LICENSE.txt) :copyright: Jumpn Limited.
npm package: @gocorus/socket-graphiql
Description: Socket GraphiQL Utilities
Author: Mauro Titimoli
Latest version: 0.2.6
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @gocorus/socket-graphiql

> Socket GraphiQL Utilities

<!-- START doctoc -->

<!-- END doctoc -->

## Installation

### Using [npm](https://docs.npmjs.com/cli/npm)

    $ npm install --save phoenix @gocorus/socket-graphiql

### Using [yarn](https://yarnpkg.com)

    $ yarn add phoenix @gocorus/socket-graphiql

## API

<!-- Generated by documentation.js. Update this documentation by updating the source code. -->

### createFetcher

Creates a Fetcher using the given arguments

#### Parameters

- `apiUrl` **[string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)**
- `subscriptionsClient` **SubscriptionClient**
- `subscriptionSentMessage` **[string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)**

## License

[MIT](LICENSE.txt) :copyright: Jumpn Limited.
npm package: @gocrisp/react-store-locator
Description: React component for Crisp's store locator widget, intended for use with the Crisp GeoJSON connector.
Author: Crisp
Latest version: 0.5.8

# @gocrisp/react-store-locator

[![Package Version](https://img.shields.io/npm/v/@gocrisp/react-store-locator.svg)](https://www.npmjs.com/package/@gocrisp/react-store-locator) [![MIT License](https://img.shields.io/npm/l/stack-overflow-copy-paste.svg)](http://opensource.org/licenses/MIT)


React version of Crisp's [store locator component](https://github.com/gocrisp/store-locator). Intended for use with the Crisp GeoJSON connector.

This uses the [Google Maps JavaScript API](https://developers.google.com/maps/documentation/javascript/overview) to easily create a simple store locator from any GeoJSON source.

Please refer to [our example page](https://gocrisp.github.io/store-locator/) to see this package in action and for more advanced usage examples. The steps below will provide the minimum for creating a store locator with React.

## Create a Store Locator

### Set up services

First, go set up a GeoJSON outbound connector on https://platform.gocrisp.com/. It will give you a URL to use later. <!--TODO: needs details/link to BYT-573 -->

Create a [Google Maps API Key](https://developers.google.com/maps/gmp-get-started) with the following APIs enabled:
- `Maps JavaScript API`
- `Places API`
- `Distance Matrix API`.
- `Street View Static API`


### Simple Implementation
**Install this package**
```bash
yarn add @gocrisp/react-store-locator
```
or
```bash
npm install @gocrisp/react-store-locator --save
```

**Include the styles:** We have some minimal styles included as plain css in `@gocrisp/react-store-locator/dist/react-store-locator.css`. You will need to pull this into your site however you are including styles. We've kept the definitions as minimal as possible so that you can easily override or recreate the styles yourself. And every class is namespaced with the `map_` prefix to avoid collisions. 

Then, wherever you want to include the store locator map, insert this snippet:
```jsx
import { StoreLocator } from '@gocrisp/react-store-locator';

<StoreLocator 
  geoJson="<URL from the GeoJSON connector>"
  loaderOptions={{ apiKey: '<your Google Maps API key>' }}
/>
```

Most of the Google Maps JavaScript API options and objects are available for customization as well. More details are available in the [examples and documentation](https://gocrisp.github.io/store-locator/).
npm package: @gocrisp/store-locator-test
Description: Store locator widget, intended for use with the Crisp GeoJSON connector.
Author: Crisp
Latest version: 1.1.0

# @gocrisp/store-locator

Store locator template page for use on any website. Intended for use with the Crisp GeoJSON connector.

## Add the store locator to your site

1. First, go set up a GeoJSON outbound connector on https://platform.gocrisp.com/. It will give you a URL to use later.
2. Create a [Google Maps API Key](https://developers.google.com/maps/gmp-get-started).
3. Install this package
```bash
yarn add @gocrisp/store-locator
```
4. Then, wherever you want to include the store locator map, insert this snippet:
```javascript
import storeLocator from '@gocrisp/store-locator';

storeLocator.init({
  component: document.getElementById('store-locator-map'),
  geoJsonUrl: '<URL from the GeoJSON connector>',
  loaderOptions: { apiKey: '<your Google Maps API key>' },
});
```

By default, this will use the center of the US and a zoom level of 4, but all [google maps options](https://developers.google.com/maps/documentation/javascript/overview#MapOptions) are configurable with the `mapOptions` property.


## Example App

To run the example app locally, you need to build the npm package into `dist` and then run the example app. You can either run the store-locator code with `yarn dev` to watch for changes or build it once with `yarn build`, but with the former you will need to run `dev` and `example` simultaneously.

```bash
yarn install
yarn start
```

The example is automatically updated from the `main` branch and served here:
https://gocrisp.github.io/store-locator
npm package: @godaddy/dmd
Description: Plugin for jsdoc2md with improved readability and GitHub compatibility
Author: GoDaddy Operating Company, LLC
Latest version: 1.0.4

# @godaddy/dmd

[![NPM Version](https://img.shields.io/npm/v/@godaddy/dmd?style=flat-square)](https://www.npmjs.com/package/@godaddy/dmd)
[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/godaddy/dmd/CI?style=flat-square)](https://github.com/godaddy/dmd/actions/workflows/ci.yml)
[![Coverage Status](https://img.shields.io/coveralls/github/godaddy/dmd?style=flat-square)](https://coveralls.io/github/godaddy/dmd)
[![GitHub](https://img.shields.io/github/license/godaddy/dmd?style=flat-square)](LICENSE.md)

Plugin for [jsdoc2md] with improved readability and [GitHub Flavored Markdown]
compatibility.

This plugin borrows from [dmd-readable] and [dmd-bitbucket] with additional
treatments. No HTML tags are generated within the markdown. Headers are
simplified with no nested links. Content links to headers are generated with
GitHub-style slugs. Reference-style links are used instead of being inline.

See the [mock file] for an example of a generated document.

## Installation

Install it as a devDependency in target project:

```
$ npm install @godaddy/dmd --save-dev
```

## Usage

Then pass the plugin name to `jsdoc2md` or `dmd` to generate docs:

```
$ jsdoc2md --plugin @godaddy/dmd --files lib/*.js
```

## Formatting

### Index Tables

This plugins prefers `table` for the index format. The description column uses
the first paragraph or line break of the items description. This provides a more
readable and concise table of contents. The full description will still be used
in the body below. When authoring jsdocs, keep this in mind when descriptions
get long: you can have a short summary paragraph, followed by detailed
paragraphs and examples.

### Reference Links

Another help to readability is the use of [shortcut reference links]. This
leaves the link text in the content, with the destination declared out of the
way at the bottom of the document. In some cases, [collapsed reference links]
are used to avoid conflicts and to handle links with brackets in the link text.

<!-- LINKS -->

[jsdoc2md]:https://github.com/jsdoc2md/jsdoc-to-markdown
[dmd-bitbucket]:https://github.com/jsdoc2md/dmd-bitbucket
[dmd-readable]:https://github.com/DarrenPaulWright/dmd-readable
[mock file]:test/fixtures/mock.snapshot.md
[GitHub Flavored Markdown]:https://github.github.com/gfm/
[shortcut reference links]:https://github.github.com/gfm/#shortcut-reference-link
[collapsed reference links]:https://github.github.com/gfm/#collapsed-reference-link
npm package: @godaddy/eslint-plugin-react-intl
Description: Eslint utils to add checks for react-intl usages.
Author: GoDaddy Operating Company, LLC
Latest version: 1.3.0

# @godaddy/eslint-plugin-react-intl

Validation of locale ids used with react-intl functions/components like `<FormattedMessage />`, `formatMessage` and `defineMessages`.

## Installation

You'll first need to install [ESLint](http://eslint.org):

```
$ npm install eslint --save-dev
```

Next, install `@godaddy/eslint-plugin-react-intl`:

```
$ npm install @godaddy/eslint-plugin-react-intl --save-dev
```

**Note:** If you installed ESLint globally (using the `-g` flag) than you must also install `@godaddy/eslint-plugin-react-intl` globally.

## Usage

Add `@godaddy/react-intl` to the config. You can omit the `eslint-plugin-` prefix:
```json
{
  "extends": ["godaddy/react-intl"]
}
```

Alternatively, you can add `@godaddy/react-intl` to the plugins section of config:

```json
{
    "plugins": [
        "@godaddy/react-intl"
    ]
}
```

By default, `id-missing` and `no-default` rules are enabled to show as errors, and `id-prefix` rule is disabled. 
If you need to set any of these rules differently, then configure the rules under the rules section.

```json
{
    "rules": {
        "@godaddy/react-intl/<rule-name>": 2
    }
}
```

By default, the plugin reads `locales/en-US.json` to apply these eslint rules. The default can be
changed by adding this setting to the config

```json
{
    "settings": {
        "localeFiles": [
            "<path to locale file.json>",
            "<path to any other locale file.json>"
        ]
    }
}
```

If your IDE integrates with eslint, and you are working on multiple packages in a project such as a monorepo, 
then it may have trouble finding which locale files to check keys against. 
To help with this, you can specify the `projectRoot` setting. 
This will need to be an absolute path to the package, which can be determined dynamically from one machine to 
another by using `__dirname` in a .eslintrc.js file.

```js
module.exports = {
    "settings": {
        "projectRoot": __dirname
    }
}
```

## Locale Files

The locale files should be named with their market id (like en-US.json) and should contain data 
in key-value pair format

```json
{
  "in_a_example": "Example",
  "in_a_another_example": "Another Example"
}
```


## Supported Rules

* [id-missing](docs/rules/id-missing.md) Enforces react-intl message ids to be in locale file
* [id-prefix](docs/rules/id-prefix.md) Enforces react-intl message ids to use predefined prefixes
* [no-default](docs/rules/no-default.md) Disallows use of defaultMessage with react-intl
npm package: @godaddy/hostfile
Description: API and CLI for querying and manipulating host files
Author: jpage@godaddy.com
Latest version: 1.0.7
Deprecated: this library is no longer in development, use at your own risk

# @godaddy/hostfile

API and CLI for querying and manipulating host files.

![Build Status](https://travis-ci.org/godaddy/hostwriter.svg?branch=master)

## Installation

First, an important note. By default, most operating systems protect your host file by restricting write permissions.
You'll need to change the permissions on that file before you can use the API or CLI to modify the file. For example:

```shell
sudo chown %USER: /etc/hosts
```


## API

To use the API, install as a dependency:

```shell
npm i --save @godaddy/hostfile
```

...then import:

```js
const hostfile = require('@godaddy/hostfile');
```

The following methods are supported:

### `.point(hostEntries: Dictionary<string, string>): Promise<void>`

Where `hostEntries` is an object mapping host names to IP addresses, `point` assigns each host to an address. If an
address is set to `null`, any existing host file overrides for the host are commented out instead.

### `.pointHost(host: string, address: string): Promise<void>`

Shortcut method for `.point({ [host]: address })`.

### `.pointLocal(host: string): Promise<void>`

Shortcut method for `.point({ [host]: '127.0.0.1' })`.

### `.reset(host: string): Promise<void>`

Shortcut method for `.point({ [host]: null })`.

### `.untilExit(hostEntries: Dictionary<string, string>): Promise<void>`

Same as `.point`, except `SIGTERM`, `SIGINT`, and `SIGHUP` handlers are installed for the process, and before exit,
each of the hosts are reset. This is useful if you're developing a local service, and you only want your host file
pointing locally while the service is running.

### `.isLocal(host: string): Promise<bool>`

Resolves to `true` if the host is pointing to `0.0.0.0`, `127.0.0.1`, `::1`, or `::0`.

### `.watch(): Observable<string>`

Returns an `Observable` that emits events when the host file changes. This is just a wrapper around
[fs.watch](https://nodejs.org/dist/latest-v8.x/docs/api/fs.html#fs_fs_watch_filename_options_listener); see the node
documentation for more information.


## CLI

To install the `hostfile` command-line:

```shell
npm i -g @godaddy/hostfile
```

The `hostfile` command can be used as follows:

```shell
hostfile query host <hosts>               # Lists active entries for one or most hosts. Supports * wildcards.
hostfile query address <addresses>        # Lists active entries pointing to one or more address
hostfile point <hosts> [to] <address>     # Assigns <address> to one or most hosts
hostfile reset <hosts>                    # Removes hostfile assignments for one or more hosts
```
 


## Operating System Support

`hostwriter` only knows how to find the host file on MacOS, Linux, and Windows at this time. If you have a need for
other OS's, let us know.
npm package: @godaddy/jiractl
Description: Jira command-line tool
Author: GoDaddy Operating Company, LLC
Latest version: 1.1.0

# jiractl

[![Greenkeeper badge](https://badges.greenkeeper.io/godaddy/jiractl.svg)](https://greenkeeper.io/)

A command-line tool for managing Jira.

## Install

```
npm i @godaddy/jiractl --global
```

Optionally enable autocomplete:

```
jiractl install-completion
```

## Setup

Add a context for the Jira instance that you use. E.g:

```console
$ jiractl config set-context https://jira.yourteam.com
Username: name
Password:
Context "https://jira.yourteam.com" created.
Set default context to "https://jira.yourteam.com".
```

Add the teams in your project. E.g., for a project named FOO:
```
jiractl setup FOO
```
This will output the team names added.

Some team names are difficult to type or remember on the command line; to alias a team that you use frequently, run:
```
jiractl alias [name] [alias]
```

e.g.
```console
$ jiractl alias "Orange Cats" cats

```
Outputs:
```
Aliased Orange Cats with cats:
 { board: 1234,
   name: 'Orange Cats',
   epicFilter: [ epicFilter ] }
```
You can then run jiractl commands using `cats` as the team name.

## Example usage

```
jiractl --team=cats [action] [context]
```

### Teams

Get teams for a project:
```console
$ jiractl get teams FOO
ID      TYPE    NAME
1234    scrum   Orange Cats
1111    scrum   Sharks
5678    kanban  Bats
```

Describe a team with velocity:
```console
$ jiractl describe team 1111
NAME       ID      TYPE
Sharks     2593    scrum

Velocity:
ID      NAME                    ESTIMATED       COMPLETED       DELTA
18465   Sharks 4/23 - 5/4       0               0               0
17071   Sharks 4/9 - 4/20       46              41              5
17047   Sharks 3/26 - 4/6       47              53              -6
17046   Sharks 3/12 - 3/23      41              34              7

Current Sprint: Sharks 4/23 - 5/4 ID: 18465

Backlog:

KEY             SUMMARY                                             POINTS
FOO-2911        As a shark ISBAT eat fish                           -
FOO-2910        As a shark ISBAT eat crustaceans                    -
FOO-2909        As a shark ISBAT participate in shark week          5
```

### Sprints

Get a team's sprints:

```console
$ jiractl --team=1111 get sprints
ID      STATE   NAME               VELOCITY
18465   open    Sharks 4/23-5/4    0
17071   closed  Sharks 4/9-4/20    41
17047   closed  Sharks 3/26-4/6    53
17046   closed  Sharks 3/12-3/23   34
```

Describe a specific sprint:

```console
$ jiractl --team=1111 describe sprint 18465
```

### Epics

Get a team's epics:

```console
$ jiractl --team=1111 get epics
```

Describe an epic:

```console
$ jiractl describe epic EPIC-KEY
```

### Issues

Get an issue:

```console
$ jiractl get issue ISSUE-KEY
```

Describe an issue:
```console
$ jiractl describe issue ISSUE-KEY
```

Update an issue:
```console
$ jiractl update issue ISSUE-KEY --points=8
```

Open an issue in the Jira UI:
```console
$ jiractl open ISSUE-KEY
```
npm package: @godaddy/localizations
Description: Internationalization localizations for GoDaddy checkout components
Latest version: 1.0.9

# @godaddy/localizations

Internationalization localizations for GoDaddy checkout components.

## Installation

```bash
npm install @godaddy/localizations
# or
pnpm add @godaddy/localizations
# or  
yarn add @godaddy/localizations
```

## Usage

```tsx
import { frFr } from "@godaddy/localizations";
import { GoDaddyProvider, Checkout } from "@godaddy/react";

function App() {
  return (
    <GoDaddyProvider localization={frFr}>
      <Checkout />
    </GoDaddyProvider>
  );
}
```

## Available Localizations

- `frFr` - French (France)

## Localization Structure

Each localization export contains the following sections:

- `general` - General UI text (optional, notes, quantity, etc.)
- `contact` - Contact form labels
- `pickup` - Local pickup configuration
- `delivery` - Delivery and shipping options
- `tips` - Tip/gratuity options
- `shipping` - Shipping address form
- `billing` - Billing address form
- `payment` - Payment methods and form
- `phone` - Phone number input
- `discounts` - Discount code functionality
- `totals` - Order totals and summary
- `lineItems` - Line item display
- `ui` - UI component labels and accessibility text
- `errors` - Error messages and validation
- `validation` - Form validation messages

## Contributing

To add a new localization:

1. Create a new file in `src/` with the locale code (e.g., `esEs.ts` for Spanish)
2. Copy the structure from `frFr.ts` and translate all strings
3. Export the new localization in `src/index.ts`
4. Add documentation to this README

## License

MIT
npm package: @godaddy/tartufo-node
Description: Ensures Tartufo is available for npm-based projects
Author: GoDaddy Operating Company, LLC
Latest version: 0.3.3
Deprecated: this library is no longer under development, use at own risk

# Tartufo, Managed By npm!

[Tartufo](https://tartufo.readthedocs.io/en/stable/) is an open-source project provides tooling to look for and find secrets that may or may not have been accidentally committed to code. It provides a wonderful pre-commit mode that is perfect for keeping repositories clean of committed secrets.

This package exists to help orchestrate making sure Tartufo is available for use by local developers working in pure-javascript projects. When installed into your projects, it will provide a local you can use in your `package.json` scripts.

This package _prefers_ to use a globally-installed tartufo _if present_, otherwise it will install a local copy.

## Prerequisites

This package requires that Python 3.6+ be installed and available. It expects to find python either at the command `python3` or `python` if the former is not available.

**This package does not currently support Windows!**

### Installing Python on a Mac

We recommend using [Homebrew](https://brew.sh) to install Python via `brew install python`.

### Installing Python on Linux

Please follow your distro's recommendations for installing Python.

### Installing Python on Windows

_Windows is not yet supported with this package. This documentation will be udpated when it is supported._

## Installing

Run `npm install --save-dev @godaddy/tartufo-node` to install in your local project

## Example usage

You can use `tartufo` like any other npm-provided bin, for example to use tartufo as a pre-commit you could combine it with [Husky](https://github.com/typicode/husky#readme):

Add the following to your `package.json`:

```json
{
  "scripts": {
    "tartufo:pre-commit": "tartufo pre-commit"
  }
}
```

Then tell Husky to run the command on pre-commit:

```bash
npx husky add .husky/pre-commit "npm run tartufo:pre-commit"
git add .husky/pre-commit
```

Alternatively you could work with tartufo directly via npx, for example you could run `npx tartufo --help` in your project to see command line tools available to you.

## Troubleshooting

This package provides a `tartufo-helper` tool to help diagnose issues locally. To do so, run `npx tartufo-helper doctor` to see debugging output. If necessary, it may recommend you run `npx tartufo-helper reset` to reset your local installation.

## How it works

This package takes advantage of `preinstall` and `postinstall` npm lifecycle hooks. When installing into your package, two things will happen:

First, the `preinstall` script will validate your local environment and fail if it cannot find Python 3.6+.

Second `postinstall` script will check if you have `tartufo` available globally. If so, the `postinstall` script will exit as there is nothing to do!

However if no `tartufo` is available, it will create a [venv](https://docs.python.org/3/library/venv.html) locally (in the `node_modules` folder) and use pip to install tartufo.
npm package: @godaddy/webpack-rtlcss-plugin
Description: Webpack Plugin to operate Right-to-Left operations over .css
Author: GoDaddy Operating Company, LLC
Latest version: 1.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# webpack-rtlcss-plugin

Webpack plugin that takes a `.css` chunk and processes RTL (right to left) conversion. Unlike other Webpack RTL plugins, this plugin __DOES NOT__ create a separate `.css` file.

Uses [rtlcss] under the hood. For more information on how to utilize [rtlcss] check out the [rtlcss docs](https://rtlcss.com/learn/).

## Install

```sh
npm install @godaddy/webpack-rtlcss-plugin --save-dev
```

## Usage

```js
const RTLPlugin = require('@godaddy/webpack-rtlcss-plugin');

// Within Webpack config

plugins: [
  ...other webpack plugins
  new RTLPlugin()
],
```

## Example

Check out the [test webpack config](./test/unit/webpack.config.js) to see an example of how `@godaddy/webpack-rtlcss-plugin` works with `mini-css-extract-plugin`.

[rtlcss]: https://github.com/MohammadYounes/rtlcss
npm package: @godal-inc/nestjs-dataloader
Description: A NestJS decorator for dataloader
Latest version: 2.1.1

# NestJS Dataloader

![Node.js CI](https://github.com/krislefeber/nestjs-dataloader/workflows/Node.js%20CI/badge.svg)
[![Coverage Status](https://coveralls.io/repos/github/krislefeber/nestjs-dataloader/badge.svg?branch=master)](https://coveralls.io/github/krislefeber/nestjs-dataloader?branch=master)

NestJS dataloader simplifies adding [graphql/dataloader](https://github.com/graphql/dataloader) to your NestJS project. DataLoader aims to solve the common N+1 loading problem.

## Installation

Install with yarn

```bash
yarn add nestjs-dataloader
```

Install with npm

```bash
npm install --save nestjs-dataloader
```

## Usage

### NestDataLoader Creation

We start by implementing the `NestDataLoader` interface. This tells `DataLoader` how to load our objects.

```typescript
import * as DataLoader from 'dataloader';
import { Injectable } from '@nestjs/common';
import { NestDataLoader } from 'nestjs-dataloader';
...

@Injectable()
export class AccountLoader implements NestDataLoader<string, Account> {
  constructor(private readonly accountService: AccountService) { }

  generateDataLoader(): DataLoader<string, Account> {
    return new DataLoader<string, Account>(keys => this.accountService.findByIds(keys));
  }
}
```

The first generic of the interface is the type of ID the datastore uses. The second generic is the type of object that will be returned. In the above instance, we want `DataLoader` to return instances of the `Account` class.

### Providing the NestDataLoader

For each NestDataLoader we create, we need to provide it to our module.

```typescript
import { Module } from '@nestjs/common';
import { APP_INTERCEPTOR } from '@nestjs/core';
import {DataLoaderInterceptor} from 'nestjs-dataloader'
...

@Module({
  providers: [
    AccountResolver,
    AccountLoader,
    {
      provide: APP_INTERCEPTOR,
      useClass: DataLoaderInterceptor,
    },
  ],

})
export class ResolversModule { }
```

### Using the NestDataLoader

Now that we have a dataloader and our module is aware of it, we need to pass it as a parameter to an endpoint in our graphQL resolver.

```typescript
import * as DataLoader from 'dataloader';
import { Loader } from 'nestjs-dataloader';
...

@Resolver(Account)
export class AccountResolver {

    @Query(() => [Account])
    public getAccounts(
        @Args({ name: 'ids', type: () => [String] }) ids: string[],
        @Loader(AccountLoader.name) accountLoader: DataLoader<Account['id'], Account>): Promise<Account[]> {
        return accountLoader.loadMany(ids);
    }
}
```

The important thing to note is that the parameter of the `@Loader` decorator is the name of the `NestDataLoader` class we want to be injected to the method. The DataLoader library will handle bulk retrieval and caching of our requests. Note that the caching is stored on a per-request basis.

## Contributing

Pull requests are always welcome. For major changes, please open an issue first to discuss what you would like to change.
npm package: @godartm/react-responsive-pinch-zoom-pan
Description: Enables zooming and panning an image, both mobile and desktop.
Author: Godart Marin
Latest version: 1.0.0

# react-responsive-pinch-zoom-pan

This is a fork of the repository [react-responsive-pinch-zoom](https://github.com/bradstiff/react-responsive-pinch-zoom-pan) by [Brad Stiffler](https://github.com/bradstiff) in order to keep the latest dependencies up to date.

A React component that adds pinch-zoom and pan capability to an `img` element. Both mobile and desktop browsers are supported. In desktop mode, you zoom with the mouse scrollwheel, and pan by dragging.

On render, the zoom and pan values are applied using CSS transforms. 

## Install

`npm install react-responsive-pinch-zoom-pan --save`

## Try it out

### Online

[Demo](https://bradstiff.github.io/react-responsive-pinch-zoom-pan/)

### Local

1. `git clone https://github.com/bradstiff/react-responsive-pinch-zoom-pan.git`
2. `cd react-responsive-pinch-zoom-pan`
3. `npm install`
4. `npm start`
5. Browse to http://localhost:3001

## Usage

```javascript
import React from "react";
import PinchZoomPan from "react-responsive-pinch-zoom-pan";

const App = () => {
    return (
        <div style={{ width: '500px', height: '500px' }}>
            <PinchZoomPan>
                <img alt='Test Image' src='http://picsum.photos/750/750' />
            </PinchZoomPan>
        </div>
    );
};
```

## API

Prop		| Type		| Default	| Description
------------|-----------|-----------|--------------------------------------------------------------------------------------------------------------------
initialScale| number	| 'auto'	| The initial scale of the image.  When `auto`, the image will be proportionally 'autofit' to the container.
minScale	| number	| 'auto'	| The minimum scale to which the image can be zoomed out. When `auto`, the minimum scale is the 'autofit' scale.
maxScale	| number	| 1			| The maximum scale to which the image can be zoomed in. 
position    | 'center' or 'topLeft'    | 'topLeft'  | Position of the image relative to the container. Applies when the scaled image is smaller than the container.
zoomButtons	| bool		| true		| Render plus (+) and minus (-) buttons on top of the image as another way to access the zoom feature.
doubleTapBehavior	| 'reset' or 'zoom' | 'reset'		| Whether to zoom in or reset to initial scale on double-click / double-tap.

## Development

You're welcome to contribute to react-responsive-pinch-zoom-pan.

To set up the project:

1.  Fork and clone the repository
2.  `npm install`
3.  `npm start`

The example page will be available on http://localhost:3001 in watch mode, meaning you don't have to refresh the page to see your changes.
npm package: @godbleason/uniswap-v2-sdk
Description: 🛠 An SDK for building applications on top of Uniswap.
Latest version: 1.0.1

# Uniswap SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/Uniswap/uniswap-sdk/workflows/CI/badge.svg)](https://github.com/Uniswap/uniswap-sdk)
[![npm version](https://img.shields.io/npm/v/@uniswap/sdk/latest.svg)](https://www.npmjs.com/package/@uniswap/sdk/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@uniswap/sdk/latest.svg)](https://bundlephobia.com/result?p=@uniswap/sdk@latest)

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/Uniswap/uniswap-sdk.git
```

Move into the uniswap-sdk working directory

```sh
cd uniswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @godbleason/uniswap-v2-sdk-frax
Description: 🛠 An SDK for building applications on top of Uniswap.
Latest version: 1.0.3

# Uniswap SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/Uniswap/uniswap-sdk/workflows/CI/badge.svg)](https://github.com/Uniswap/uniswap-sdk)
[![npm version](https://img.shields.io/npm/v/@uniswap/sdk/latest.svg)](https://www.npmjs.com/package/@uniswap/sdk/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@uniswap/sdk/latest.svg)](https://bundlephobia.com/result?p=@uniswap/sdk@latest)

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/Uniswap/uniswap-sdk.git
```

Move into the uniswap-sdk working directory

```sh
cd uniswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```