open-index/open-npm huggingface dataset:
npm package: @houkmellah/integrations
Description: Pluggable integrations that can be used to enhance JS SDKs
Author: Sentry
Latest version: 7.74.1

<p align="center">
  <a href="https://sentry.io/?utm_source=github&utm_medium=logo" target="_blank">
    <img src="https://sentry-brand.storage.googleapis.com/sentry-wordmark-dark-280x84.png" alt="Sentry" width="280" height="84">
  </a>
</p>

# Sentry JavaScript SDK Integrations

[![npm version](https://img.shields.io/npm/v/@sentry/integrations.svg)](https://www.npmjs.com/package/@sentry/integrations)
[![npm dm](https://img.shields.io/npm/dm/@sentry/integrations.svg)](https://www.npmjs.com/package/@sentry/integrations)
[![npm dt](https://img.shields.io/npm/dt/@sentry/integrations.svg)](https://www.npmjs.com/package/@sentry/integrations)

## Links

- [Official SDK Docs](https://docs.sentry.io/quickstart/)
- [TypeDoc](http://getsentry.github.io/sentry-javascript/)

## General

Pluggable integrations that can be used to enhance JS SDKs.

All of the integrations can also be found on our CDN e.g.:

Angular integration: `https://browser.sentry-cdn.com/5.0.0/angular.min.js`

Please make sure to always to match the version of the integration with the version of the JS SDK you are loading.
npm package: @houkunlin/bpmn-js-react
Description: A react library developed with dumi
Latest version: 0.0.10

# @houkunlin/bpmn-js-react

[![NPM version](https://img.shields.io/npm/v/@houkunlin/bpmn-js-react.svg?style=flat)](https://npmjs.org/package/@houkunlin/bpmn-js-react)
[![NPM downloads](http://img.shields.io/npm/dm/@houkunlin/bpmn-js-react.svg?style=flat)](https://npmjs.org/package/@houkunlin/bpmn-js-react)

A react library developed with dumi

## Usage

TODO

## Options

TODO

## Development

```bash
# install dependencies
$ yarn install

# develop library by docs demo
$ yarn start

# build library source code
$ yarn run build

# build library source code in watch mode
$ yarn run build:watch

# build docs
$ yarn run docs:build

# check your project for potential problems
$ yarn run doctor
```

## LICENSE

MIT
npm package: @houkunlin/farm-js-plugin-tanstack-router-watch
Description: farm tanstack router 路由文件变更监听，然后重新生成 routeTree.gen.ts 文件
Author: houkunlin
Latest version: 0.0.5

# farm js-plugins-tanstack-router-watch

![npm](https://img.shields.io/npm/v/%40houkunlin%2Ffarm-js-plugin-tanstack-router-watch.svg)

> tanstack router 路由文件变更监听，然后重新生成 routeTree.gen.ts 文件

## 示例

```bash
npm i -D @houkunlin/farm-js-plugin-tanstack-router-watch
```

`farm.config.js`

```ts
import { defineConfig } from '@farmfe/core';
import * as path from 'node:path';
import { tanstackRouter } from '@tanstack/router-plugin/vite';
import farmJsPluginTanstackRouterWatch from '@houkunlin/farm-js-plugin-tanstack-router-watch';

const isDev = process.env.NODE_ENV === 'development';
const isProd = process.env.NODE_ENV === 'production';

export default defineConfig({
  compilation: {
    input: {
      // 可以配置相对或者绝对路径
      index: './src/index.html',
    },
    output: {
      path: 'dist',
      publicPath: '/',
      targetEnv: 'browser',
      filename: 'assets/[name]_[hash].[ext]',
      assetsFilename: 'static/[name].[ext]',
    },
    resolve: {
      alias: {
        '@/': path.join(process.cwd(), 'src'),
      },
    },
    external: ['node:fs'],
    sourcemap: isDev ? 'all' : false,
  },
  // Dev Server 相关配置
  server: {
    port: 9000,
  },
  // 插件配置
  plugins: [
    [
      '@farmfe/plugin-react',
      {
        refresh: isDev,
        development: isDev,
        runtime: 'automatic',
      },
    ],
    farmJsPluginTanstackRouterWatch({
      watchEvents: ['add', 'unlink'],
      options: {
        target: 'react',
        routesDirectory: 'src/routes/',
      },
    }),
  ],
  vitePlugins: [
    tanstackRouter({
      target: 'react',
      routesDirectory: 'src/routes/',
      // 在开发环境下 autoCodeSplitting: true 会无法加载页面，但是 build 后就正常了
      autoCodeSplitting: isProd,
      // 禁用 tanstackRouter 插件的生成 routeTree.gen.ts 功能，使用 farmJsPluginTanstackRouterWatch 插件来达成此目的
      enableRouteGeneration: false,
    }),
  ],
});

```
npm package: @houlagins/ds-style
Description: Design system style
Author: Randy Houlahan
Latest version: 0.0.2


# @houlagins/ds-style

Design tokens from @houlagins/design-system.

## Setup
- Add `@houlagins/ds-style` dependency using yarn or npm to your project
```bash
  yarn add @houlagins/ds-style
```
```bash
  npm install @houlagins/ds-style
```
## Usage
SCSS
```scss
  @import path-to-file/index.scss;
```
CSS
```css
  @import path-to-file/index.css;
```
npm package: @houlagins/ds-tokens
Description: Design system tokens
Author: Randy Houlahan
Latest version: 0.0.4


# @houlagins/ds-tokens

Design tokens from @houlagins/design-system.

## Setup
- Add `@houlagins/ds-tokens` dependency using yarn or npm to your project
```bash
  yarn add @houlagins/ds-tokens
```
```bash
  npm install @houlagins/ds-tokens
```
## Usage
SCSS
```scss
  @import path-to-file/index.scss;
```
CSS
```css
  @import path-to-file/index.css;
```
CSS Module
```js
  import tokens from '@houlagins/ds-tokens/index.cssmodules.css'
```
Common JS
```js
  var tokens = require('@houlagins/ds-tokens/index.common.js')
```
Module
```js
  import tokens from '@houlagins/ds-tokens/index.module.js'
```
npm package: @houlak/hk-audit-producer
Description: Client for pushing new messages in aws sqs
Author: devteam@houlak
Latest version: 2.0.1

# hk-audit-producer

Library to facilitate sending messages to `AWS SQS`.

## Requirements

### Preconfigured resources

- `AWS SQS`: fifo source queue.
- `Slack`: webhook to receive notifications.
- `Sendgrid`: template and verified email to send email notifications.

### Environment variables

```
# AWS SQS
AWS_SQS_REGION=
AWS_SQS_SOURCE_QUEUE_URL=

# SLACK
AUDIT_SLACK_NOTIFICATION_URL=

# SENDGRID
AUDIT_SENDGRID_API_KEY=
AUDIT_SENDGRID_FAILURE_NOTIFICATION_TEMPLATE_ID=
AUDIT_SENDGRID_FAILURE_NOTIFICATION_VERIFIED_EMAIL=
AUDIT_SENDGRID_FAILURE_NOTIFICATION_FROM_NAME=
AUDIT_SENDGRID_FAILURE_NOTIFICATION_SUBJECT=
AUDIT_SENDGRID_FAILURE_NOTIFICATION_RECIPIENTS=
```

## Available utilities

- `SQSAuditMessage`: data type of the message to send to `SQS`.

- `messageHandler()`: asynchronous function to send the message to `SQS`.

## Installation

### Install via yarn

```
yarn add @houlak/hk-audit-producer
```

## Usage

```typescript
import { SQSAuditMessage, messageHandler } from '@houlak/hk-audit-producer'

const messageToSend: SQSAuditMessage = {
  auditType: 'PAYMENT_CANCELLED',
  date: new Date(),
  clientName: 'main-project-name',
  tags: ['tag01', 'tag02', 'tag03'],
  text: 'payment cancelled detail',
  metadata: {
    metadata01: {
      subMetadata0102: 'subMetadata0102',
      subMetadata0102: 'subMetadata0102',
    },
    metadata02: {
      subMetadata0201: 'subMetadata0201',
      subMetadata0202: 'subMetadata0202',
    },
  },
}

const groupId = 'a-group'
const fallbackFile = '/absolute/path/to/fallback/file/file_name.txt'

await messageHandler(messageToSend, groupId, fallbackFile)
```

## Clarifications

- `SQSAuditMessage`

Define the structure of the message.

Fields `auditType`, `date` and `clientName` are required. `tags` and `metadata` are optional.

- `messageHandler()`

In charge of preparing the message and sending it to `SQS`.

If message is sent: details of sent message will be logged as info log.

If message could not be sent: will be stored in fallback file, details of unsent message will be logged as error log and notifications of failure will be sent by `slack` and email.

- `Semaphore`

When main application call `messageHandler()` for the first time, a `semaphore` instance is created and its light is defined in yellow.

If the message could be successfully sent to the `SQS`, semaphore light is changed to green.
If it could not be sent, it is changed to red.

It is the key to handling the fallback file.

- `Fallback file`

Is a `.txt` file where the messages that cannot be sent to the `SQS` are stored.

When a message could not be delivered, it is stored in `fallback file` and `semaphore` light is changed to red.

When a message is sent to `SQS`, `semaphore` light is changed to green and `fallback file` is read.
Trying to send the messages, those that are sent will be deleted from the file and those that are not will be kept.
npm package: @hound-main/contract-helpers
Description: The `@aave/contract-helpers` package offers a set of services which allow querying aggregated on-chain data via rpc.
Latest version: 0.0.2

# @aave/contract-helpers

The `@aave/contract-helpers` package offers a set of services which allow
querying aggregated on-chain data via rpc.

## Installation

Install the package in your project directory with:

```sh
// with npm
npm install @aave/contract-helpers

// with yarn
yarn add @aave/contract-helpers
```
npm package: @hounddesk/epayco-signature-verifier
Description: ePayco Signature verifier used for transactions integrity checks
Author: R.R
Latest version: 1.3.0

# epayco-signature-verifier
ePayco Signature verifier used for transactions integrity checks

- Follow up specific documentation here (in spanish only) (https://docs.epayco.co/payments/checkout)[https://docs.epayco.co/payments/checkout]

## Installation

This is a [Node.js](https://nodejs.org/en/) module available through the
[npm registry](https://www.npmjs.com/).

Before installing, [download and install Node.js](https://nodejs.org/en/download/).
Node.js 0.10 or higher is required.

Installation is done using the
[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):

```bash
$ npm i @hounddesk/epayco-signature-verifier
```

## Use the library

```js
const { verify } = require('@hounddesk/epayco-signature-verifier');
const transactionIsLegit = verify({signature, transaction, separator}) 
```

## Development

If you to contribute or run the project as standalone library

```bash
$ git clone git@github.com:hounddesk/epayco-signature-verifier.git --depth 1
$ cd epayco-signature-verifier
$ npm install
```

Then run the library in development mode:

```bash
$ npm run start:dev 
```

This library is build with TypeScript, you need to build the source first:

```bash
$ npm run build
```

## Tests

  To run the test suite, first install the dependencies, then run `npm test`:

```bash
$ npm i
$ npm test
```
npm package: @hounddesk/hapi-authorization-header
Description: Hapi authorization header parser and utilities
Author: Ruben Restrepo
Latest version: 1.1.1

# `@hounddesk/hapi-authorization-header`

Hapi authorization header parser and utilities

## Usage

```
const hapiAuthorizationHeader = require('@hounddesk/hapi-authorization-header');

// TODO: DEMONSTRATE API
```
npm package: @hounddesk/hapi-bearer-parser
Description: Hapi Bearer token parser
Author: Ruben Restrepo
Latest version: 1.1.1

# `@hounddesk/hapi-bearer-parser`

Hapi bearer parser

## Usage

```
const hapiBearerParser = require('@hounddesk/hapi-bearer-parser');
const token = hapiBearerParser('Bearer [token]')

```
npm package: @hounddesk/plugin-firebase-authz
Description: Hapi firebase plugin for Authorization validation
Author: Ruben Restrepo
Latest version: 1.1.2

# `@hounddesk/plugin-firebase-authz`

Firebase authorization plugin for Hapi, use this plugin for validating the JWT generated by Firebase.

## How it works ?

1. Verify the token using the firebase admin SDK
2. Verify that the decoded token contains the proper claims

## Usage

```
import Hapi from '@hapi/hapi';
import { ServiceAccount } from 'firebase-admin';
import pluginFirebaseAuthz from '@hounddesk/plugin-firebase-authz';

// Initialize your firebase application using the sdk
const firebaseApp = admin.initializeApp(...);

// Register the plugin
await server.register({
    plugin: pluginFirebaseAuthz,
    options: {
      serviceAccount: firebaseApp,
      logger: console,
      userClaims: ['admin'], // optional
      schemeName: 'firebase', // optional, by default will use firebase
    },
  });
  // Register the authorization strategy
  server.auth.strategy('firebase', 'firebase');
```
npm package: @hounddesk/plugin-firebase-users
Description: Hapi plugin for firebase users sdk
Author: Ruben Restrepo
Latest version: 1.1.9

# `@hounddesk/firebase-users`

Firebase users plugin for Hapi

## Available endpoints

### Create user

### Delete user

### Get user by Id

### Get user by Email

### Get user by Phone number

### Update user

### Create claim

### List users

## Adding authorization

You can customize the authorization strategy for each specific endpoint, if you leave the strategy empty for all or any specific route, the endpoint will not require authorization.

The plugin receives a strategies property that you can use for control how each endpoint is being authorized.

Example:
Use firebase authorization strategy and require delete:user scopes for deleting an user

```
{
    actionName: 'delete',
    strategy: 'firebase',
    scope: 'delete:user',
}

```

You can specify multiple scopes if you want (following the same behavior for Hapi routes authorization mechanism)

```
{
    actionName: 'delete',
    strategy: 'firebase',
    scope: ['+delete:user', '+admin'],
}

```

## Usage

```
import Hapi from '@hapi/hapi';
import { ServiceAccount } from 'firebase-admin';
import pluginFirebaseUsers from '@hounddesk/plugin-firebase-users';

// Initialize your firebase application using the sdk
const firebaseApp = admin.initializeApp(...);

// Register the plugin
await server.register({
    plugin: pluginFirebaseUsers,
    options: {
      logger: console,
      serviceAccount: firebaseApp,
      strategies: [
        {
          actionName: 'list',
          strategy: 'firebase',
          scope: 'list:user',
        },
      ],
      routePrefix: '/api',
    },
  });
```
npm package: @hounddesk/test-pkg
Description: The best starting point for your new NPM package
Author: R.R
Latest version: 1.4.0

# pkg-template

The best starting point for your new Node project

## Installation

This is a GitHub template repository [Read more](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template)

It provides basic foundations for package authors, but it can be used as a good starting point for your Node.js application

Before using, [download and install Node.js](https://nodejs.org/en/download/).
Node.js 10.16.3 or higher is recommended.

## Available utilities enabled by default

- TypeScript
- Testing with [Jest](https://jestjs.io/) and [Tap reporter](https://www.npmjs.com/package/jest-tap-reporter)
- TypeScript linting using eslint
- TypeScript watch mode using ts-node-dev
- Formatting using Prettier
- Pre-commit hook using Husky (will run linter, formatting and unit tests before each commit)

## VSCode support

- Format on save / type enabled by default using Prettier
- Prettier extension configuration, [Read more](https://github.com/prettier/prettier-vscode)

## Conventions

- Source folder: src
- Output directory: dist
- Sourcemaps enabled by default
- Jest current file: Unit test debugging command for VSCode
- Debug: Node debugging command for VSCode
- All the eslint plugins are using the recommended defaults

## Available commands

### Start in development mode (watch mode with automatic restart)

```bash
$ npm run dev
```

### Build TypeScript

```bash
$ npm run build
```

### Build TypeScript in watch mode (without automatic restart)

```bash
$ npm run build:watch
```

### Run unit tests

```bash
$ npm test
```

### Run linter

```bash
$ npm run lint
```

### Run linter with auto fix

```bash
$ npm run lint:fix
```

### Run tests with coverage report

```bash
$ npm run coverage
```

## VSCode developer suggested extensions

The following extensions works great alongside with this setup:

- [Prettier](https://github.com/prettier/prettier-vscode)
- [Jest](https://github.com/jest-community/vscode-jest) - once installed, enable the runner >> Jest > Start runner

## Usage for publishing packages

The recommended approach is to create a scoped public package (if you are not using private packages)
[Read more about scoped packages here](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)

If you're using the package.json from the template you may want to change the name and references to pgk-template and change it to your library.
npm package: @houqwq/wasapi-win32-x64-msvc
Description: This is the **x86_64-pc-windows-msvc** binary for `@houqwq/wasapi`
Latest version: 0.0.11

# `@houqwq/wasapi-win32-x64-msvc`

This is the **x86_64-pc-windows-msvc** binary for `@houqwq/wasapi`
npm package: @hourcoding/hourcoding-ui
Description: UI library for the hourcoding web apps
Author: Amit Raikwar
Latest version: 0.20.5

# Hourcoding UI

[![Code-coverage](https://codecov.io/github/onemanfighter/hourcoding-ui/graph/badge.svg?token=VE9SQ4E4SI)](https://codecov.io/github/onemanfighter/hourcoding-ui)

[![Hourcoding UI Lint-Test](https://github.com/onemanfighter/hourcoding-ui/actions/workflows/main.yaml/badge.svg)](https://github.com/onemanfighter/hourcoding-ui/actions/workflows/main.yaml)
[![Hourcoding UI Publish job](https://github.com/onemanfighter/hourcoding-ui/actions/workflows/publish-npm.yaml/badge.svg)](https://github.com/onemanfighter/hourcoding-ui/actions/workflows/publish-npm.yaml)

UI Library for the hourcoding project, which is a collection of React web components.

[![npm version](https://badge.fury.io/js/%40hourcoding%2Fhourcoding-ui.svg)](https://badge.fury.io/js/%40hourcoding%2Fhourcoding-ui)
[![npm](https://img.shields.io/npm/dm/%40hourcoding%2Fhourcoding-ui)](https://www.npmjs.com/package/@hourcoding/hourcoding-ui)
![GitHub license](https://img.shields.io/github/license/onemanfighter/hourcoding-ui)
![GitHub issues](https://img.shields.io/github/issues/onemanfighter/hourcoding-ui)
![GitHub forks](https://img.shields.io/github/forks/onemanfighter/hourcoding-ui)
![GitHub stars](https://img.shields.io/github/stars/onemanfighter/hourcoding-ui)

## Library hosted on Netlify

[![Netlify Status](https://api.netlify.com/api/v1/badges/b6f0e253-0cde-444f-99ff-75a8a2a21a84/deploy-status)](https://app.netlify.com/sites/hourcoding-ui/deploys)

- [Hourcoding-ui](https://hourcoding-ui.netlify.app/)

## Chromatic Storybook

[![Chromatic](https://img.shields.io/badge/Chromatic-Storybook-FF4785?logo=storybook)](https://www.chromatic.com/library?appId=660b6f1cba8a33d3e2049592)

- [Chromatic link](https://www.chromatic.com/library?appId=660b6f1cba8a33d3e2049592)

## Installation

```bash
npm install @hourcoding/hourcoding-ui
or
npm i @hourcoding/hourcoding-ui
```

## Usage

**Basic component usage syntax:**

```jsx
import React from 'react';
import { Button } from '@hourcoding/ui';

const App = () => <Button>Click me</Button>;

export default App;
```

## License

- [MIT](https://github.com/onemanfighter/hourcoding-ui/blob/development/LICENSE)

## Documentation and Examples

- [Storybook](https://onemanfighter.github.io/hourcoding-ui/)

## Author and Maintainer

- [Amit Raikwar - onemanfighter](https://github.com/onemanfighter)
- [Amit Raikwar - Github](https://github.com/raikwaramit)
- [Amit Raikwar LinkedIn](https://in.linkedin.com/in/amitrai1603)