open-index/open-npm huggingface dataset:
npm package: @omniframe/react-app
Description: Scaffolding and shared build pipeline for Onmiframe React apps.
Author: Robert H. Hameetman
Latest version: 1.0.0-alpha.2

![Omniframe][header]

[![npm][npm-badge]][npm-badge-url]
[![Release](https://github.com/omniframe/omniframe/workflows/Release/badge.svg)](https://github.com/omniframe/omniframe/actions)
[![license][npm-license]][npm-license-url]

# 📦 @omniframe/cli

Scaffolding and shared build pipeline for Onmiframe.

---

- [📦 @omniframe/cli](#-omniframecli)
  - [💼 [§1.0] Getting Started](#-10-getting-started)
  - [🛠 [§2.0] Building Services](#-20-building-services)
    - [[§2.1] Creating Components](#21-creating-components)
  - [📄 [§3.0] License](#-30-license)

---

```bash
npm init omniframe
```

Omniframe is a new approach to Front End microservice orchestration which
combines asynchronous rendering with organic event-driven service management.

## 💼 [§1.0] Getting Started

Create a new project using the Omniframe interactive CLI:

```bash
npm init omniframe
```

Spin up the app in `development`:

```bash
npm run dev
```

Or in `production`:

```bash
npm start
```

## 🛠 [§2.0] Building Services

To get started building services, run the following command:

```bash
npm init @omniframe/service <service>
```

### [§2.1] Creating Components

Once your new service is up and running, you may begin adding new components by
running the following command in the service's root directory:

```bash
npm run make component ./components/Example
```

## 📄 [§3.0] License

This project is licensed under the MIT License.
See the [LICENSE.md](LICENSE.md) file for details

[header]: /.github/readme.png 'Omniframe'
[npm-badge]: https://img.shields.io/npm/v/@omniframe/core.svg
[npm-badge-url]: https://www.npmjs.com/package/@omniframe/core
[npm-license]: https://img.shields.io/npm/l/@omniframe/core.svg
[npm-license-url]: https://github.com/omniframe/omniframe/blob/master/LICENSE
npm package: @omnilumen/cli
Description: OmniLumen CLI streamlines Stellar development, integrating CLI tools, Soroban contract deployment, and local development environments.
Latest version: 1.0.0

# OmniLumen CLI

OmniLumen CLI (ocli) is a powerful command-line interface designed for interacting with the Stellar network. It wraps around the Stellar CLI, adding enhanced functionality for streamlined operations, making it easier for developers to manage their Stellar-related tasks.
## Installation

To install the OmniLumen CLI, ensure Node.js is installed, and then run the following command:

```sh
npm install -g omnilumen@latest
```
## Usage
### Interactive Menu

After installation, you can access the OmniLumen interactive menu by simply running:

```sh
ocli
```
### example Commands
OmniLumen CLI supports various commands for managing Stellar operations. Below are a few examples:

#### Detailed CLI Overview

For more detailed documentation and command usage examples, visit [OmniLumen CLI Overview](https://www.omnilumen.net/cliOverview).

#### Contract Commands
- Deploy a Contract
```sh
	
scli contract deploy --source S... --network testnet --wasm-hash <hex-encoded-wasm-hash>

```
- Events Command
```sh
scli events [options]

```
- Keys Command
```sh
scli keys [options]

```
- Network Command
```sh
scli network [options]

```
- Snapshot Command
```sh
scli snapshot [options]
```
- Tx Command
```sh
scli tx [options]
```
- XDR Command
```sh
scli xdr [options]
```
- Completion Command
```sh
scli completion [options]
```
- Cache Command
```sh
scli cache [options]
```
npm package: @omnilumen/core
Description: Core library for OmniLumen
Latest version: 1.0.0

# @omnilumen-core

OmniLumen Core is A VanillaJS library used by OmniLumen, for example the OmniLumen CLI (ocli) and OmniLumen Quickstart (sqs). 

It provides the essential functionality that powers these tools, making it easier to interact with the Stellar network and Soroban smart contracts.

## Learn More

For more details about how to use OmniLumen Core, visit our official documentation:

Visit our official website: https://www.omnilumen.net
npm package: @omnilumen/quickstart
Description: OmniLumen Quickstart streamlines Stellar development, integrating quickstart tools, provides a simple way to run stellar-core and horizon locally for development and testing.
Latest version: 1.0.0

# OmniLumen Quickstart

OmniLumen Quickstart (sqs) is a tool that simplifies setting up a local Stellar development environment. It wraps around Stellar Quickstart with additional functionality, enabling developers to efficiently manage their Stellar network setup, test smart contracts, and interact with Stellar-related tools using Docker.
## Installation

To install OmniLumen Quickstart, ensure you have Node.js and Docker installed, and then run the following command:

```sh
npm install -g omnilumen@latest
```

This will install the sqs command, providing access to all OmniLumen Quickstart features.

## Usage
### Interactive Menu

After installation, you can access the OmniLumen interactive menu by simply running:

```sh
sqs
```
### example Commands
OmniLumen Quickstart supports various commands for managing Stellar operations. Below are a few examples:

#### Detailed Omnilumen Quick Start Overview

For more detailed documentation and command usage examples, visit [OmniLumen Quick Start Overview](https://www.omnilumen.net/quickStartOverview).

#### Local Network

- Starting a Local Network
```sh
	
sqs local

```
or you can run:
```sh
	
sqs up

```
- Start Local Development Network in Background
```sh
sqs local -d

```

### shutdown Network
- Shut Down the Quickstart Environment
```sh
sqs down

```

#### Testnet and Futurenet Nodes

- Start Testnet Node
```sh
sqs tn

```
- Start Testnet Node in Persistent Mode
```sh
 sqs tnp

```
- Start Futurenet  Node
```sh
sqs fn

```
- Start Futurenet  Node in Persistent Mode
```sh
sqs fnp

```

####  Run a Custom Docker Command

You can prepend sqs to execute custom Docker commands within the Stellar Quickstart environment. 

For example, to run a custom Docker command that maps port 8000 on your host to port 8000 inside the container, use:

```sh
sqs docker run -p 8000:8000 stellar/quickstart --local

```

This allows you to tailor your development environment with specific Docker configurations while leveraging the power of OmniLumen Quickstart.
npm package: @omnimedia/kimura
Description: A tool for interactively editing the transformation matrices of pixi objects.
Author: Przemysław Gałęzki
Latest version: 1.0.4

# @omnimedia/kimura
<p align="center">
  <img src="assets/kimura.png" width="600px" alt="Kimura wireframe">
</p>


 Tool for interactively editing the transformation matrices of pixi objects.

## Installation :package:

```base
npm install @omnimedia/kimura
```

## Usage :page_facing_up:

```js
import {Application, Graphics} from "pixi.js"

import {Kimura} from "../kimura.js"

const app = new Application()

await app.init({
    autoDensity: true,
    backgroundColor: 0xabcdef,
    width: 1024,
    height: 1024,
    antialias: true,
    view: document.createElement('canvas') ,
})
document.body.appendChild(app.canvas)

const a = app.stage.addChild(new Graphics())
a.circle(0, 0, 100)
    .fill(0xfedbac)
a.pivot.set(50, 100)
a.scale.set(1)
a.position.set(300, 300)

const b = app.stage.addChild(new Graphics())
b.circle(0, 0, 100)
    .fill(0xfedbac)
b.pivot.set(50, 100)
b.scale.set(1)
b.position.set(600, 300)

app.stage.addChild(new Kimura({
    group: [a, b]
}))

```

<p align="center">
<img src="https://i.imgur.com/b82qYjF.png" width="100%" />
</p>
npm package: @omnious/eslint-config
Description: ESLint shareable config for the Omnious JavaScript style guide
Author: Omnious Dev Team
Latest version: 0.2.1

<div align="center">
  <a href="https://github.com/omnious/omnious-linter/tree/master/packages/eslint-config" title="ESLint Config Omnious">
    <img alt="ESLint Config Omnious" src="https://raw.githubusercontent.com/omnious-dev/i/master/omnious-logo.png" width="240px" />
  </a>
  <br />
  <h1>@omnious/eslint-config</h1>
</div>

<p align="center">
  ESLint <a href="http://eslint.org/docs/developer-guide/shareable-configs.html">shareable config</a> for the Omnious JavaScript style guide
</p>

<div align="center">
  <!-- <a href="https://circleci.com/gh/omnious-dev/eslint-config-omnious">
    <img alt="CircleCI" src="https://circleci.com/gh/omnious-dev/eslint-config-omnious.svg?style=shield" />
  </a> -->
  <a href="https://badge.fury.io/js/@omnious/eslint-config">
    <img alt="npm version" src="https://badge.fury.io/js/@omnious/eslint-config.svg" />
  </a>
  <a href="https://www.npmjs.com/package/@omnious/eslint-config">
    <img alt="npm" src="https://img.shields.io/npm/dt/@omnious/eslint-config.svg" />
  </a>
  <a href="https://david-dm.org/omnious-dev/@omnious/eslint-config">
    <img alt="npm" src="https://img.shields.io/david/omnious-dev/@omnious/eslint-config.svg?style=flat-square" />
  </a>
  <a href="https://opensource.org/licenses/mit-license.php">
    <img alt="MIT Licence" src="https://badges.frapsoft.com/os/mit/mit.svg?v=103" />
  </a>
  <a href="https://github.com/ellerbrock/open-source-badge/">
    <img alt="Open Source Love" src="https://badges.frapsoft.com/os/v1/open-source.svg?v=103" />
  </a>
</div>

<br />

## Installation

```bash
# NPM
$ npm install --save-dev eslint @omnious/eslint-config
# Yarn
$ yarn add -D eslint @omnious/eslint-config
```

## Usage

<!-- Once the `eslint-config-omnious` package is installed, you can use it by specifying `omnious` in the [`extends`](http://eslint.org/docs/user-guide/configuring#extending-configuration-files) section of your [ESLint configuration](http://eslint.org/docs/user-guide/configuring). -->

```js
{
  "extends": "@omnious",
  "rules": {
    // Additional, per-project rules...
  }
}
```

### Using the `omnious` config with `eslint:recommended`

There are several rules in the [`eslint:recommended` ruleset](http://eslint.org/docs/rules/) that Omnious style is not opinionated about that you might want to enforce in your project.

To use Omnious style in conjunction with ESLint's recommended rule set, extend them both, making sure to list `omnious` last:

```js
{
  "extends": ["eslint:recommended", "@omnious"],
  "rules": {
    // Additional, per-project rules...
  }
}
```

## License

[MIT](https://github.com/omnious-dev/eslint-config-omnious/blob/master/LICENSE) © [Omnious](http://www.omnious.com)
npm package: @omnious/eslint-config-react
Description: ESLint shareable config for the Omnious JavaScript React projects
Author: Omnious Dev Team
Latest version: 0.1.2

<div align="center">
  <a href="https://github.com/omnious/omnious-linter/tree/master/packages/eslint-config-react" title="ESLint Config Omnious React">
    <img alt="ESLint Config Omnious React" src="https://raw.githubusercontent.com/omnious-dev/i/master/omnious-logo.png" width="240px" />
  </a>
  <br />
  <h1>@omnious/eslint-config-react</h1>
</div>

<p align="center">
  ESLint <a href="http://eslint.org/docs/developer-guide/shareable-configs.html">shareable config</a> for the Omnious JavaScript React projects
</p>

<div align="center">
  <!-- <a href="https://circleci.com/gh/omnious-dev/eslint-config-omnious">
    <img alt="CircleCI" src="https://circleci.com/gh/omnious-dev/eslint-config-omnious.svg?style=shield" />
  </a> -->
  <a href="https://badge.fury.io/js/@omnious/eslint-config-react">
    <img alt="npm version" src="https://badge.fury.io/js/@omnious/eslint-config-react.svg" />
  </a>
  <a href="https://www.npmjs.com/package/@omnious/eslint-config-react">
    <img alt="npm" src="https://img.shields.io/npm/dt/@omnious/eslint-config-react.svg" />
  </a>
  <a href="https://david-dm.org/omnious-dev/@omnious/eslint-config-react">
    <img alt="npm" src="https://img.shields.io/david/omnious-dev/@omnious/eslint-config-react.svg?style=flat-square" />
  </a>
  <a href="https://opensource.org/licenses/mit-license.php">
    <img alt="MIT Licence" src="https://badges.frapsoft.com/os/mit/mit.svg?v=103" />
  </a>
  <a href="https://github.com/ellerbrock/open-source-badge/">
    <img alt="Open Source Love" src="https://badges.frapsoft.com/os/v1/open-source.svg?v=103" />
  </a>
</div>

<br />

## Installation

```bash
# NPM
$ npm install --save-dev eslint eslint-plugin-import eslint-plugin-react eslint-plugin-jsx-a11y @omnious/eslint-config-react
# Yarn
$ yarn add -D eslint eslint-plugin-import eslint-plugin-react eslint-plugin-jsx-a11y @omnious/eslint-config-react
```

## Usage

```js
{
    "extends": "@omnious/eslint-config-react",
    "rules": {
        // Additional, per-project rules...
    }
}
```

### Using the `omnious` config with `eslint:recommended`

There are several rules in the [`eslint:recommended` ruleset](http://eslint.org/docs/rules/) that Omnious style is not opinionated about that you might want to enforce in your project.

To use Omnious style in conjunction with ESLint's recommended rule set, extend them both, making sure to list `omnious` last:

```js
{
  "extends": ["eslint:recommended", "@omnious/eslint-config-react"],
  "rules": {
    // Additional, per-project rules...
  }
}
```

## License

[MIT](https://github.com/omnious/omnious-linter/blob/master/LICENSE) © [Omnious](https://www.omnious.com)
npm package: @omnious/kit
Description: React components for omnious.
Author: Omnious Dev Team
Latest version: 0.1.0
Deprecated: use @omnious/ui

# Omniouskit

[React](http://facebook.github.io/react/) components for [omnious](https://www.omnious.com).

## Installation

```sh
  npm install --save @omnious/kit
  # or yarn
  yarn add @omnious/kit
```
npm package: @omnious/reset
Description: [![npm][npm]][npm-url] [![dt][dt]][npm-url]
Author: Omnious Dev Team
Latest version: 0.3.1-alpha.2

# @omnious/reset

[![npm][npm]][npm-url]
[![dt][dt]][npm-url]

## Installation

```bash
# NPM
$ npm install --save @omnious/reset
# Yarn
$ yarn add @omnious/reset
```

## Usage

```js
import '@omnious/reset';
```

[npm]: https://img.shields.io/npm/v/@omnious/ui.svg
[npm-url]: https://www.npmjs.com/package/@omnious/ui
[dt]: https://img.shields.io/npm/dt/@omnious/ui.svg
npm package: @omnious/tslint-config
Description: TSLint sharable config for the Omnious TypeScript style guide
Author: Omnious Dev Team
Latest version: 0.1.1
Deprecated: deprecated

# @omnious/tslint-config

## License

[MIT](https://github.com/omnious-dev/omnious-linter/blob/master/LICENSE) © [Omnious](https://www.omnious.com)
npm package: @omnious/webpack
Description: Webpack scripts and configurations for omnious.
Author: Omnious Dev Team
Latest version: 0.9.5-alpha.0

# @omnious/webpack

[![node][node]][node.url]
[![npm][npm]][npm.url]
[![dt][dt]][npm.url]
[![code style: prettier][prettier]][prettier.url]

## Installation

```bash
# NPM
$ npm install --save-dev @omnious/webpack
# Yarn
$ yarn add -D @omnious/webpack
```

[node]: https://img.shields.io/node/v/@omnious/webpack.svg
[node.url]: https://nodejs.org
[npm]: https://img.shields.io/npm/v/@omnious/webpack.svg
[npm.url]: https://www.npmjs.com/package/@omnious/webpack
[dt]: https://img.shields.io/npm/dt/@omnious/webpack.svg
[prettier]: https://img.shields.io/badge/code_style-prettier-ff69b4.svg
[prettier.url]: https://github.com/prettier/prettier
npm package: @omnipair/carbon-cli
Description: Carbon CLI - Solana indexing framework for generating decoders and scaffolding projects
Latest version: 1.0.1

# @omnipair/carbon-cli

Carbon CLI for the [Carbon](https://github.com/Omnipair/carbon) Solana indexing framework.

## Install

```bash
npm install -g @omnipair/carbon-cli
```

## Usage

```bash
# Interactive mode
carbon-cli

# Generate a decoder from an Anchor IDL
carbon-cli parse --idl my_program.json --output ./src/decoders

# Generate a decoder from an on-chain program address
carbon-cli parse --idl LBUZKhRxPF3XUpBCjp4YzTKgLccjZhTSDM9YuVaPwxo -u mainnet-beta --output ./src/decoders

# Scaffold a new project
carbon-cli scaffold --name my-indexer --output ./my-indexer --decoders pumpfun,moonshot --data-source yellowstone-grpc --metrics log

# Help
carbon-cli --help
```

## Supported Platforms

- Linux x64
- macOS x64 (Intel)
- macOS arm64 (Apple Silicon, via Rosetta 2)
- Windows x64

## Building from Source

If your platform isn't supported, you can build from source:

```bash
cargo install --git https://github.com/Omnipair/carbon.git carbon-cli
```
npm package: @omnipixel/payload-oauth2-plus
Description: Enhanced OAuth2 plugin for Payload CMS with robust Apple OAuth support
Author: Jake Palmer
Latest version: 1.0.2

# @omnipixel/payload-oauth2-plus

Enhanced OAuth2 plugin for Payload CMS with robust Apple OAuth support. This package extends the excellent [payload-oauth2](https://github.com/WilsonLe/payload-oauth2) plugin with additional features and improvements.

## Features

✨ Everything from the original payload-oauth2, plus:
- Full Apple OAuth support with `form_post` response mode
- Improved type safety
- Better error handling
- Comprehensive examples

## Installation

```bash
npm install @omnipixel/payload-oauth2-plus
# or
yarn add @omnipixel/payload-oauth2-plus
# or
pnpm add @omnipixel/payload-oauth2-plus
```

## Usage

```typescript
import { OAuth2Plugin } from '@omnipixel/payload-oauth2-plus'

// Configure your OAuth providers
export const appleOAuth = OAuth2Plugin({
  // ... your config
})
```

## Credits

This package is a fork of [payload-oauth2](https://github.com/WilsonLe/payload-oauth2) by Wilson Le, enhanced with Apple OAuth support and other improvements.

## License

MIT