open-index/open-npm huggingface dataset:
npm package: @ha_tecno/live-id-sdk
Description: React Native SDK for Live ID
Author: Ewerton Vinicius Turco
Latest version: 2.19.7
Deprecated: Este pacote está depreciado. Use o novo @ha_tecno/react-native-sdk

## Instalação

```
npm i @ha_tecno/live-id-sdk react-native-vision-camera react-native-fs
cd ios && pod install
```

### Android

Abra o `AndroidManifest.xml` e adicione as seguintes linhas dentro da tag `manifest`:

```
    <uses-permission android:name="android.permission.CAMERA" />
```

### iOS

Open your project's Info.plist and add the following lines inside the outermost "dict" tag:

```
    <key>NSCameraUsageDescription</key>
    <string>$(PRODUCT_NAME) needs access to your Camera.</string>
```

## Uso Básico

### LifeCertificate

```ts
import React from "react";
import { LifeCertificate } from "@ha_tecno/live-id-sdk";

export const LifeCertificateScreen = () => {
  const UID = "321";
  return <LifeCertificate UID={UID} mock={false} />;
};
```

### FingerAuth

```ts
import React from "react";
import { FingerAuth } from "@ha_tecno/live-id-sdk";

export const FingerAuthScreen = () => {
  return (
  <FingerAuth
            UID={"321"}
            onSuccess={() => {})}
            isFocused={true}
            mock={false}
        />;
    );
};
```

### FingerRegister

```ts
import React from "react";
import { FingerRegister } from "@ha_tecno/live-id-sdk";

export const FingerRegisterScreen = () => {
  return (
  <FingerRegister
            UID={"321"}
            onSuccess={() => {})}
            isFocused={true}
            mock={false}
        />;
    );
};
```

### MultiFingerRegister

```ts
import React from "react";
import { MultiFingerRegister } from "@ha_tecno/live-id-sdk";

export const MultiFingerRegisterScreen = () => {
  return (
  <MultiFingerRegister
            UID={"321"}
            onSuccess={() => {})}
            isFocused={true}
            mock={false}
        />;
    );
};
```

## License

MIT
npm package: @haad/go-ipfs-dep
Description: Install the latest go-ipfs binary
Author: Juan Benet
Latest version: 0.4.5-beta.11
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

Install go-ipfs from npm as a dependency of your project
========================================================


[![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io)
[![](https://img.shields.io/badge/project-IPFS-blue.svg?style=flat-square)](http://ipfs.io/)
[![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](http://webchat.freenode.net/?channels=%23ipfs)
[![Dependency Status](https://david-dm.org/ipfs/npm-go-ipfs.svg?style=flat-square)](https://david-dm.org/ipfs/npm-go-ipfs)

> Install the latest [go-ipfs](https://github.com/ipfs/go-ipfs/) binary from [http://dist.ipfs.io](http://dist.ipfs.io)

# Installation

```
npm install go-ipfs --save
```

See [IPFS getting-started](http://ipfs.io/docs/getting-started). If anything goes wrong, try using: [http://ipfs.io/docs/install](http://ipfs.io/docs/install).

## Development

**Warning**: The binary gets put in the `go-ipfs` folder inside the module folder.

### Which go-ipfs version this package downloads?

Can be specified in `package.json` with a field `go-ipfs.version`, eg:

```json
"go-ipfs": {
  "version": "v0.4.5-pre1"
},
```

### Using local IPFS daemon as the package download url
Can be specified in `package.json` with a field `go-ipfs.version`, eg:

```json
"go-ipfs": {
  "version": "v0.4.5-pre1",
  "distUrl": "http://localhost:8080/ipfs/QmSoNtqW22htkg9mtHWNBvZLUEmqfq8su7957meS1iQfeL"
},
```

Where `QmSoNtqW22htkg9mtHWNBvZLUEmqfq8su7957meS1iQfeL` is the root of the distributions web site.

Or when run with `node src/bin.js`, the dist url can be passed via an environment variable `GO_IPFS_DIST_URL`, eg:

```
GO_IPFS_DIST_URL=http://localhost:8080/ipfs/QmSoNtqW22htkg9mtHWNBvZLUEmqfq8su7957meS1iQfeL node binsrc/bin.js
```

### Arguments

When used via `node src/bin.js`, you can specify the target platform, version and architecture via environment variables:

`TARGET_OS`

See: [Supported Platforms](https://github.com/haadcode/go-ipfs-dep/blob/master/src/supported-platforms.js) for possible values.

`TARGET_VERSION`

See: [Supported Versions](https://github.com/haadcode/go-ipfs-dep/blob/master/src/supported-versions.js) for possible values.

`TARGET_ARCH`

See: [Supported Architectures](https://github.com/haadcode/go-ipfs-dep/blob/master/src/checkPlatform.js#L4) for possible values.

Or via command line arguments in the order of: 
```
node src/bin.js <version> <platform> <architecture> <install directory>
```

```
node src/bin.js v0.4.5-pre1 linux amd64 ./go-ipfs
```

### API

For programmatic usage, see https://github.com/haadcode/go-ipfs-dep/blob/master/src/index.js#L18
npm package: @haandev/canvasbg
Description: A TypeScript library for creating interactive canvas backgrounds.
Author: Hakan Özoğlu
Latest version: 0.0.5

# CanvasBG 0.0.5

A powerful TypeScript library for creating interactive canvas backgrounds.

## Features

- **CanvasBG Base Class**: Extendable base class for creating canvas backgrounds.
- **StarField Class**: Generate a star field background with customizable options.
- **Constellation Class**: Display constellations on the canvas based on provided data.
- **MouseTracker Class**: Track the mouse position on the canvas.

## Installation

```bash
npm install @haandev/canvasbg
```

## Usage

```typescript
import { CanvasBG, StarField, Constellation } from "@haandev/canvasbg";

// Create a canvas element or select an existing one
const canvas = document.createElement("canvas");
document.body.appendChild(canvas);

// Create a CanvasBG instance and set up a star field background
const bg = new CanvasBG(canvas);
const starField = new StarField();
bg.use(starField);

// Display constellations on the star field background
const constellation = new Constellation();
bg.use(constellation);

// Start the animation loop
bg.animate();
```

## Documentation

For detailed usage instructions and API reference, please refer to the Documentation. https://haandev.github.io/canvasbg/

## Examples
For examples on how to use CanvasBG, please refer to the Examples. https://canvasbg.vercel.app/

## Contributing

Contributions are welcome! Please read the Contribution Guide for details.

## License

This project is licensed under the MIT License - see the LICENSE file for details.
npm package: @haaretz/commitlint-config
Description: Shareable commitlint config enforcing the Haaretz commit convention (mostly angular, but a bit more relaxed)
Author: TxHawks
Latest version: 1.2.0

## @haaretz/commitlint-config

Shareable commitlint config enforcing the Haaretz commit convention (mostly 
[angular](https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit), 
but a bit more relaxed). 

For use with [@commitlint/cli](https://www.npmjs.com/package/@commitlint/cli) 
and [@commitlint/prompt-cli](https://www.npmjs.com/package/@commitlint/prompt-cli).

This configuration checks every commit message to ensure it complies with the following structure:
```git
type(scope)?: subject line

body?

footer?
```
The following rules must too be observed:

* The header (first line) length is no more than `100` chars at length (warning)
* The header starts with the `type` of commit at hand. Options are:
  * `build` Build-process related commits.
  * `chore` Maintenance. General chores that don't fall into any of the other categories
  * `ci` Continuous-integration related commits (e.g., fixing Travis build, setting up Jenkins, etc.)
  * `docs` Documentation related commits
  * `feat` Commits introducing a new feature
  * `fix` Bug fixes
  * `perf` Commits dealing with measuring or improving performance
  * `refactor` Refactor commits that introduce no new functionality, infrastructure or fixes.
  * `revert` Reverting an old commit 
  * `style` Reformatting, missing commas, semi colons, etc.
  * `test` When _only_ adding missing or fixing failing tests
  * `WIP` Work in progress
* The header _may_ include a `scope` denoting what parts of the code are affected by the changes
* The scope must be enclosed in parentheses
* The `scope` must be lower-case
* The `type` and optional `scope` must be followed directly by a colon (`:`) and a space
* The header must include a subject succinctly describing the commit
* The subject must not end with a `.`
* There is a blank line between the commit-msg header and body, if one exists
* There is a blank line between the commit-msg body and footer, if one exists

## Installaion
Install with Yarn:
```sh
yarn add --dev @haaretz/commitlint-config
echo "module.exports = {extends: ['@haaretz/commitlint-config']};" > commitlint.config.js
```
or with npm:
```sh
npm install -save-dev @haaretz/commitlint-config
echo "module.exports = {extends: ['@haaretz/commitlint-config']};" > commitlint.config.js
```

## Usage
Install `husky` and `@commitlint/cli`:
```sh
yarn add --dev @commitlint/cli husky
```

And add a `commitmsg` script to your `package.json`:
```json
"scripts": {
  "commitmsg": "commitlint -e"
  }
```

Husky will setup a `commitmsg` git-hook that is executed every time a new commit 
is created, invoking commitlint with the -e flag, which causes it process the 
commit message from `.git/COMMIT_MSG`.
npm package: @haaretz/cz-htz
Description: Commitizen adapter for Haaretz frontent, with lerna and ClickUP info
Latest version: 5.0.1

# @haaretz/cz-htz
A commitizen adapter for Haaretz frontend with autodetection of affected
monorepo packages (with Lerna) and linked ClickUp task integration.


## Installation

```sh
yarn add --dev @haaretz/cz-htz
# or
npm install --save-dev @haaretz/cz-htz
```

The default export is the commitizen adapter. The default times can be imported
from `defaultTypes.js`:

```js
const types = require('@haaretz/cz-htz/defaultTypes');
```


## Configuration

### package.json

Like commitizen, you specify the configuration of cz-htz through the package.json's `config.commitizen` key.

```json5
{
// ...  default values
    "config": {
        "commitizen": {
            "path": "./node_modules/@haaretz/cz-htz",
            "disableScopeLowerCase": false,
            "disableSubjectLowerCase": false,
            "maxHeaderWidth": 100,
            "maxLineWidth": 100,
            "defaultType": "",
            "defaultScope": "",
            "defaultSubject": "",
            "defaultBody": "",
            "defaultIssues": "",
            "types": {
              ...
              "feat": {
                "description": "A new feature",
                "title": "Features"
              },
              ...
            }
        }
    }
// ...
}
```

### Environment variables

The following environment varibles can be used to override any default configuration or package.json based configuration.

* CZ_TYPE = defaultType
* CZ_SCOPE = defaultScope
* CZ_SUBJECT = defaultSubject
* CZ_BODY = defaultBody
* CZ_MAX_HEADER_WIDTH = maxHeaderWidth
* CZ_MAX_LINE_WIDTH = maxLineWidth

### Commitlint

If using the [commitlint](https://github.com/conventional-changelog/commitlint) js library, the "maxHeaderWidth" configuration property will default to the configuration of the "header-max-length" rule instead of the hard coded value of 100.  This can be ovewritten by setting the 'maxHeaderWidth' configuration in package.json or the CZ_MAX_HEADER_WIDTH environment variable.
npm package: @haaretz/generator-interactive
Description: Scaffold an Haaretz interactive page or element
Author: TxHawks
Latest version: 2.8.0

# @haaretz/generator-interactive

> Scaffold an Haaretz interactive page or element

## Usage

There is no need to install anything. Create the directory you'd like to
scaffold your your project in, `cd` into it and simply run one of the following
commands, based on the type of project you are scaffolding:

**Page:**

```sh
npm init yo @haaretz/interactive:app
```
Or with Yarn:
```sh
yarn create yo @haaretz/interactive:app
```


**Element(s):**
```sh
npm init yo @haaretz/interactive:element
```
Or with Yarn:
```sh
yarn create yo @haaretz/interactive:element
```

Your new project will now be git initialized with all base files committed,
have dependencies installed and feature a functioning build and deploy pipeline.

Good Luck.


## TODO

  1. Better docs
npm package: @haaretz/htz-css-tools
Description: A toolbelt for writing css-in-js in Haaretz apps
Author: TxHawks
Latest version: 1.1.3

# htz-css-tools 

A set of functions and mixins for consistent style authoring in Haaretz apps


<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents**

- [Installation](#installation)
- [Usage](#usage)

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

## Installation

```console
$ yarn add @haaretz/htz-css-tools
```

or 
```console
$ yarn install --save @haaretz/htz-css-tools
```

## Usage

See the [documentation](https://haaretz.github.io/htz-frontend/htz-css-tools)
npm package: @haaretz/sass-type
Description: Typographic scale with css custom properties
Author: TxHawks
Latest version: 1.1.3

# @haaretz/sass-type

> Typographic scale with css custom properties

## Installation

```sh
yarn add --dev @haaretz/sass-type
```
or with npm:
```sh
yarn install --save-dev @haaretz/sass-type
```

## Usage

```scss
@import '~@haaretz/sass-type'
```

### Configuration

`@haaretz/sass-type` exposes the following configuration variables:

#### `$htz-typescale-steps`
A map enabling or disabling the generation of typographic
scale custom properties on a pre-step basis  
**type:** `map`  
**default:**
```scss
$htz-typescale-steps: (
  -4: false,
  -3: false,
  -2: false,
  -1: false,
  0: false,
  1: false,
  2: false,
  3: false,
  4: false,
  5: false,
  6: false,
  7: false,
  8: false,
  9: false,
  10: false,
  11: false,
  12: false,
  13: false,
  14: false,
) !default;
```

### Usage

#### `generate-typography-custum-props`

Generate the custom props used by the `type` mixin, based on the configuration
of `$htz-typescale-steps`. **Must be used _after_ `$htz-typescale-steps` was
defined.**  
**Type:** `mixin`  
**Params:**  
  `$selector` (`string` or `false`): Defaults to `false`. The selector inside
  of which custom properties will be generated. `false`, the default, will 
  cause custom styles to be scoped inside the selectors under which the 
  mixin is included.
**Examples:**
```scss
.foo { @include generate-typography-custum-props(); }
// -> .foo { /* custom property declerations */ }

@include generate-typography-custum-props(":root");
// -> :root { /* custom property declerations */ }
```

#### `type`
Output font-size and line-height definitions for a defined step 
in the typographic scale.  
**Type:** `mixin`  
**Params:**  
  `$step` (`number`): The step in the typographic scale to be used.  
  `$line` (`number`): _OPTIONAL_. Overrides the default line-height for
  the step with a number of vertical rhythm units.