open-index/open-npm huggingface dataset:
npm package: @pixelpay/react-native-plugin
Description: Native bridge with ReactNative plugin and PixelPaySDK
Author: Ivan Suazo
Latest version: 2.0.9

# Librería de desarrollo para el Framework ReactNative

## ¿Como instalar?

Los paquetes oficiales de NPM son [@pixelpay/sdk-core](https://www.npmjs.com/package/@pixelpay/sdk-core) y [@pixelpay/react-native-plugin](https://www.npmjs.com/package/@pixelpay/react-native-plugin).

Utiliza los siguientes comandos para su descarga e instalación:

``` bash
npm install @pixelpay/sdk-core
npm install @pixelpay/react-native-plugin
```
npm package: @pixelpay/ui-core
Description: Interfaz grafica para los componentes de PixelPay
Latest version: 1.0.0-beta.15


# PixelPay UI Core (Stencil)

Stencil is a compiler for building fast web apps using Web Components.

Stencil combines the best concepts of the most popular frontend frameworks into a compile-time rather than run-time tool.  Stencil takes TypeScript, JSX, a tiny virtual DOM layer, efficient one-way data binding, an asynchronous rendering pipeline (similar to React Fiber), and lazy-loading out of the box, and generates 100% standards-based Web Components that run in any browser supporting the Custom Elements v1 spec.

Stencil components are just Web Components, so they work in any major framework or with no framework at all.

## Getting Started

To start building and run:

```bash
npm install
npm start
```

To build the component for production, run:

```bash
npm run build
```

Need help? Check out our docs [here](https://stenciljs.com/docs/my-first-component).


## Naming Components

When creating new component tags, we recommend _not_ using `stencil` in the component name (ex: `<stencil-datepicker>`). This is because the generated component has little to nothing to do with Stencil; it's just a web component!

Instead, use a prefix `x-` For example, `x-segment`.
npm package: @pixelperf/eslint-config
Description: Common ESLint Configuration for projects at github.com/pixelperf
Latest version: 1.0.0

# eslint-config-pixelperf

Personal ESLint Configuration for projects at github.com/pixelperf

### Features

* JavaScript linting with `eslint-config-airbnb`
* React best practices (including hooks)
* Accessibility (a11y) best practices
* Browser compatibility warnings
* Typescript integration
* Import sorting

### Sort Order

This configuration enables automatic import sorting using `eslint --fix` to sort imports to the following order:

1. `import React from 'react'` (always goes first)
2. Third party libraries (i.e. from `node_modules`)
3. Imports from the root directory using the alias `'@/../..'`
4. Relative imports (i.e. `../` or `./`)

Imports in the same group will then be sorted alphabetically.
npm package: @pixelpine/core
Description: Premium, enterprise-level React component library for high-performance UIs.
Author: Electron UI Team
Latest version: 0.0.3
Deprecated: This package has been removed.

# @pixelpine/core 🚀

Premium, enterprise-level React component library for high-performance UIs.

## Installation

```bash
npm install @pixelpine/core @pixelpine/theme
```

## Features

- **Full Tree-Shaking**: Optimized bundles (ESM/CJS) ensuring zero-clutter in your production apps.
- **Enterprise Ready**: Full TypeScript support.
- **Premium Design**: A focus on "WOW" factor aesthetics out of the box.

## License

MIT © Electron UI Team
npm package: @pixelpine/theme
Description: Design tokens and theming engine for Electron UI.
Author: Electron UI Team
Latest version: 0.0.1
Deprecated: This package has been removed.

# @pixelpine/theme 🎨

Design tokens and theming engine for Electron UI.

## Installation

```bash
npm install @pixelpine/theme
```

## Features

- **Theming Engine**: Built-in support for Light and Dark modes with CSS variable injection.
- **Token System**: Core design tokens for consistent spacing, colors, and typography.

## License

MIT © Electron UI Team
npm package: @pixelplex/api-decorators
Description: Set of decorators that can simplify DTO creation.
Author: PixelPlex Inc.
Latest version: 0.4.5

# Nest.js API Decorators

Set of decorators that can simplify DTO creation.

## Install the library

```bash
yarn add @pixelplex/api-decorators
```

## Use the library

### Example of usage

```typescript
import { ApiPropertyString, ApiPropertyArray } from '@pixelplex/api-decorators';

export class MyBodyDTO {

  @ApiPropertyString()
  comment: string;

  @ApiPropertyArray({ type: 'enum', enumValue: USER_ROLE, isNotEmpty: true, isUnique: true })
  roles: USER_ROLE[];
}
```

### List of decorators:

```typescript
ApiPropertyArray
ApiPropertyBigint
ApiPropertyBoolean
ApiPropertyDate
ApiPropertyEmail
ApiPropertyEnum
ApiPropertyFloat
ApiPropertyHash
ApiPropertyId
ApiPropertyJwt
ApiPropertyNumber
ApiPropertyPassword
ApiPropertyPhoneNumber
ApiPropertyString
```
npm package: @pixelplex/sms-service
Description: Sms service
Author: dev@pixelplex.io
Latest version: 1.2.0

# SMS Service

Library for fast implementation of the functionality of sending SMS messages.

Supported gateways:

- smsc
- sms-traffic
- twilio
- fire-mobile
- devinotele

and debug gateways:

- console
- slack

The service receive messages and sends them via SMS.

## How to use

1. create template for message
2. add `@pixelplex/sms-service` to your application
3. call `SmsModule.forRoot` from `@pixelplex/sms-service` to `import` in your module
4. send a message by calling `this.smsService.sendSms('+375297775544', 'auth', { name: 'Афанасий' });` where `smsService` is `SmsSenderService` from `@pixelplex/sms-service`

Didn't understand anything? Okay, let's see more details

### Prepare templates

The service uses Handlebars as template engine. So all your sms templates should be prepared as handlebars templates.

```handlebars
Welcome, {{name}}! This is subject
```

## Configuration Variables

| Name           | Description                                                       | Example                   |
|----------------|-------------------------------------------------------------------|---------------------------| 
| gateways       | Array of gateways to send email, supported: smpt, slack, console  | `['slack']`               |
| customGateways | Array of custom gateways classes                                  | `[CustomGateway]`         |
| slack.url      | Hook URL in case you want to duplicate messages to Slack          | `https://hooks.slack.com` |
| *.sender       | Sms sender phone number                                           | `+375333333333`           |
| *              | Other gateway-specific options like username, password, sid etc.  |                           |

### Trigger new message sending

**1. Install npm package**

```bash
yarn add @pixelplex/sms-service
```

**2. Import SmsModule** in your module you'll send sms from:

```ts
import { Module } from '@nestjs/common';
import { SmsModule } from '@pixelplex/sms-service';
import { AppService } from './app.service';

@Module({
  controllers: [],
  imports: [
    MailModule.forRoot({
      gateways: ['slack', 'twilio', 'console'],
      slack: { url: 'hooks.slack.com' },
      twilio: {
        sid: 'SID',
        token: 'TOKEN',
        sender: '+375333333333',
      },
    }),
  ],
  providers: [AppService],
})
export class AppModule {}
```

**3. Call sendSms** to send your sms:

```typescript
import { Injectable } from '@nestjs/common';
import { SmsSenderService } from '@pixelplex/sms-service';

@Injectable()
export class AppService {

  constructor(private readonly smsService: SmsSenderService) {
  }

  async onModuleInit() {
    this.smsService.sendSms('+375297775544', './path', { name: 'Афанасий' });
  }

}
```

In the example below we'll send sms to `+375297775544` with handlebars path `./path`.

`{name: 'Афанасий'}` is the object with data which will used as payload data during processing your handlebars template.
npm package: @pixelplex/typechain-web3-v1-simplified
Description: 🔌 TypeChain target for Web3-v1
Latest version: 0.1.1

# Typechain target Web3-v1

<p align="center">
  <img src="https://github.com/Neufund/TypeChain/blob/d82f3cc644a11e22ca8e42505c16f035e2f2555d/docs/images/typechain-logo.png?raw=true" width="300" alt="TypeChain">
  <h3 align="center">TypeChain target Web3-v1</h3>
  <p align="center">🔌 TypeScript bindings for Web3 1.x.x smartcontracts</p>

  <p align="center">
    <a href="https://github.com/ethereum-ts/TypeChain/actions"><img alt="Build Status" src="https://github.com/ethereum-ts/TypeChain/workflows/CI/badge.svg"></a>
    <a href="https://coveralls.io/github/ethereum-ts/TypeChain?branch=master"><img alt="Coverage" src="https://coveralls.io/repos/github/ethereum-ts/TypeChain/badge.svg?branch=master"></a>
    <img alt="Downloads" src="https://img.shields.io/npm/dm/typechain.svg">
    <a href="https://github.com/prettier/prettier"><img alt="Prettier" src="https://img.shields.io/badge/code_style-prettier-ff69b4.svg"></a>
    <a href="/package.json"><img alt="Software License" src="https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square"></a>
  </p>

  <p align="center">
    <a href="https://blog.neufund.org/introducing-typechain-typescript-bindings-for-ethereum-smart-contracts-839fc2becf22">Medium post</a> | <a href="https://www.youtube.com/watch?v=9x6AkShGkwU">DappCon Video</a>
  </p>
</p>

## [TypeChain readme](https://github.com/ethereum-ts/TypeChain)
npm package: @pixelpusher/emojirate
Description: A dependency free native/vanilla web component element
Author: olliew
Latest version: 0.3.0

# Emoji Rater

Rate things with emoji rather than stars 

![screenshot showing the emojirate component](./emojirate.png)

## Usage
```
	<emoji-rate></emoji-rate>

<script type="module">
	import './emojirate/index.js'
</script>
```

Unfortunately there is in not yet a way for a custom element to automatically pass its data to a form submission. Instead, something like the following is necessary:

```
var emojirate = document.querySelector('emoji-rate');
var formData = new FormData();
formData.append('rating', emojirate.rating);
```

The `emoji-rate` element also will dispatch a custom "rating" event: 

```
var emojirate = document.querySelector('emoji-rate');
emojirate.addEventListener('rating', function(e) {console.log(e.target.rating)});
```
npm package: @pixelry/react-scopes
Description: Lightweight cross component state management allowing multiple components to independently access, use, and set the same shared state.
Author: Pixelry.com
Latest version: 1.2.0

# Pixelry - React Scopes

Lightweight cross component state management allowing multiple components to independently access, use, and set the same shared state. A simple React solution to signals.

React Scopes require React 18 or higher.

## Quick Start

Installation

`npm i @pixelry/react-scopes`

This example shows efficient state sharing between three components.

```tsx
import React, { useCallback } from 'react';
import { useObjectScope, IObjectScope } from '@pixelry/react-scopes';

type CounterState = {
  count: number;
};

//
// component that creates a scope and shares it with child components
//
export function Counter() {
  // scope is always the same object
  const scope = useObjectScope<CounterState>({ count: 1 });

  // this component does not need the state to render
  // it does not call `use` and will not rerender on state changes
  return (
    <div>
      <CounterValue scope={scope}></CounterValue>
      <CounterButton scope={scope}></CounterButton>
    </div>
  );
}

//
// component that uses scope state
//
function CounterValue(props: { scope: IObjectScope<CounterState> }) {
  // call `use` to hook the state of the scope and
  // rerender on state changes
  const state = props.scope.use();

  return <span>{state.count}</span>;
}

//
// component that gets and sets scope state
//
function CounterButton(props: { scope: IObjectScope<CounterState> }) {
  // since the scope dependency is unchanging the callback is
  // always the same object
  const handleIncrement = useCallback(() => {
    props.scope.set({
      // call `get` for the current state when needed in the callback
      count: props.scope.get().count + 1,
    });
  }, [props.scope]);

  // this component does not need the state to render
  // it does not call `use` and will not rerender on state changes
  return <button onClick={handleIncrement}>+</button>;
}
```

Passing the unchanging scope object as a prop (or via context) allows each participating component to control if they subscribe to changes of the state. If they need to rerender when state changes they can `use` the scope. If they need the state value in a callback they can `get` the value without needing to subscribe via `use`. They can `set` the value of the scope directly without needing to invoke a parent or `use` the state value.

## Documentation

[Object Scopes](https://github.com/pixelry/react-scopes#object-scopes)

[Array Scopes](https://github.com/pixelry/react-scopes#array-scopes)

[Record Scopes](https://github.com/pixelry/react-scopes#record-scopes)

[Composition and Performance](https://github.com/pixelry/react-scopes#composition-and-performance)

[Stores and Actions](https://github.com/pixelry/react-scopes#stores-and-actions)
npm package: @pixelshift.ai/gl-conformance
Description: Khronos WebGL conformance test suite
Author: Mikola Lysenko
Latest version: 0.0.8

The Official Khronos WebGL Repository

This is the official home of the Khronos
WebGL repository for the WebGL specifications
and the WebGL conformance test suite.

Before adding a new test or editing an existing test
[please read these guidelines](sdk/tests/test-guidelines.md).

You can find live versions of the specifications at
http://www.khronos.org/webgl/

The newest work in progress WebGL conformance test suite
for the next version of the spec can be accessed at.
https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html

Official live versions of the conformance test suite can be found at
https://www.khronos.org/registry/webgl/conformance-suites/

The WebGL Wiki can be found here
http://www.khronos.org/webgl/wiki/