open-index/open-npm huggingface dataset:
npm package: @fp51/eslint-config-redux-saga
Description: fp51 javascript eslint rules for redux-saga
Author: fp51 developers
Latest version: 1.0.0

# @fp51/eslint-config-redux-saga

## Install

Add this dependency to your repository and eslint peer-dependency:

```bash
npm add --save-dev @fp51/eslint-config-redux-saga
```

## Usage

Create a .eslintrc file in your project root with this content

```json
{
  "extends": [
    "@fp51/eslint-config-redux-saga"
  ]
}
```
npm package: @fp51/store-devtools
Description: Devtools for @fp51/store
Author: fp51 developers
Latest version: 2.0.1

@fp51/store-devtools
=======================

Devtools for `@fp51/store`, a lightweight Javascript store library.

Use `@fp51/store-devtools` to debug your store with [ReduxDevtools
extension](https://github.com/zalmoxisus/redux-devtools-extension).

[📖 Documentation](https://fp51.github.io/store-library/packages/store-devtools/)

# Usage

```
npm install @fp51/store @fp51/store-devtools
```

`@fp51/store` is a peer-dependency

# Example

```typescript
import * as Store from '@fp51/store';
import { withDevtools } from '@fp51/store-devtools';

const store = withDevtools({
  name: 'my store',
})(Store.create(() => 2)());
```

Instead of classic `Redux` action type, it will try to use the reducer function
name to log the change.

```typescript
store.apply(
  function multiplyByTwo(state: number) {
    return state * 2;
  }
)();
```

Devtools will use `multiplyByTwo` as change type here.
npm package: @fp8/yaml-templater
Description: Yaml Templater
Author: marcos.lin@farport.co
Latest version: 0.1.0

# yaml-templater

```
Usage: yaml-templater [--apply-array] [--data data.yaml] <main yaml> <yaml templates>
```

## Install

```
yarn add -D @farport/yaml-templater
```

This should create a `.bin/yaml-templater` executable in your `node_modules`.

## Test Run

To do a test run, do:

```bash
# Show Help
yarn cli --help

# The result should be test/data/config-merged.yaml
FP8PROJKEY=TKuNFwIosI yarn cli --data test/data/data.yaml test/data/config-a.yaml test/data/config-b.template.yaml
```
npm package: @fpaboim/now-sapper
Description: ZEIT Now 2.0 builder for Sapper with SSR enabled
Author: Thomas Ghysels
Latest version: 0.38.1

# now-sapper

ZEIT Now 2.0 builder for Sapper with SSR enabled

## What's in it for you?

* [x] Deploy your Sapper app in 30 seconds.
* [x] Serve all static assets from a CDN.

## Basic usage

You must make 3 changes to your project to get started:

1. Configure `now-sapper` as builder in `now.json`
2. Export the server instance in `src/server.js`
3. Ignore the local build folder `__sapper__`

Check out this [demo project](https://github.com/beyonk-adventures/now-sapper-demo) that uses this builder. It can be used as a template, or a way to verify correct usage of the following instructions.

##### 1. Configure `now-sapper` as builder in `now.json`

```json
{
  "version": 2,
  "builds": [{ "src": "package.json", "use": "now-sapper" }]
}
```

##### 2. Export the server instance in `src/server.js`

```js
const app = express() // or polka()
export default app
```

##### 3. Ignore the local build folder `__sapper__`

Example `.nowignore` :
```
__sapper__
node_modules
```

Consider also ignoring the `cypress` folder if you are not running tests.

## Options

##### Node.js version

You can change the Node.js version with the engines field.

Example `package.json`
```json
{
  "engines": {
    "node": "12.x"
  }
}
```

##### No-build usage

Useful if you are building the project on CI, and then want to just push the compiled source.

Recommended `.nowignore`:
```
__sapper__/dev
__sapper__/export
cypress
node_modules
```

Example `now.json`
```json
{
  "version": 2,
  "builds": [
    {
      "src": "package.json",
      "use": "now-sapper",
      "config": {
        "build": false
      }
    }
  ]
}
```

## Troubleshooting

##### Using `fetch` serverside

Use absolute URLs, like this: https://github.com/thgh/now-sapper/issues/8#issuecomment-548860177

##### `now dev` doesn't work

True story, use `sapper dev` instead: https://github.com/thgh/now-sapper/issues/4#issuecomment-536189926

## Changelog

Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.

## Contributing

Contributions and feedback are very welcome.

This project aims to enable developers to deploy to Now with minimal config. New features should be in line with other builders like [now-next](https://github.com/zeit/now/tree/master/packages/now-next).
npm package: @fpapado/blurhash
Description: Encoder and decoder for the Wolt BlurHash algorithm. Fork of blurhash, to export ES modules.
Author: fpapado
Latest version: 1.1.4

# blurhash

[![NPM Version](https://img.shields.io/npm/v/blurhash.svg?style=flat)](https://npmjs.org/package/blurhash)
[![NPM Downloads](https://img.shields.io/npm/dm/blurhash.svg?style=flat)](https://npmjs.org/package/blurhash)

> JavaScript encoder and decoder for the [Wolt BlurHash](https://github.com/woltapp/blurhash) algorithm

## Install

```sh
npm install --save blurhash
```

See [react-blurhash](https://github.com/woltapp/react-blurhash) to use blurhash with React.

## API

### `decode(blurhash: string, width: number, height: number, punch?: number) => Uint8ClampedArray`

> Decodes a blurhash string to pixels

#### Example

```js
import { decode } from "blurhash";

const pixels = decode("LEHV6nWB2yk8pyo0adR*.7kCMdnj", 32, 32);

const canvas = document.createElement("canvas");
const ctx = canvas.getContext("2d");
const imageData = ctx.createImageData(width, height);
imageData.data.set(pixels);
ctx.putImageData(imageData, 0, 0);
document.body.append(canvas);
```

### `encode(pixels: Uint8ClampedArray, width: number, height: number, componentX: number, componentY: number) => string`

> Encodes pixels to a blurhash string

```js
import { encode } from "blurhash";

const loadImage = async src =>
  new Promise((resolve, reject) => {
    const img = new Image();
    img.onload = () => resolve(img);
    img.onerror = (...args) => reject(args);
    img.src = src;
  });

const getImageData = image => {
  const canvas = document.createElement("canvas");
  canvas.width = image.width;
  canvas.height = image.height;
  const context = canvas.getContext("2d");
  context.drawImage(image, 0, 0);
  return context.getImageData(0, 0, image.width, image.height);
};

const encodeImageToBlurhash = async imageUrl => {
  const image = await loadImage(imageUrl);
  const imageData = getImageData(image);
  return encode(imageData.data, imageData.width, imageData.height, 4, 4);
};
```

### `isBlurhashValid(blurhash: string) => { result: boolean; errorReason?: string }`

```js
import { isBlurhashValid } from "blurhash";

const validRes = isBlurhashValid("LEHV6nWB2yk8pyo0adR*.7kCMdnj");
// { result: true }

const invalidRes = isBlurhashValid("???");
// { result: false, errorReason: "The blurhash string must be at least 6 characters" }
```
npm package: @fpapado/react-feather
Description: React component for Feather icons. Fork of react-feather for convenience.
Author: fpapado
Latest version: 2.1.0

## React Feather Icons

[![npm](https://img.shields.io/npm/v/@fpapado/react-feather.svg)](https://www.npmjs.com/package/@fpapado/react-feather)

Fork of [react-feather](https://github.com/carmelopullara/react-feather) with `microbundle` as the build step, and ES modules in the distribution.
Also has accessible defaults.

> Simply beautiful SVG icons as React components.
> Designed by [colebemis](https://github.com/colebemis/) on a 24x24 grid with an emphasis on functionality, consistency and simplicity.

### Installation
```shell
npm install @fpapado/react-feather
```

### Usage

ES module imports should get tree-shaken correctly by bundlers.
This means that you ship only the icons used.

```javascript
import { Camera } from 'react-feather';

const MyComponent = () => (
  <div>
    <span>Photos</span>
    <Camera purpose="decorative"/>
  </div>
)
```

Icons can be configured with props:
```javascript
  <Camera color="red" size={48} purpose="decorative "/>
```

### Purpose prop
The `purpose` prop is technically required, and allows the buttons to expose accessible defaults.
There are two options:
- "decorative", which marks the Icon to be ignored by assistive technologies;
- "standalone", which markes the Icon as content, and exposes it to assistive technlogies.

### Why would I use this?
- This package includes accessible defaults (`focusable="false"`, `role="img"`, handling of purpose being "decorative" or "standalone")
- `react-feather` requires path imports for bundle savings. That results in more verbose imports, and exposes distribution details. Imo, those should be opaque.
- I have not had much luck using such imports with Typescript.
- `react-feather` includes propTypes, which I do not need.

### Why would I not use this?
- You are fine with full-path imports and / or your setup supports them.
- NPM download count is important to you.
npm package: @fparchive/flashpoint-archive-darwin-x64
Description: This is the **x86_64-apple-darwin** binary for `@fparchive/flashpoint-archive`
Latest version: 0.13.7

# `@fparchive/flashpoint-archive-darwin-x64`

This is the **x86_64-apple-darwin** binary for `@fparchive/flashpoint-archive`
npm package: @fparchive/flashpoint-archive-win32-x64-msvc
Description: This is the **x86_64-pc-windows-msvc** binary for `@fparchive/flashpoint-archive`
Latest version: 0.13.7

# `@fparchive/flashpoint-archive-win32-x64-msvc`

This is the **x86_64-pc-windows-msvc** binary for `@fparchive/flashpoint-archive`
npm package: @fparchive/multi-zip-reader
Description: NodeJS library designed for fast access to arbitrary files across an arbitrary number of read only zip files. Supports reading back files as streams or into a returned buffer.
Author: Colin969
Latest version: 1.0.5

# Multi Zip Reader

NodeJS library designed for fast access to arbitrary files across an arbitrary number of read only zip files.
Supports reading back files as streams or into a returned buffer.

Supports:
- Zip64 files (>4GB)
- Store and Deflate compression
- Reading files into buffers or streams

## Example

```typescript
import { MultiZipReader } from '@fparchive/multi-zip-reader';

async function run() {
  // Loads all .zip files in the current directory
  const reader = new MultiZipReader();
  await reader.loadDirectory('./'); 

  // Read file back as a buffer
  const fileData = await reader.readFile("image.png")
  
  // Read file back as stream
  const stream = await reader.readFileStream("image.png");
  // No stream is an empty file, no content
  if (stream === null) {
  }
}
```
npm package: @fpelsser/label-manager
Description: Centran Label Manager
Author: Centran
Latest version: 3.12.2

# CentranLabelManager

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.0.4.

## Code scaffolding

Run `ng generate component component-name --project centran-label-manager` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project centran-label-manager`.
> Note: Don't forget to add `--project centran-label-manager` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build centran-label-manager` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build centran-label-manager`, go to the dist folder `cd dist/centran-label-manager` and run `npm publish`.

## Running unit tests

Run `ng test centran-label-manager` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @fphgov/nestjs-meilisearch
Description: Meilisearch integration for NestJS.
Latest version: 4.1.0

## About

This package is a simple wrapper around [meilisearch-js](https://github.com/meilisearch/meilisearch-js).

## Installation

This package requires `meilisearch` dependency to work properly.

```bash
yarn add @fphgov/nestjs-meilisearch meilisearch
```

## Getting Started

The simplest way to use `@fphgov/nestjs-meilisearch` is to use `MeiliSearchModule.forRoot` or `MeiliSearchModule.forRootAsync`

```typescript
import { Module } from '@nestjs-common';
import { MeiliSearchModule } from '@fphgov/nestjs-meilisearch';

@Module({
  imports: [
    MeiliSearchModule.forRoot({
      host: 'http://127.0.0.1:7700',
      apiKey: 'masterKey',
    }),
  ],

  // or async
  MeiliSearchModule.forRootAsync({
    useFactory: () => ({
      host: 'http://127.0.0.1:7700',
      apiKey: 'masterKey',
    }),
  }),
})
export class AppModule {}
```

use `@InjectMeiliSearch()` decorator in any injectables to get a `MeiliSearch` client inside class

```typescript
import { Injectable } from '@nestjs/common';
import { InjectMeiliSearch } from '@fphgov/nestjs-meilisearch';
import { MeiliSearch } from 'meilisearch';
@Injectable()
export class TestService {
  public constructor(
    @InjectMeiliSearch() private readonly meiliSearch: MeiliSearch,
  ) {}
}
```

You can also use `MeiliSearchService` to `add`,`update` and `delete` documents. I'm planning to add further operations to this service.

## License

Distributed under the MIT License. See `LICENSE` for more information.
npm package: @fphgov/typescript-eslint
Description: Egyedi ESLint konfiguráció TypeScript és NestJS projektekhez.
Latest version: 1.3.2

# @fphgov/typescript-eslint 🧩

Ez a csomag a @fphgov szervezet által összeállított alapértelmezett [ESLint](https://eslint.org/) szabálykészletet tartalmazza TypeScript projektekhez. Célja egységes kódkonvenciók biztosítása, egyszerű integráció mellett.

## 📦 Telepítés

Telepítsd a csomagot fejlesztési függőségként:

```bash
npm install --save-dev @fphgov/typescript-eslint
```

## ⚙️ Használat

A konfiguráció használatához hozz létre egy `eslint.config.mjs` fájlt a projekted gyökerében az alábbi tartalommal:

```ts
import fphgovConfig from '@fphgov/typescript-eslint';

export default [
  ...fphgovConfig,
];
```

Ez a konfiguráció támogatja az ESLint flat config struktúrát, és automatikusan alkalmazza a szervezet által ajánlott szabályokat.

## 🛠️ Szabályok testreszabása

Az `eslint.config.mjs` fájlban lehetőséged van tetszőleges szabály felülírására vagy kiegészítésére. Például:

```ts
import fphgovConfig from '@fphgov/typescript-eslint';

export default [
  ...fphgovConfig,
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'off',
      'no-console': 'warn',
    },
  },
];

```

## 📋 Követelmények

- Node.js 16 vagy újabb
- ESLint 9 vagy újabb
- TypeScript projekt

## 🔧 Példa a package.json beállításra

```json
{
  "name": "my-typescript-project",
  "version": "1.0.0",
  "type": "module",
  "scripts": {
    "lint": "eslint ./src/**/*.ts",
    "lint:fix": "eslint ./src/**/*.ts --fix"
  },
  "devDependencies": {
    "@fphgov/typescript-eslint": "^1.0.0",
    "eslint": "^9.0.0",
    "typescript": "^5.0.0"
  }
}
```

## 🧱 Példa a tsconfig.json beállításra

```json
{
  "compilerOptions": {
    "target": "ES2020",
    "module": "ESNext",
    "moduleResolution": "Node",
    "lib": ["ES2020", "DOM"],
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "sourceMap": true,
    "outDir": "./dist",
    "rootDir": "src",
    "baseUrl": "./"
  },
  "include": [
    "src"
  ],
  "exclude": [
    "node_modules",
    "data",
    "dist"
  ]
}
```