open-index/open-npm huggingface dataset:
npm package: @netresearch/node-red-contrib-magento-eqp
Description: Node-RED module for parsing callbacks from the Magento Marketplace EQP API
Author: DevMiner
Latest version: 4.1.0

# @netresearch/node-red-contrib-magento-eqp

[![npm version](https://img.shields.io/npm/v/@netresearch/node-red-contrib-magento-eqp?style=flat-square)](https://www.npmjs.com/package/@netresearch/node-red-contrib-magento-eqp)
[![CI](https://img.shields.io/github/actions/workflow/status/netresearch/node-red-contrib-magento-eqp/lint.yml?branch=main&style=flat-square&label=CI)](https://github.com/netresearch/node-red-contrib-magento-eqp/actions/workflows/lint.yml)
[![CodeQL](https://img.shields.io/github/actions/workflow/status/netresearch/node-red-contrib-magento-eqp/codeql.yml?branch=main&style=flat-square&label=CodeQL)](https://github.com/netresearch/node-red-contrib-magento-eqp/actions/workflows/codeql.yml)
[![License: MIT](https://img.shields.io/npm/l/@netresearch/node-red-contrib-magento-eqp?style=flat-square)](https://github.com/netresearch/node-red-contrib-magento-eqp/blob/main/LICENSE)
[![Node.js](https://img.shields.io/node/v/@netresearch/node-red-contrib-magento-eqp?style=flat-square)](https://nodejs.org)
[![TypeScript](https://img.shields.io/badge/TypeScript-strict-blue?style=flat-square)](https://www.typescriptlang.org/)

[Node-RED](https://nodered.org/) nodes for parsing [Adobe Commerce Marketplace EQP API](https://developer.adobe.com/commerce/marketplace/guides/eqp/v1/) callbacks.

## Installation

Install via npm or the Node-RED Palette Manager:

```sh
npm install @netresearch/node-red-contrib-magento-eqp
```

## Nodes

| Node                          | Description                              |
| ----------------------------- | ---------------------------------------- |
| `magento-eqp-config`          | Configuration node with API secret       |
| `magento-eqp-callback-parser` | Parse EQP callbacks from `http in` nodes |

## Example Flow

An example flow is available at [example/flow.json](https://github.com/netresearch/node-red-contrib-magento-eqp/blob/main/example/flow.json).

![Example Usage](https://i.imgur.com/xGD2WvE.png)

## Related packages

- [`@netresearch/node-magento-eqp`](https://github.com/netresearch/node-magento-eqp) — TypeScript API wrapper for the EQP API

## Contributing

Contributions, issues, and feature requests are welcome. See the [issues page](https://github.com/netresearch/node-red-contrib-magento-eqp/issues).

## License

[MIT](LICENSE) - Netresearch DTT GmbH
npm package: @netresearch/postdirekt-autocomplete-library
Description: Library for the Deutsche Post Direkt Autocomplete
Author: Andreas Müller
Latest version: 1.4.0

# Deutsche Post Direkt DATAFACTORY Autocomplete Library

## Manual Installation

1. Pick the format you need from `dist/browser/postdirekt-autocomplete-lib.*.js
2. Move the `.js` file to your project
3. Move the file `dist/browser/styles.css` to your project

## Usage

Include the library `.js` and `.css` on the HTML page where your form is located:

``` html
<head>
    <script type="text/javascript"
            src="path/to/postdirekt-autocomplete-lib.*.js"></script>
    <link rel="stylesheet"
        type="text/css"
        href="path/to/styles.css">
</head>
```

Instantiate the library, passing in the following information:

- the `HTMLInputElement`s for your *street*, *city*, *postal code* and *country* inputs
- the country input value that maps to "Germany"
- a valid DATAFACTORY Autocomplete access token. You can generate a token from PHP with the [PHP Authentication SDK](https://github.com/netresearch?q=autocomplete)

``` js
postdirektAutocompleteLib.init(
        document.querySelector('[id="shipping:street1"]'),
        document.querySelector('[id="shipping:city"]'),
        document.querySelector('[id="shipping:postcode"]'),
        document.querySelector('[name="shipping[country_id]"]'),
        'DE',
        'YOUR_ACCESS_TOKEN',
        'YOUR_HOUSENUMBER_HINT_TEXT'
    );
```

### Additional Options

The library also supports the following optional parameters:
- `renderSuggestions` - boolean, default `true`. If `false`, the library will not render suggestions by itself. You can implement your own suggestion rendering by listening to the `'autocomplete:suggestions-retrieve'` event on the document.
- `'autocomplete:suggestions-retrieve'` event will contain the suggestions and a pointer to the source element.
npm package: @netresearch/postdirekt-autocomplete-sdk
Description: SDK for the Deutsche Post Direkt Autocomplete API
Author: Paul Siedler
Latest version: 1.4.0

# Deutsche Post Direkt DATAFACTORY Autocomplete 2.0 API SDK

## Usage Example

### In browser
```javascript
import { SearchSubjects, createSearchService } from 'dist/lib/postdirekt-autocomplete';

let searchService = createSearchService('myApiAccessToken')
let requestBuilder = searchService.requestBuilder;
let request = requestBuilder.create({
  country: 'de',
  subject: Subject.Buildings,
  city: 'Test city',
  street: 'Test street'
});

let responsePromise = searchService.search(request);
responsePromise.then(response => { /* handle response */ })
```

### In node

Running in node currently is only possible with a `fetch` polyfill
 (e.g. [isomorphic-fetch](https://www.npmjs.com/package/isomorphic-fetch)).
 A native implementation might follow in the future.

```javascript
require('es6-promise').polyfill();
require('isomorphic-fetch');
const sdk = require('./dist/browser/postdirekt-autocomplete.umd');
let process = require('process');

const token = process.env.TOKEN;

const searchService = sdk.createSearchService(token);

const request = searchService.requestBuilder.create({
  country: 'de',
  street: 'Be',
  city: 'Leipzig',
  subject: sdk.SearchSubjects.PostalCodesCitiesStreets,


});

searchService.search(request).then(
  (response) => {
    console.table(response.addresses)
  }
).catch(
  console.error
);

```
npm package: @netresearch/vault-read
Description: Read and print secrets from Hashicorp Vault
Author: Paul Siedler
Latest version: 1.3.1

# vault-read

Read and print secrets from Hashicorp Vault

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/@netresearch/vault-read.svg)](https://npmjs.org/package/@netresearch/vault-read)
[![Downloads/week](https://img.shields.io/npm/dw/@netresearch/vault-read.svg)](https://npmjs.org/package/@netresearch/vault-read)
[![License](https://img.shields.io/npm/l/@netresearch/vault-read.svg)](https://github.com/netresearch/vault-read/blob/master/package.json)

## Usage

```sh-session
$ npm install -g vault-read
$ vault-read [-u|--username Vault user] [-p|--password Vault password] [-a|--address Vault address] PATH [KEY]
$ vault-read (-v|--version|version)
vault-read/0.0.0 linux-x64 node-v10.16.3
$ vault-read --help
Read secrets from the vault

USAGE
  $ vault-read PATH [KEY]

ARGUMENTS
  PATH  Path from which to read the secret
  KEY   Specific key from the data store in the path

OPTIONS
  -a, --address=address    The Vault url, alternatively provide CI_VAULT_ADDRESS env variable
  -h, --help               show CLI help
  -p, --password=password  The LDAP password for Vault, alternatively provide CI_VAULT_PASSWORD env variable
  -u, --username=username  The LDAP username for Vault, alternatively provide CI_VAULT_USER env variable
  -v, --version            show CLI version
```
npm package: @netribe/jsx-bundle
Description: A pre-configured global bundler for JSX
Author: ido-ofir
Latest version: 1.0.0

# jsx-bundle
A pre-configured global bundler for JSX

## Installation
Install globally
```
npm i -g jsx-bundle
```

## Usage
### Development usage
```sh
jsx-bundle Test.jsx
```
This compiles and bundles your component and then opens it in your browser. the page will live-reload but no build files are created. 
> If the source file does not exist it will be created for you.

### Production usage

```sh
jsx-bundle src/Test.jsx dist/bundle.js
```
This compiles and bundles `src/Test.jsx` to `dist/bundle.js`.

## Options
Option | Description
--- | ---
<a href="#external">--external</a> | a list of modules to exclude from the bundle
<a href="#dlls">--dll</a> | compile this bundle as a dll that can be used by other bundles 
--watch | watch the source files and recompiles when they change
--port | the dev server's http port to use
--ws-port | the dev server's websocket port to use
--hot (not yet applicable) | enable hot reloading for this bundle

### External
The `--external` option tells the bundler which moduels should be excluded from the build, so any peer dependencies should be listed here.
`react` and `react-dom` are external by default but if you are using additional peer dependencies you should pass them in the `external` option along with `react` and `react-dom` (if you use them):
```sh
jsx-bundle src/Component.jsx dist/index.js --external react react-dom @material-ui/core
```

### DLLs

The `--dll` option lets your bundle use (or be used by) other DLL bundles, without having to bundle them all together. this may be usefull when bundling for a full application (rather than a single component or library), or if you want to load modules dynamically. your code is split between several DLL bundles and you only need to build the bundles that you're currently developing. the exports of your bundle can be imported by other DLL bundles and vise versa (although circular dependency is not supported).
```sh
jsx-bundle src/Test.jsx dist/bundle.js --dll
```
DLL bundles can export either an object with named modules:
```jsx
// myLibrary.js
import TextInput from './TextInput.jsx';
import BooleanSwitch from './BooleanSwitch.jsx';

export default {
    TextInput,
    BooleanSwitch
}
```
or a single React component:
```jsx
// TextEditor.jsx
import React from 'react';

export default class TextEditor extends React.Component { ... }
```
You can than import them to other DLLs using the component class name or the exported object's keys:
```jsx
import TextInput from 'TextInput';
import BooleanSwitch from 'BooleanSwitch';
import TextEditor from 'TextEditor';
```
Note that all the DLL modules share scope so proper namespacing may be a good idea.

# TODO
*   Some optimization for development and production builds
*   Hot Component Replacement
npm package: @netribe/react-interact
Description: Easy user interaction (hover, mouse press, focus) for react components
Author: ido-ofir
Latest version: 1.0.1

# react-interact
Easy user interaction (mouse hover, mouse press, focus) for react components.

# Installation
`npm i @netribe/react-interact --save`

# Usage


```jsx
import React from 'react';
import Interact from '@netribe/react-interact';

export default () => 
    <div>
        <Interact>
            { ({ isHovered, isPressed, isFocused })  => 
                <input 
                    style={{ 
                        background: isPressed 
                            ? '#fff' 
                            : isHovered 
                                ? '#ddd'
                                : '#eee', 
                        border: `1px solid ${isFocused ? 'blue' : 'transparent'}`,
                        outline: 0,
                        borderRadius: 4 
                    }}
                />
            }
        </Interact>
    </div>
;
```
`@netribe/react-interact` expects a function as a single child.
this function should return the element to render and will run whenever the hover/pressed/focused state changes on this element.
it recieves one argument, an object with 'isHovered', 'isPressed' and 'isFocused' boolean values.

Note that `isFocused` will only work on focusable elements (usually inputs)

## Development

```
git clone https://github.com/netribe/react-interact.git
```

compiled with rollup, install it globally if it's missing:
```
npm install --global rollup
```

Compile
```
cd react-interact
rollup -c
```