open-index/open-npm huggingface dataset:
npm package: @nfjs/auth-openid
Description: Authorization by openid module
Author: Andrey Maksimov
Latest version: 1.0.1

**ОГЛАВЛЕНИЕ**
- [Используемые понятия](#Используемые-понятия)
- [Принцип работы](#Принцип-работы)
- [Конфигурация](#Конфигурация)

### Используемые понятия
`Клиент` - инстанс класса обёртки над `openid-client`.

### Принцип работы
Является оберткой над пакетом `openid-client`. Позволяет сконфигурировать экземпляр для аутентификации пользователя (встроиться в общий механизм @nf/auth) и получить роли для приложения.
Осуществляется это с помощью следующих шагов:
* на основной форме `desktop.frm` выполняется запрос на подмененный роут веб сервера */front/action/check-auth*, для проверки авторизованности в приложении 
* при получении информации от веб сервера, что не пользователь не авторизован и вместе с этим приходит адрес, на который нужно перенаправиться для аутентификации
* ожидается ответный вызов на адресе */openid/callback* с состоянием не равным **logout**
* достается информация о пользователе из токенов, отдельно выиискиваются его роли(_roles), уникальное(_username) и полное(_fullname) имя, и складывается в сессию пользователя(openid-userinfo) на веб сервере вместе с токенами
* выполняются хуки, помеченные как "до авторизации"
* выполняются хуки, помеченные как "авторизация" (обычно это сохранение информации о пользователе в постоянное хранилище). Если они успешно прошли, считается что пользователь полностью авторизован в приложении
* выполняются хуки, помеченные как "после авторизации"
* происходит перенаправление на адрес */* и форма `desktop.frm` уже показывает оснвную форму (`main.frm`) приложения.

В последующих запросах к веб серверу, на роуте в котором указана **auth** middleware юудет проверятся время жизни access токена и пытается обновиться по истечении.

### Конфигурация
Описание в **package.config.json**
В блоке `client` можно указывать все опции для оригинального класса **Client** пакета `openid-client`.
npm package: @nfjs/global-properties-addon
Description: Global properties for NF-Framework
Author: Sergey Bekhter
Latest version: 1.1.0

# @nfaddon/global-properties

Для любого компонента унаследованного от PlElement (в том числе и PLForm)
флаг global у свойтсва уведомляет все другие компоненты
с таким же именем свойства и флагом global

``` js
class Component extends PlElement {
    static properties = {
        propName: { type: String, global: true}
    }
}

class OtherComponentOrForm extends PlForm {
    static properties = {
        propName: { type: String, global: true}
    }
}
```
npm package: @nfort/logistics-core
Description: logistics-core React component
Latest version: 2.19.3

# logistics-core

[![Travis][build-badge]][build]
[![npm package][npm-badge]][npm]
[![Coveralls][coveralls-badge]][coveralls]

Describe logistics-core here.

[build-badge]: https://img.shields.io/travis/user/repo/master.png?style=flat-square
[build]: https://travis-ci.org/user/repo

[npm-badge]: https://img.shields.io/npm/v/npm-package.png?style=flat-square
[npm]: https://www.npmjs.org/package/npm-package

[coveralls-badge]: https://img.shields.io/coveralls/user/repo/master.png?style=flat-square
[coveralls]: https://coveralls.io/github/user/repo
npm package: @nfort/logistics-icons
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Author: GPB Team
Latest version: 6.11.8

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

* React
* Styled-components
* Typescript



```
import { EmailIcon, GpbClientIcon } from '@holism/icons';
```
npm package: @nfort/react-skylight
Description: A react component for modals and dialogs.
Author: Marcio Gasparotto
Latest version: 0.6.6

react-skylight
==============

React SkyLight is a simple react component for modals and dialogs. Powerful, lightweight and customizable design.

[React skylight DEMOS and DOCS.](http://marcio.github.io/react-skylight)

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

```sh
npm install react-skylight --save
#Or
yarn add react-skylight
```

Features
--------

- Very simple modal/dialog
- Animation support
- Stateless
- Callback before open
- Callback after open
- Callback before close
- Callback after close
- Callback on overlay click
- All styles can be overridden


How to use
--------------------

[React skylight DEMOS and DOCS.](http://marcio.github.io/react-skylight)



##Enjoy!



## Release History
 * 2018-04-03   v0.5.1   Change dialog style height to minHeight, react 16 support, remove unused dependencies
 * 2017-09-20   v0.5.0   Add animation, ESC to close, title as component and and some fixes
 * 2017-05-23   v0.4.2   Solve propTypes warnings, and some fixes
 * 2016-08-31   v0.4.1   Polyfill Object.assign() to works in IE
 * 2016-04-27   v0.4.0   Fix issue #35 (numeric string value for CSS property), up to react 15.0.1 and merged pull request to support Stateless (thanks @darthtrevino)
 * 2016-01-09   v0.3.0   Rewrite to ES2015, overlay callback and new site.
 * 2015-04-08   v0.2.0   Improvements
 * 2015-02-03   v0.1.4   Changed skylight.js to skylight.jsx and adjust of namespace
npm package: @nfort/uber-logistics-core
Description: logistics-core React component
Author: nfort
Latest version: 1.0.0

# logistics-core

[![Travis][build-badge]][build]
[![npm package][npm-badge]][npm]
[![Coveralls][coveralls-badge]][coveralls]

# Почему существуют 2 репозитория logistics-core?
Если разрабатывать в рамках одного репозитория, то получим смесь компонентов которые используются как в старом, так и в новом подходе что в свою очередь затрудняет понимания где какой компонент должен использоваться

[build-badge]: https://img.shields.io/travis/user/repo/master.png?style=flat-square
[build]: https://travis-ci.org/user/repo

[npm-badge]: https://img.shields.io/npm/v/npm-package.png?style=flat-square
[npm]: https://www.npmjs.org/package/npm-package

[coveralls-badge]: https://img.shields.io/coveralls/user/repo/master.png?style=flat-square
[coveralls]: https://coveralls.io/github/user/repo
npm package: @nfpocket/v-calendar
Description: A calendar and date picker plugin for Vue.js. Forked because my problem is too specific to be solved by the original author.
Author: Nathan Reyes
Latest version: 3.1.5

# USE THE ORIGINAL [v-calendar](https://www.npmjs.com/package/v-calendar)

##  DO NOT USE THIS VERSION! THIS IS JUST A FORK TO FIX A VERY SPECIFIC PROBLEM I HAD THAT IS WAY OUT OF SCOPE FOR THE MAIN PACKAGE
npm package: @nfq/adition-switch
Description: Soap cmdlet for NFQ
Author: .NFQ | Christoph Kruppe
Latest version: 0.0.1

<div id="top"></div>

# @nfq/svg-to-react

[![EsLint](https://github.com/nfqde/nfq-svg-to-react/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-svg-to-react/actions/workflows/eslint.yml)

---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
3. [Usage](#usage)
4. [Props](#props)
5. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

This project, `@nfq/svg-to-react`, is a powerful tool that allows you to convert SVG images into React components. It's built with Node.js and TypeScript. The main functionality of this package is to take a directory or a file of SVG images as input, and output a directory of React components. This is particularly useful for projects where SVG images are used extensively and need to be managed efficiently.
The package provides a command line interface for easy use. It also supports different templates for generation, including 'typescript', 'jsdoc-typescript', and 'legacy'. This allows you to choose the format that best suits your project's needs.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To the package follow the next steps:

### Installation

To install the package run
```sh
npm install -g <Project name>
```
if you are on yarn
```sh
yarn add --global <Project name>
```
or on pnpm
```sh
pnpm install -g <Project name>
```

---

## Usage

You can use this package to convert SVG files to React components. You can specify the input directory or file, the output directory, and the template to use for generation. The available templates are 'typescript', 'jsdoc-typescript', and 'legacy'.

For example, to convert all SVG files in the `icons` directory and output them as TypeScript React components in the `components` directory, you would use the following command:

```sh
svgToReact --src ./icons --out ./components --template typescript
```

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

This package provides a command line interface with the following options:

- `src`: The input directory or file.
- `out`: The output directory.
- `template`: The generation type. It has to be one of the following options: ['typescript', 'jsdoc-typescript', 'legacy'].

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/autobind
Description: <div id="top"></div>
Author: .NFQ | Christoph Kruppe
Latest version: 1.1.4

<div id="top"></div>

# @nfq/autobind

[![EsLint](https://github.com/nfqde/nfq-autobind/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-autobind/actions/workflows/eslint.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)


---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
3. [Usage](#usage)
4. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

The `@nfq/autobind` package provides a decorator function for automatically binding class methods to the instance of the class. This ensures the correct context (`this` value) is maintained, especially useful when passing methods as callbacks. It is designed to streamline method binding in JavaScript and TypeScript applications, particularly beneficial in React components and other class-based structures.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To install the package locally follow the next steps:

### Installation

To install the package run
```sh
npm install @nfq/autobind
```
if you are on yarn
```sh
yarn add @nfq/autobind
```
or on pnpm
```sh
pnpm install @nfq/autobind
```

---

## Usage

The @autobind decorator can be used in class components to ensure that methods are bound to the instance of the class. This is especially useful when passing methods as callbacks.

```ts
import {autobind} from '@nfq/autobind';

class MyClass {
  @autobind
  myMethod() {
    // This method is automatically bound to instances of MyClass.
  }
}
```

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/next-fonts
Description: Next.js plugin to load and preload fonts
Author: .NFQ | Christoph Kruppe
Latest version: 1.7.2

<div id="top"></div>

# @NFQ Next.Js Fonts

[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/license/mit/)
[![EsLint](https://github.com/nfqde/nfq-next-fonts/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-next-fonts/actions/workflows/eslint.yml)
[![Horusec](https://github.com/nfqde/nfq-next-fonts/actions/workflows/horusec.yml/badge.svg)](https://github.com/nfqde/nfq-next-fonts/actions/workflows/horusec.yml)
[![Cypress](https://github.com/nfqde/nfq-next-fonts/actions/workflows/cypress.yml/badge.svg)](https://github.com/nfqde/nfq-next-fonts/actions/workflows/cypress.yml)

---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
    2. [PeerDependencies](#peerdependencies)
3. [Usage](#usage)
4. [Props](#props)
5. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

An small package that adds auto @font-face generation to your next.js project. It also adds the preview link tags to the head of the document.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To setup the project locally follow the next steps:

### Installation

To install the package run
```sh
npm install <Project name>
```
if you are on yarn
```sh
yarn add <Project name>
```
or on pnpm
```sh
pnpm install <Project name>
```
   
### PeerDependencies:

The following PeerDependencies are needed so the package does work:

- typescript >= 4.9.5

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Usage

Use this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.

_For more examples, please refer to the [Documentation](https://example.com)_

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

Use this space for prop tables if you make an react module or for params if you create js module. Or use it for arguments if you create an cli.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/payload-lexical-parser
Description: An react parser for payloads lexical editor
Author: .NFQ | Christoph Kruppe
Latest version: 1.2.1

<div id="top"></div>

# Project name

[![EsLint](https://github.com/nfqde/nfq-npm-modules-template/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-npm-modules-template/actions/workflows/eslint.yml)

---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
    2. [PeerDependencies](#peerdependencies)
3. [Usage](#usage)
4. [Props](#props)
5. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Labore adipisicing nostrud nostrud consequat in excepteur ullamco veniam Lorem nostrud. Do laborum laboris nulla quis duis dolor est non pariatur irure esse occaecat. Id anim anim sint sunt nulla officia velit occaecat enim consectetur. Dolore occaecat ex ad occaecat consequat. Nulla anim nostrud excepteur nulla commodo dolor aute duis veniam culpa sit quis. Irure et irure enim cillum irure eiusmod nostrud exercitation esse ut minim.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To setup the project locally follow the next steps:

### Installation

To install the package run
```sh
npm install <Project name>
```
if you are on yarn
```sh
yarn add <Project name>
```
or on pnpm
```sh
pnpm install <Project name>
```
   
### PeerDependencies:

The following PeerDependencies are needed so the component does work:

- \<dependency> >= \<version>

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Usage

Use this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.

_For more examples, please refer to the [Documentation](https://example.com)_

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

Use this space for prop tables if you make an react module or for params if you create js module. Or use it for arguments if you create an cli.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/platform-dependencies
Description: yarn fork Module to specify dependencies for different operating systems.
Author: Christoph Kruppe
Latest version: 0.1.2

# NPM Platform Dependencies
Small script that allows you to specify OS-specific dependencies in your package.json and install them only in that OS.

Install via:

`npm install npm-platform-dependencies`

## Specify your packages inside package.json

Specify the specific dependencies for each platform, like:

```
"darwinDependencies": {
    "nodobjc": "latest"
},
"win32Dependencies": {
    "edge": "latest"
}
```

Then run:

```
npmpd
```

And that's it! Depending the platform where you run the command, it will install one or the other (or nothing if linux).

## Use with npm install
To use it just after npm install, put this script on the scripts section of package.json

```
"postinstall": "npmpd"
```

## Append your own arguments to the install process
Simply add any arguments to the npmpd call to have them appended to the `npm install` process.
The example below shows how you could append the `--ignore-scripts` argument to the install process.
```
npmpd --ignore-scripts
```

Or append the arguments at the scripts section of package.json
```
"postinstall": "npmpd --ignore-scripts"
```

## Inside the code
Be sure to make your code detect the platform you are running on, or you will end up requiring things you don't have installed!

## Motivation
I came across a problem where it would be useful to specify platform specific dependencies. For instance, when trying to deal with addons that connect to specific
os frameworks (Cocoa, .NET...). This is an easy solution if you don't want to deal with building a native addon with [node-gyp](https://github.com/nodejs/node-gyp), if
the functionalities you need are already in different os specific packages.

Another use case would be when dealing with wrappers of os specific programs, and you want to link to one or the other depending the platform you run your program with.

## License

MIT License Copyright (c) 2016 Alberto Fernandez
npm package: @nfq/react-form
Description: <div id="top"></div>
Author: .NFQ | Christoph Kruppe
Latest version: 1.2.1

<div id="top"></div>

# Project name

[![EsLint](https://github.com/nfqde/nfq-react-form/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-react-form/actions/workflows/eslint.yml)

---

- [Project name](#project-name)
  - [Description: ](#description-)
  - [Getting started](#getting-started)
    - [Installation](#installation)
    - [PeerDependencies:](#peerdependencies)
  - [Usage](#usage)
  - [Props](#props)
  - [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Labore adipisicing nostrud nostrud consequat in excepteur ullamco veniam Lorem nostrud. Do laborum laboris nulla quis duis dolor est non pariatur irure esse occaecat. Id anim anim sint sunt nulla officia velit occaecat enim consectetur. Dolore occaecat ex ad occaecat consequat. Nulla anim nostrud excepteur nulla commodo dolor aute duis veniam culpa sit quis. Irure et irure enim cillum irure eiusmod nostrud exercitation esse ut minim.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To setup the project locally follow the next steps:

### Installation

To install the package run
```sh
npm install @nfq/react-form
```
if you are on yarn
```sh
yarn add @nfq/react-form
```
or on pnpm
```sh
pnpm install @nfq/react-form
```
   
### PeerDependencies:

The following PeerDependencies are needed so the component does work:

- mobx >= 6.0.0
- mobx-react-lite >= 4.0.0
- react >= 19.0.0
- react-dom >= 19.0.0

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Usage

Use this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.

_For more examples, please refer to the [Documentation](https://example.com)_

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

Use this space for prop tables if you make an react module or for params if you create js module. Or use it for arguments if you create an cli.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/react-native-mock-render
Description: A fork of react-native-mock-render that renders components and mocks also the Touchable class
Author: Root Insurance Co. Dev Team
Latest version: 0.1.6

# react-native-mock-render

A fork of [react-native-mock](https://github.com/RealOrangeOne/react-native-mock) that renders components

## Requirements
- Node.js 4+
- The latest version of react-native

## Installation

```bash
npm i react-native-mock-render --save-dev
```

```js
/* file-that-runs-before-all-of-my-tests.js */

// This will mutate `react-native`'s require cache with `react-native-mock`'s.
require('react-native-mock-render/mock'); // <-- side-effects!!!
```

### Jest

Jest [doesn't support](https://github.com/Root-App/react-native-mock-render/issues/23) `require.cache`, so the correct way to do the mocking is using `jest.mock('react-native', () => require('react-native-mock-render'), {virtual: true})` in your tests setup file.

## Why?

We wanted to be able deeply render React Native components in our integration tests and already used `react-native-mock`.

### Contributors

- [Root Insurance's Dev Team](https://joinroot.com)

### [react-native-mock](https://github.com/RealOrangeOne/react-native-mock) Core Contributors
- [Jake Howard](https://github.com/RealOrangeOne)
- [Leland Richardson](https://github.com/lelandrichardson) (Original Creator)
npm package: @nfq/svg-to-react
Description: Package to batch create react components from svg images
Author: .NFQ | Christoph Kruppe
Latest version: 3.0.3

<div id="top"></div>

# @nfq/svg-to-react

[![EsLint](https://github.com/nfqde/nfq-svg-to-react/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-svg-to-react/actions/workflows/eslint.yml)

---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
3. [Usage](#usage)
4. [Props](#props)
5. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

This project, `@nfq/svg-to-react`, is a powerful tool that allows you to convert SVG images into React components. It's built with Node.js and TypeScript. The main functionality of this package is to take a directory or a file of SVG images as input, and output a directory of React components. This is particularly useful for projects where SVG images are used extensively and need to be managed efficiently.
The package provides a command line interface for easy use. It also supports different templates for generation, including 'typescript', 'jsdoc-typescript', and 'legacy'. This allows you to choose the format that best suits your project's needs.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To the package follow the next steps:

### Installation

To install the package run
```sh
npm install -g <Project name>
```
if you are on yarn
```sh
yarn add --global <Project name>
```
or on pnpm
```sh
pnpm install -g <Project name>
```

---

## Usage

You can use this package to convert SVG files to React components. You can specify the input directory or file, the output directory, and the template to use for generation. The available templates are 'typescript', 'jsdoc-typescript', and 'legacy'.

For example, to convert all SVG files in the `icons` directory and output them as TypeScript React components in the `components` directory, you would use the following command:

```sh
svgToReact --src ./icons --out ./components --template typescript
```

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

This package provides a command line interface with the following options:

- `src`: The input directory or file.
- `out`: The output directory.
- `template`: The generation type. It has to be one of the following options: ['typescript', 'jsdoc-typescript', 'legacy'].

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/telefonica-component-libary
Description: <div id="top"></div>
Author: .NFQ | Christoph Kruppe
Latest version: 1.26.5

<div id="top"></div>

# Project name

[![EsLint](https://github.com/nfqde/nfq-npm-modules-template/actions/workflows/eslint.yml/badge.svg)](https://github.com/nfqde/nfq-npm-modules-template/actions/workflows/eslint.yml)

---

1. [Description](#description)
2. [Getting started](#getting-started)
    1. [Installation](#installation)
    2. [PeerDependencies](#peerdependencies)
3. [Usage](#usage)
4. [Props](#props)
5. [Support](#support)

---

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Labore adipisicing nostrud nostrud consequat in excepteur ullamco veniam Lorem nostrud. Do laborum laboris nulla quis duis dolor est non pariatur irure esse occaecat. Id anim anim sint sunt nulla officia velit occaecat enim consectetur. Dolore occaecat ex ad occaecat consequat. Nulla anim nostrud excepteur nulla commodo dolor aute duis veniam culpa sit quis. Irure et irure enim cillum irure eiusmod nostrud exercitation esse ut minim.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Getting started

To setup the project locally follow the next steps:

### Installation

To install the package run
```sh
npm install <Project name>
```
if you are on yarn
```sh
yarn add <Project name>
```
or on pnpm
```sh
pnpm install <Project name>
```
   
### PeerDependencies:

The following PeerDependencies are needed so the component does work:

- \<dependency> >= \<version>

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Usage

Use this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.

_For more examples, please refer to the [Documentation](https://example.com)_

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Props

Use this space for prop tables if you make an react module or for params if you create js module. Or use it for arguments if you create an cli.

<p align="right">(<a href="#top">back to top</a>)</p>

---

## Support

Christoph Kruppe - [https://github.com/ckruppe] - c.kruppe@nfq.de  

<p align="right">(<a href="#top">back to top</a>)</p>
npm package: @nfq/test-reporter
Description: Sends CI tests to an report endpoint
Author: .NFQ | Christoph Kruppe
Latest version: 1.1.5


# @nfq/test-reporter

# Table of Contents
- [Description](#description)
- [Installation](#installation)
- [PeerDependencies](#peerdependencies)
- [Configuration](#configuration)
  - [cypress.json](#cypressjson)
  - [package.json](#packagejson)
  - [.env](#env)
- [Contributions](#contributions)
- [Licence](#licence)
- [Questions](#questions)

## Description: [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
This is an module to report test data to an server endpoint.
## Installation:
To install the package run
```sh
npm install @nfq/test-reporter
```
if you are in yarn
```sh
yarn add @nfq/test-reporter
```
or on pnpm
```sh
pnpm install @nfq/test-reporter
```
---
---
## PeerDependencies:
- @cypress/code-coverage >= 3
- babel-plugin-istanbul >= 6
- cypress >= 8
- mochawesome >= 6
- nyc >= 15
---
---
## Configuration:
Configure your cypress to do code coverage and everything is set.

---
### cypress.json:

Add following keys to your cypress.json config.

example:

```json
"reporter": "mochawesome",
"reporterOptions": {
    "reportDir": "cypress/reports",
    "json": true,
    "html": false,
    "timestamp": "yyyymmddHHMMssl"
},
```
---
### package.json

Setup your test commands like you want to have them and make sure to call the reporter afterwards.

example:
```json
{
    ...
    "scripts": {
        "test:cypress:ct": "pnpx cross-env NODE_ENV=test FEATURE_ENV=test pnpx cypress run-ct",
        "test:cypress:integration": "pnpx cross-env NODE_ENV=test FEATURE_ENV=test pnpx cypress run",
        "test": "pnpm run test:cypress:integration && pnpm run test:cypress:ct && pnpx nfqReport"
    },
    ...
}
```
---
### .env

To configure the test reporter you have to create an .env file with the following keys:

example:
```env
REPORTER_KEY=identification key //Informations to our intern data can be asked from the author of this package
REPORTER_URL=reporterurl //Informations to our intern data can be asked from the author of this package
REPORT_NAME=report name and page title
```
---
---
## Contributions:
.NFQ | Christoph Kruppe

---
---
## License:
The licence used is: `MIT`
Click on licence badge for licence details:
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

---
---
## Questions:
If you have any further questions please contact the following email address:
email: c.kruppe@nfq.de
npm package: @nfrasser/milligram
Description: A minimalist CSS framework.
Author: CJ Patoilo
Latest version: 1.4.1-1

<a align="center" href="https://milligram.io"><img width="100%" src="https://milligram.io/images/thumbnail.png" alt="Milligram - A minimalist CSS framework."></a>

> A minimalist CSS framework.

[![Travis Status](https://travis-ci.org/milligram/milligram.svg?branch=master)](https://travis-ci.org/milligram/milligram?branch=master)
[![AppVeyor Status](https://ci.appveyor.com/api/projects/status/xcm8meymwerq0r82?svg=true)](https://ci.appveyor.com/project/cjpatoilo/milligram)
[![Codacy Status](https://img.shields.io/codacy/grade/848fb4bd6902434fab0bcfb5461284fe/master.svg)](https://www.codacy.com/app/milligram/milligram/dashboard)
[![Dependencies Status](https://david-dm.org/milligram/milligram.svg)](https://david-dm.org/milligram/milligram)
[![Version Status](https://badge.fury.io/js/milligram.svg)](https://www.npmjs.com/package/milligram)
[![Download Status](https://img.shields.io/npm/dt/milligram.svg)](https://www.npmjs.com/package/milligram)
[![Gitter Chat](https://img.shields.io/badge/gitter-join_the_chat-4cc61e.svg)](https://gitter.im/milligram/milligram)
[![Setup Automated](https://img.shields.io/badge/setup-automated-blue?logo=gitpod)](https://gitpod.io/from-referrer/)

## Why it's awesome

Milligram provides a minimal setup of styles for a fast and clean starting point. Just it! **Only 2kb gzipped!** It's not about a UI framework. Specially designed for better performance and higher productivity with fewer properties to reset resulting in cleaner code. Hope you enjoy!

## Download

**Install with Bower**

```sh
$ bower install milligram
```

**Install with npm**

```sh
$ npm install milligram
```

**Install with Yarn**

```sh
$ yarn add milligram
```

## Table of Contents

- [Getting Started](https://milligram.io/#getting-started)
- [Typography](https://milligram.io/#typography)
- [Blockquotes](https://milligram.io/#blockquotes)
- [Buttons](https://milligram.io/#buttons)
- [Lists](https://milligram.io/#lists)
- [Forms](https://milligram.io/#forms)
- [Tables](https://milligram.io/#tables)
- [Grids](https://milligram.io/#grids)
- [Code](https://milligram.io/#code)
- [Utilities](https://milligram.io/#utilities)
- [Tips](https://milligram.io/#tips)
- [Browser Support](https://milligram.io/#browser-support)
- [Examples](https://milligram.io/#examples)

## Contributing

Want to contribute? Follow these [recommendations](https://github.com/milligram/milligram/contribute).

## License

Designed with ♥ by [CJ Patoilo](https://twitter.com/cjpatoilo). Licensed under the [MIT License](https://cjpatoilo.com/license).
npm package: @nfrasser/simple-html-tokenizer
Description: Simple HTML Tokenizer is a lightweight JavaScript library that can be used to tokenize the kind of HTML normally found in templates.
Latest version: 0.5.11-4

# Simple HTML Tokenizer [![Build Status](![CI](https://github.com/tildeio/simple-html-tokenizer/workflows/CI/badge.svg))](https://github.com/tildeio/simple-html-tokenizer/actions?query=workflow%3ACI)

Simple HTML Tokenizer is a lightweight JavaScript library that can be
used to tokenize the kind of HTML normally found in templates. It can be
used to preprocess templates to change the behavior of some template
element depending upon whether the template element was found in an
attribute or text.

It is not a full HTML5 tokenizer. It focuses on the kind of HTML that is
used in templates: content designed to be inserted into the `<body>`
and without `<script>` tags.

In particular, Simple HTML Tokenizer does not handle many states from
the [HTML5 Tokenizer Specification][1]:

* Any states involving `CDATA` or `RCDATA`
* Any states involving `<script>`
* Any states involving `<DOCTYPE>`
* The bogus comment state

It also passes through character references, instead of trying to
tokenize and process them, because the preprocessed templates will
ultimately be parsed by a real browser context.

At the moment, there are some error states specified by the tokenizer
spec that are not handled by Simple HTML Tokenizer. Ultimately, I plan
to support all error states, as well as provide information about
tokenizer errors in debug mode.

[1]: http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html

# Usage

You can tokenize HTML:

```js
var tokens = HTML5Tokenizer.tokenize("<div id='foo' href=bar class=\"bat\">");

var token = tokens[0];
token.tagName     //=> "div"
token.attributes  //=> [["id", "foo"], ["href", "bar"], ["class", "bat"]]
token.selfClosing //=> false
```

## Building and running the tests

```bash
npm install
npm test
```
npm package: @nfreear/my-map
Description: Easily embed a map powered by Leaflet.
Author: Nick Freear
Latest version: 1.6.0


[![Node.js CI][ci-img]][ci]
[![NPM package][npm-img]][npm]
[![Leaflet 1.9.4][leaflet-img]][leaflet]

# my-map #

Easily embed a map powered by [Leaflet][]. Includes [accessibility][myp] and [translation][myp] Leaflet plugins.

* [nfreear.github.io/elements/demo][demo]
* Demo on [CodePen][]

## Usage

Available on the [Unpkg][] CDN:

```html
<script src="https://unpkg.com/@nfreear/my-map@1" type="module"></script>

<my-map
  latlng="51.505,-0.09"
  zoom="13"
  geojson="./data/landmarks.geo.json"
>
  <marker latlng="51.505, -0.09" hidden>Hello, I'm a popup!</marker>

  <p> My map description ... </p>
</my-map>
```

<!--
```
<custom-element-demo>
<template>
  <script src="https://unpkg.com/@nfreear/my-map@1" type="module"></script>

  <my-map latlng="51.505,-0.09" zoom="13">
    <marker latlng="51.505, -0.09" hidden>Hello, I'm a popup!</marker>

    <p> My map description ... </p>
  </my-map>
</template>
</custom-element-demo>
```
-->


## License

* License: [MIT][].

[ci]: https://github.com/nfreear/elements/actions/workflows/node.js.yml
[ci-img]: https://github.com/nfreear/elements/actions/workflows/node.js.yml/badge.svg
[leaflet-img]: https://img.shields.io/badge/leaflet-1.9.4-green.svg?style=flat
[codepen]: https://codepen.io/nfreear/pen/KKeJKov
[demo]: https://nfreear.github.io/elements/demo/
[mit]: https://github.com/nfreear/elements/blob/main/LICENSE.txt
[npm]: https://www.npmjs.com/package/@nfreear/my-map
[npm-img]: https://img.shields.io/npm/v/%40nfreear/my-map
[unpkg]: https://unpkg.com
  "A fast, global content delivery network for everything on npm"
[up-cdn]: https://unpkg.com/@nfreear/my-map@1/index.js
[skypack]: https://cdn.skypack.dev
  "A JavaScript Delivery Network for modern web apps"
[leaflet]: https://leafletjs.com/
[myp]: https://github.com/nfreear/leaflet.plugins
  "A collection of accessibility and localisation/ translation plugins for Leaflet"
npm package: @nfriend/nfriendact
Description: Please see [https://gitlab.com/nfriend/nfriendact](https://gitlab.com/nfriend/nfriendact) for information about this package!
Latest version: 1.0.4

# @nfriend/nfriendact

Please see [https://gitlab.com/nfriend/nfriendact](https://gitlab.com/nfriend/nfriendact) for information about this package!
npm package: @nfscratch/cli
Description: Node.js version manager with support for compiling its source code from scratch with custom parameters.
Author: Victor Queiroz
Latest version: 0.0.13

# Node.js From Scratch

Node.js version manager with support for compiling its source code from scratch with custom parameters.

## Installation

If you do not define `NFS_DIR`, NFS will try to do that for you. It is a good idea to define it for the best results. For example, you can put this at the top of your `.bashrc` (or `.zshrc`, `~/.profile`, ...) file:

```sh
NFS_DIR="${HOME}/.nfs"
export NFS_DIR
```

NFS does not aim to be a replacement of [NVM](https://nvm.sh). You should have a pre-installed version of Node.js. Install NFS using npm:

```sh
npm install -g @nfscratch/cli
nfs-js init # Create the `environment.sh` file inside `NFS_DIR`
```

If you want NFS to be loaded automatically when you open a new shell, you can add the following line after `NFS_DIR` to your shell profile:

```sh
[ -f "${NFS_DIR}/environment.sh" ] && source "${NFS_DIR}/environment.sh"
```

## Usage

```sh
nfs-js install '^22' --lts --jobs="$(nproc)"
```
npm package: @nft-blender/ual-anchor
Description: This authenticator is meant to be used with [Anchor](https://github.com/greymass/anchor/) and [Universal Authenticator Library](https://github.com/EOSIO/universal-authenticator-library). When used in combination with them, it gives developers the ability 
Author: Greymass
Latest version: 1.2.0

# UAL for Anchor Authenticator

This authenticator is meant to be used with [Anchor](https://github.com/greymass/anchor/) and [Universal Authenticator Library](https://github.com/EOSIO/universal-authenticator-library). When used in combination with them, it gives developers the ability to request transaction signatures through Anchor using the common UAL API.

## Supported Environments

- The Anchor Authenticator only supports both Desktop and Mobile environments

## Getting Started

`yarn add ual-anchor`

#### Dependencies

You must use one of the UAL renderers below.

React - `ual-reactjs-renderer`
PlainJS - `ual-plainjs-renderer`

#### Basic usage and configuration with React

```javascript
import { Anchor } from 'ual-anchor'
import { UALProvider, withUAL } from 'ual-reactjs-renderer'

const eos = {
  chainId: 'aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906',
  rpcEndpoints: [{
    protocol: 'https',
    host: 'eos.greymass.com',
    port: '443',
  }]
}

const App = (props) => <div>{JSON.stringify(props.ual)}</div>
const AppWithUAL = withUAL(App)

const anchor = new Anchor([eos], {
  // Required: The app name, required by anchor-link. Short string identifying the app
  appName: 'my-example-dapp',
  // Optional: a @greymass/eosio APIClient from eosjs for both your use and to use internally in UAL
  // client = new APIClient({ provider }),
  // Optional: a JsonRpc instance from eosjs for your use
  // rpc: new JsonRpc(),
  // Optional: The callback service URL to use, defaults to https://cb.anchor.link
  // service: 'https://cb.anchor.link',
  // Optional: A flag to disable the Greymass Fuel integration, defaults to false (enabled)
  // disableGreymassFuel: false,
  // Optional: An account name on a Fuel enabled network to specify as the referrer for transactions
  // fuelReferrer: 'teamgreymass',
  // Optional: A flag to enable the Anchor Link UI request status, defaults to true (enabled)
  // requestStatus: true,  
  // Optional: Whether or not to verify the signatures during user login, defaults to false (disabled)
  // verifyProofs: false,
})

<UALProvider chains={[exampleNet]} authenticators={[anchor]}>
  <AppWithUAL />
</UALProvider>
```

## License

[MIT](https://github.com/EOSIO/ual-anchor/blob/develop/LICENSE)
npm package: @nft-open-marketplace/interface
Description: Contract ABI and interfaces for nft-open-marketplace project
Author: Eugene Perminov
Latest version: 0.5.0

# NFT Open Marketplace: contracts typechains and ABIs

Package contains nft-open-marketplace contracts and ABI.
These files are autogenerated by hardhat in @nft-open-marketplace/blockchain and copied to this package by script - all `src` files except `index.ts`. `index.ts` should be updated manually if needed.

## To publish updated interface

0. Update `CHANGELOG.md`
1. Update `package.json`
2. Update `src/index.ts` if needed
3. run
   `npm login`
   `npm publish`