open-index/open-npm huggingface dataset:
npm package: @progresso/react-giphy-picker-https
Description: A react gif picker using giphy API over https
Author: Steven Iseki
Latest version: 1.3.6

# react-giphy-picker-https

[![npm version](https://badge.fury.io/js/%40progresso%2Freact-giphy-picker-https.svg)](https://badge.fury.io/js/%40progresso%2Freact-giphy-picker-https)

![](https://raw.githubusercontent.com/progresso-group/react-giphy-picker/master/example/preview.gif)

react-giphy-picker-https is a simple gif picker component using giphy API over https.

## Install

`yarn add @progresso/react-giphy-picker-https`

## Usage basic

```jsx
import Picker from 'react-giphy-picker-https'
import ReactDOM from 'react-dom'
import React, { Component, PropTypes } from 'react'

class TestComponent extends Component {
  log (gif) {
    console.log(gif)
  }

  render () {
    return (
      <div>
        <Picker apiKey="your-giphy-api-key" onSelected={this.log.bind(this)} />
      </div>
    )
  }
}

ReactDOM.render(
  <TestComponent />,
  document.getElementById('root')
)
```

## Props

### `apiKey` (required)
Your giphy api key, see [API Quickstart Guide](https://developers.giphy.com/docs/api) on [developers.giphy.com](https://developers.giphy.com/).

### `width` (required)
The width of the control, in pixels. Used for layouting gifs with different sizes.

### `onSelected` (required)
Handles a gif selection and provides the selected gif as a [Gif Object](https://developers.giphy.com/docs/api/schema#gif-object).

### `visible`
Set to `true` to make the component visible.

### `modal`
Set to `true`, if you want the component to be displayed as a floating layer. It will set the component `position: absolute` and add a box shadow.

### `style`
A `React.CSSProperties` object that appies to the outer component shape.

### `searchBoxStyle`
A `React.CSSProperties` object that applies to the component's search box.

### `gifStyle`
A `React.CSSProperties` object that applies to each rendered gif image within the component.

### `scrollComponent`
A `React.Component` that should be used for scrolling. If not provided, a default `<div />` with `overflow-y: auto` is used.

## Development
    yarn
    yarn dev

## Test
    yarn test

## Build
    yarn
    yarn build

## License

[MIT](http://isekivacenz.mit-license.org/)
npm package: @progressteaching/lightning-components
Description: ### Storybook
Author: Progress Teaching
Latest version: 1.17.0

# Lightning-components

### Storybook

Run in terminal:

```bash
npm run storybook
```

### Build & publish

To Build the library, run:

```bash
npm run build
```

This command creates a folder in root directory called lib. This folder is used as distribute folder for components.

To publish the library to npm, run:

```bash
npm publish
```

## Component library dependency order

Please only use components from the following places only (in the following order):

- TailwindUI (https://tailwindui.com/components)
- Shadcn (https://ui.shadcn.com/)
- Flowbite (https://flowbite.com/)
- NextUI (https://nextui.org/docs/components)

## Changelog

Change logs must be added for every single PR. You should always add it under a `unreleased` header.

For example:

```
## Unreleased

* The name of PR here (PR #123)[https://github.com/ProgressTeaching/lightning-components/pull/123]
* The name of PR here (PR #124)[https://github.com/ProgressTeaching/lightning-components/pull/124]
* The name of PR here (PR #125)[https://github.com/ProgressTeaching/lightning-components/pull/125]
```

## Publishing a new version of the component

Example PR of how to do this: https://github.com/ProgressTeaching/lightning-components/pull/10

1. Update the `package.json` with new version
2. Run `npm install` to generate new `package-lock.json`
3. Update (CHANGELOG.md)[/CHANGELOG.md] with the new version number

```
## 1.2.0

* The name of PR here (PR #123)[https://github.com/ProgressTeaching/lightning-components/pull/123]
* The name of PR here (PR #124)[https://github.com/ProgressTeaching/lightning-components/pull/124]
* The name of PR here (PR #125)[https://github.com/ProgressTeaching/lightning-components/pull/125]
```

4. Commit and make PR
npm package: @progressteaching/react-components
Description: React components for creating ProgressTeaching frontend apps
Author: ProgressTeaching
Latest version: 1.2.1

# react-components

> React components for creating ProgressTeaching frontend apps

[![NPM](https://img.shields.io/npm/v/@progressteaching/react-components.svg)](https://www.npmjs.com/package/@progressteaching/react-components) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save @progressteaching/react-components
```

## Usage

```jsx
import React, { Component } from 'react'

import { SidebarNav } from '@progressteaching/react-components'
import '@progressteaching/react-components/dist/index.css'

class Example extends Component {
  render() {
    return <SidebarNav />
  }
}
```

## Local development

Create two terminals.

On one run:
```
$ npm start;
```

On the other:
```
$ cd example && npm start;
```

## License

MIT © [ProgressTeaching](https://github.com/ProgressTeaching)
npm package: @progstream/cantor-pairing
Description: cantor pairing function
Author: @progstream
Latest version: 1.0.1

# cantor-pairing

The Cantor pairing function is a primitive recursive pairing function.

## Installation
```
npm i @progstream/cantor-pairing
```

## Usage
```tsx
import pairing from '@progstream/cantor-pairing'

pairing.pair(3, 8)
// 74

pairing.unpair(74)
// [3, 8]
```
npm package: @progtechbr/n8n-nodes-rdsme
Description: Send events through API to RD Station Marketing para Ecommerce
Author: ProgTech
Latest version: 0.1.6

![Banner image](https://user-images.githubusercontent.com/10284570/173569848-c624317f-42b1-45a6-ab09-f0ea3c247648.png)

# n8n-nodes-starter

This repo contains example nodes to help you get started building your own custom integrations for [n8n](https://n8n.io). It includes the node linter and other dependencies.

To make your custom node available to the community, you must create it as an npm package, and [submit it to the npm registry](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry).

If you would like your node to be available on n8n cloud you can also [submit your node for verification](https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/).

## Prerequisites

You need the following installed on your development machine:

* [git](https://git-scm.com/downloads)
* Node.js and npm. Minimum version Node 20. You can find instructions on how to install both using nvm (Node Version Manager) for Linux, Mac, and WSL [here](https://github.com/nvm-sh/nvm). For Windows users, refer to Microsoft's guide to [Install NodeJS on Windows](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows).
* Install n8n with:
  ```
  npm install n8n -g
  ```
* Recommended: follow n8n's guide to [set up your development environment](https://docs.n8n.io/integrations/creating-nodes/build/node-development-environment/).

## Using this starter

These are the basic steps for working with the starter. For detailed guidance on creating and publishing nodes, refer to the [documentation](https://docs.n8n.io/integrations/creating-nodes/).

1. [Generate a new repository](https://github.com/n8n-io/n8n-nodes-starter/generate) from this template repository.
2. Clone your new repo:
   ```
   git clone https://github.com/<your organization>/<your-repo-name>.git
   ```
3. Run `npm i` to install dependencies.
4. Open the project in your editor.
5. Browse the examples in `/nodes` and `/credentials`. Modify the examples, or replace them with your own nodes.
6. Update the `package.json` to match your details.
7. Run `npm run lint` to check for errors or `npm run lintfix` to automatically fix errors when possible.
8. Test your node locally. Refer to [Run your node locally](https://docs.n8n.io/integrations/creating-nodes/test/run-node-locally/) for guidance.
9. Replace this README with documentation for your node. Use the [README_TEMPLATE](README_TEMPLATE.md) to get started.
10. Update the LICENSE file to use your details.
11. [Publish](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry) your package to npm.

## More information

Refer to our [documentation on creating nodes](https://docs.n8n.io/integrations/creating-nodes/) for detailed information on building your own nodes.

## Publish Scoped Package to NPM

```bash
npm adduser
npm publish --access public
```

## License

[MIT](https://github.com/n8n-io/n8n-nodes-starter/blob/master/LICENSE.md)
npm package: @progus/connector-ui
Description: Progus connector UI components
Latest version: 0.7.2

# @progus/connector-ui

UI components for Progus apps. Cross-sell helpers are re-exported from
`@progus/connector`.

## Installation

```bash
npm install @progus/connector-ui
```

## Usage

```tsx
import {
  Recommendations,
  PartnerIdCard,
  PartnerProgramBanner,
  getCrossSellOffersFromApi,
} from "@progus/connector-ui";
```

Note: `getCrossSellOffersFromApi` is re-exported from `@progus/connector` and is
intended to run server-side (pass a server-side `fetch`).

## Prompt: Partner ID block implementation (copy/paste)

```
You are adding the Partner ID block using @progus/connector-ui.

Implement these pieces:
1) Fetch current partnerId on load (server-side loader recommended):
   - call checkPartnerId({ shopDomain }) via @progus/connector
   - set initial value and lock the field if a partnerId already exists

2) Render PartnerIdCard:
   - <PartnerIdCard
       partnerId={value}
       onPartnerIdChange={setValue}
       onSave={handleSave}
       saveLabel="Save Partner ID"
       label="Partner ID"
       placeholder="e.g. partner_123"
       helpText="Enter your partner ID to track affiliate referrals."
       loading={loading}
       saving={saving}
       locked={isLocked}
       error={error}
       saveDisabled={isLocked || loading || saving || !value.trim()}
     />

3) Save flow:
   - on save, call assignPartnerId({ shopDomain, partnerId }) via @progus/connector
   - on success, lock the field and stop allowing edits
```

## Prompt: Recommendations block implementation (copy/paste)

```
You are adding the Progus Recommendations block using @progus/connector-ui.

Implement these pieces:
1) Fetch recommendations (server-side loader preferred):
   - getCrossSellOffersFromApi({ appName, limit, locale, installedAppKeys })
   - pass the resulting list to the UI

2) Render Recommendations:
   - <Recommendations
       recommendations={list}
       title="Recommended Progus apps"
       dismissLabel="Hide recommendations"
       installLabel="Install"
       freePlanLabel="Free plan"
       newBadgeLabel="New"
       onDismiss={() => hideBlock()}
     />
   - if list is empty, do not render the block

This block is independent from the partner program and can be used alone.
```

## Prompt: Partner program banner (copy/paste)

```
You are adding the Partner Program banner using @progus/connector-ui.

Implement these pieces:
1) Render PartnerProgramBanner near the top of the dashboard:
   - <PartnerProgramBanner />
2) The banner is dismissable and persists dismissal in localStorage.
```