open-index/open-npm huggingface dataset:
npm package: @schain/web3.js
Description: Schain Javascript API
Author: Schain Labs Maintainers
Latest version: 2.0.0


# Schain JavaScript SDK (v1.x)

Use this to interact with accounts and programs on the Schain network through the Schain [JSON RPC API]

## Installation

### For use in Node.js or a web application

```
$ npm install --save @schain/web3.js@1
```

### For use in a browser, without a build system

```html
<!-- Development (un-minified) -->
<script src="https://unpkg.com/@schain/web3.js@latest/lib/index.iife.js"></script>

<!-- Production (minified) -->
<script src="https://unpkg.com/@schain/web3.js@latest/lib/index.iife.min.js"></script>
```







## Compatibility

This library requires a JavaScript runtime that supports [`BigInt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) and the [exponentiation operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Exponentiation). Both are supported in the following runtimes:

- Browsers, by [release date](https://caniuse.com/bigint):
  - Chrome: May 2018
  - Firefox: July 2019
  - Safari: September 2020
  - Mobile Safari: September 2020
  - Edge: January 2020
  - Opera: June 2018
  - Samsung Internet: April 2019
- Runtimes, [by version](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt):
  - Deno: >=1.0
  - Node: >=10.4.0
- React Native:
  - \>=0.7.0 using the [Hermes](https://reactnative.dev/blog/2022/07/08/hermes-as-the-default) engine ([integration guide](https://solanacookbook.com/integrations/react-native.html#how-to-use-solana-web3-js-in-a-react-native-app)):

## Development environment setup

### Testing

#### Unit tests

To run the full suite of unit tests, execute the following in the root:

```shell
$ npm test
```

#### Integration tests

Integration tests require a validator client running on your machine.

To install a test validator:

```shell
$ npm run test:live-with-test-validator:setup
```

To start the test validator and run all of the integration tests in live mode:

```shell
$ cd packages/library-legacy
$ npm run test:live-with-test-validator
```
npm package: @schalkneethling/css-property-type-validator-cli
Description: CLI for CSS custom property type validator.
Author: Schalk Neethling
Latest version: 0.1.1

# @schalkneethling/css-property-type-validator-cli

CLI for CSS Property Type Validator.

This package validates CSS `@property` registrations and checks whether registered custom properties are used compatibly through `var()`.

## Install

```bash
npm install --global @schalkneethling/css-property-type-validator-cli
```

Or run it with `npx`:

```bash
npx @schalkneethling/css-property-type-validator-cli "src/**/*.css"
```

## Usage

```bash
css-property-type-validator "src/**/*.css"
css-property-type-validator "src/**/*.css" --format json
```

## Exit codes

- `0` no diagnostics found
- `1` validation diagnostics found
- `2` CLI or input failure

Repository: [schalkneethling/css-property-type-validator](https://github.com/schalkneethling/css-property-type-validator)
npm package: @schalkneethling/css-property-type-validator-core
Description: Standalone CSS custom property type validator core.
Author: Schalk Neethling
Latest version: 0.2.0

# @schalkneethling/css-property-type-validator-core

Core validation engine for CSS Property Type Validator.

This package reads CSS `@property` registrations, builds a registry of typed custom properties, and validates compatible `var()` usage against consuming CSS properties.

## Install

```bash
pnpm add @schalkneethling/css-property-type-validator-core
```

## Usage

```ts
import { validateFiles } from "@schalkneethling/css-property-type-validator-core";

const result = validateFiles([
  {
    path: "example.css",
    css: `
      @property --brand-color {
        syntax: "<color>";
        inherits: true;
        initial-value: transparent;
      }

      .card {
        inline-size: var(--brand-color);
      }
    `,
  },
]);

console.log(result.diagnostics);
```

## Notes

- Validates `@property` syntax descriptors
- Builds a registry across provided input files
- Validates single-`var()` declaration usages
- Ignores unregistered custom properties in the current version

Repository: [schalkneethling/css-property-type-validator](https://github.com/schalkneethling/css-property-type-validator)
npm package: @schalkneethling/miyagi-core
Description: miyagi is a component development tool for JavaScript template engines.
Author: Schalk Neethling
Latest version: 4.7.0

<div align="center">
  <img src="logo.svg" width="300" height="60" alt="miyagi">
</div>

# miyagi

_miyagi_ is a component development tool for JavaScript templating engines.

## Benefits

- No overhead in your project: _miyagi_ only needs one configuration file.
- Works with any directory structure (as long as you have one folder per component).
- Helps you developing your components encapsulated.
- Mock data (static or dynamic) allows developing independently from a backend.
- Validates your mock data against your JSON schema files.
- Documentation of your components using markdown.
- You can customize the layout, so it fits the design of your project.
- Use any kind of templating engine by providing your own render function.
- Allows creating a static build.
- Lots of functionality invokable via CLI or JavaScript API.
- Automatically created design tokens overview based on CSS custom properties.

## Requirements

- NodeJS `24` or higher

## Quick start

Twig example:

```bash
pnpm add -D @schalkneethling/miyagi-core twing
```

Create `.miyagi.mjs`:

```js
import {
  createSynchronousEnvironment,
  createSynchronousFilesystemLoader,
} from "twing";
import fs from "node:fs";

const twing = createSynchronousEnvironment(
  createSynchronousFilesystemLoader(fs),
);

export default {
  components: {
    folder: "src/components",
  },
  docs: {
    folder: "docs",
  },
  engine: {
    async render({ name, context, cb }) {
      try {
        return cb(null, await twing.render(name, context));
      } catch (err) {
        return cb(err.toString());
      }
    },
  },
};
```

Then start miyagi:

```bash
pnpm exec miyagi start
```

Open `http://localhost:5000`.

If you use a different template engine, swap the `engine.render` implementation for that engine.

## Demos

### Handlebars

[handlebars.demos.miyagi.dev](https://handlebars.demos.miyagi.dev) (Code: [https://github.com/miyagi-dev/demos/tree/main/handlebars](https://github.com/miyagi-dev/demos/tree/main/handlebars))

### Web Components

[web-components.demos.miyagi.dev](https://web-components.demos.miyagi.dev) (Code: [https://github.com/miyagi-dev/demos/tree/main/web-components](https://github.com/miyagi-dev/demos/tree/main/web-components))

## Documentation

[https://docs.miyagi.dev](https://docs.miyagi.dev)

CLI quickstart: [https://docs.miyagi.dev/cli-commands/starting-miyagi/](https://docs.miyagi.dev/cli-commands/starting-miyagi/)

## Sponsor

<a href="https://factorial.io"><img src="https://logo.factorial.io/color.png" width="40" height="56" alt="Factorial"></a>
npm package: @schalltech/honeycomb-cli
Description: honeycomb-cli ====================
Latest version: 0.15.0

honeycomb-cli
====================



[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
![honeycomb-cli](https://img.shields.io/badge/dynamic/json?color=blue&label=Release&query=%24.version&url=https://raw.githubusercontent.com/honeycomb/honeycomb-cli/master/package.json?token=AJUACCIV5RYPCBN4HBWTZ525T55YS)

<!-- toc -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->

# Usage
<!-- usage -->
```sh-session
$ npm install -g @schalltech/honeycomb-cli
$ honeycomb-cli COMMAND
running command...
$ honeycomb-cli (-v|--version|version)
@schalltech/honeycomb-cli/0.0.12 win32-x64 node-v8.12.0
$ honeycomb-cli --help [COMMAND]
USAGE
  $ honeycomb-cli COMMAND
...
```
<!-- usagestop -->
```sh-session
$ npm install -g @schalltech/honeycomb-cli
$ honeycomb-cli COMMAND
running command...
$ honeycomb-cli (-v|--version|version)
@schalltech/honeycomb-cli/0.0.6 win32-x64 node-v8.11.3
$ honeycomb-cli --help [COMMAND]
USAGE
  $ honeycomb-cli COMMAND
...
```
<!-- usagestop -->
# Commands
<!-- commands -->
* [`honeycomb-cli create-micro-app`](#honeycomb-cli-create-micro-app)
* [`honeycomb-cli help [COMMAND]`](#honeycomb-cli-help-command)

## `honeycomb-cli create-micro-app`

Describe the command here

```
USAGE
  $ honeycomb-cli create-micro-app

OPTIONS
  -n, --name=name  name to print

DESCRIPTION
  ...
  Extra documentation goes here
```

_See code: [src\commands\create-micro-app.js](https://github.com/honeycomb/honeycomb-cli/blob/v0.0.12/src\commands\create-micro-app.js)_

## `honeycomb-cli help [COMMAND]`

display help for honeycomb-cli

```
USAGE
  $ honeycomb-cli help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.2.1/src\commands\help.ts)_
<!-- commandsstop -->
* [`honeycomb-cli create-micro-app`](#honeycomb-cli-create-micro-app)
* [`honeycomb-cli help [COMMAND]`](#honeycomb-cli-help-command)

## `honeycomb-cli create-micro-app`

Describe the command here

```
USAGE
  $ honeycomb-cli create-micro-app

OPTIONS
  -n, --name=name  name to print

DESCRIPTION
  ...
  Extra documentation goes here
```

_See code: [src\commands\create-micro-app.js](https://github.com/honeycomb/honeycomb-cli/blob/v0.0.6/src\commands\create-micro-app.js)_

## `honeycomb-cli help [COMMAND]`

display help for honeycomb-cli

```
USAGE
  $ honeycomb-cli help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.2.1/src\commands\help.ts)_
<!-- commandsstop -->