open-index/open-npm huggingface dataset:
npm package: @slateui/cli
Description: @slateui/cli - initialize themes and add UI directives
Author: Mohammad Javed
Latest version: 0.2.0

# SlateUI CLI — Angular UI setup and component generator

The `@slateui/cli` package provides Angular schematics to quickly set up SlateUI in your project and add fully-typed, accessibility-friendly UI directives from the official registry.

## Features

- **Initialize SlateUI**: Configure Tailwind, theme tokens, and base color in one command.
- **Add directives on demand**: Install directives like `button`, `badge`, `accordion`, etc., or add them all at once.

## Installation

Install the CLI as a dev dependency (recommended):

```bash
npm install -D @slateui/cli
# or
yarn add -D @slateui/cli
# or
pnpm add -D @slateui/cli
```

## Quick start

Initialize SlateUI in your Angular application:

```bash
ng g @slateui/cli:init
```

Then add a directive from the registry (example: `button`):

```bash
ng g @slateui/cli:add button
```

Or add everything available:

```bash
ng g @slateui/cli:add --all
```

## Schematics and options

### `init` — Initialize SlateUI

Sets up SlateUI in your project. This will configure Tailwind, add styles, and set your chosen base color.

Usage:

```bash
ng g @slateui/cli:init [options]
```

Options:

- `--project <name>`: Target Angular app project. Defaults to your workspace default.
- `--baseColor <neutral|slate|zinc|stone|gray>`: Base color palette. Default: `neutral`.
- `--confirmOverwrite <y|n>`: When `styles.css` already has content, confirm whether to overwrite.

Examples:

```bash
ng g @slateui/cli:init --baseColor=slate
ng g @slateui/cli:init --project=my-app --baseColor=neutral --confirmOverwrite=y
```

### `add` — Add a SlateUI directive from the registry

Installs directive files from the official SlateUI registry into your project.

Usage:

```bash
ng g @slateui/cli:add <itemName> [options]
```

Options:

- `itemName` (positional): Directive name, e.g., `button`, `badge`, `accordion`.
- `--all` (boolean): Add all available directives.

Examples:

```bash
ng g @slateui/cli:add button
ng g @slateui/cli:add --all
```

## Best practices

- Run `init` before `add` so your theme and styles are in place.
- Commit your changes before running schematics so you can easily review file edits.
- Prefer adding directives incrementally to keep your bundle lean.

- For monorepos with multiple apps, pass `--project <name>` to target the correct app.


## Documentation

Visit [https://slateui.dev/docs/cli](https://slateui.dev/docs/cli) to view the complete documentation.




## License

MIT © SlateUI
npm package: @slatham/quadtree
Description: Basic quadtree data structure
Author: S J Latham
Latest version: 1.0.5

# Quadtree
A simple javascript implementation of a quadtree data structure for storing 2d objects - [Quadtree](https://en.wikipedia.org/wiki/Quadtree)

For use in node or browser based projects.

## Usage

### Install
Use your node package manager to install, or if you're just using it in the browser, skip this.
```
npm install @slatham/quadtree
```

### Import
Include in your node project
```javascript
// import the module
const qt = require('@slatham/quadtree');
```
Or, if it is a browser-based project, include the file found in the build folder in your HTML
```HTML
<html>
  <head>
    <title>My Quadtree</title>
    <script src="/path/to/build/index.js"></script>
  </head>
```
### Define the properties of the quadtree
Set up the required properties of the quadtree
```javascript
// define the area of the quadtree
// qt.Rectangle(x, y, w, h)
const area = new qt.Rectangle(0, 0, 100, 100);

// define how many points each node should hold before sub-dividing
const maxPointsPerNode = 10;
```
### Create the quadtree
Will create a new quadtree
```javascript
// create the quadtree
const qtree = new qt.Quadtree(area, maxPointsPerNode);
```
### Insert points
Will insert a valid point into the quadtree
```javascript
// define a Point object
// qt.Point(x, y, data)
const point = new qt.Point(50, 50, 'Some test data');
// insert point
qtree.insertPoint(point);
```
### Query points
Will return a ```Set``` of Point objects for the area defined
```javascript
// define an area to query
// qt.Rectangle(x, y, w, h)
const queryArea = new qt.Rectangle(25, 25, 50, 50);
// query the quadtree
const points = qtree.queryPoints(queryArea);
```
### Get all points
Will return all points in the quadtree
```javascript
// get all points simply by omitting the query area parameter on queryPoints()
const allPoints = qtree.queryPoints(); 
```
## Examples
Two working examples can be found in the folders web_example and node_example.  To run the node example,
navigate to the node_example folder and run
```
node index.js
```
To run the web example that uses p5 to visualise the quadtree, open up web_example/index.html with your browser.
npm package: @slatwall/slatwall-sdk
Description: Slatwall SDK
Author: Slatwall Inc.
Latest version: 1.2.1

# Slatwall Commerce SDK

The Slatwall Commerce team is dedicated to making new tools and services available to development teams that make building, creating and launching eCommerce projects faster & easier. The Slatwall Commerce SDK will connect your Javascript Apps to Slatwall via our API.

## Resources

### API Documentation

The Slatwall API contains example scripts and endpoints to connect and interact with Slatwall.

https://publicapi.slatwallcommerce.com/

### User Documentation

The Slatwall User Guide provides documentation on how to use Slatwall features.

https://www.slatwallcommerce.com/user-guide/

### Slatwall Roadmap

Get insight into our future plans and when new features and functionality will be released.

https://www.slatwallcommerce.com/slatwall-roadmap/

## Examples

### Slatwall Storefront

See an example of how to integrate this sdk in an app.

https://github.com/ten24/slatwall-storefront-react
npm package: @slaughtr/apache-log-parser
Description: Nodejs Apache Log Parser
Author: Dallas Slaughter
Latest version: 1.0.1

# apache-log-parser
> Nodejs Apache Log Parser

Simple lib to naively parse Apache combined log format logs. Pass in a line from a log, get an object back.

This ONLY works with combined log format logs at the moment. 

Example usage:

```js
const logParser = require('@slaughtr/apache-log-parser');

const logObject = logParser({ string: someLogLine })

```
npm package: @slavab89/cz-conventional-changelog
Description: Commitizen adapter following the conventional-changelog with a slight tweak
Author: Jim Cummins
Latest version: 2.1.2

# cz-conventional-changelog

[![npm version](https://img.shields.io/npm/v/@slavab89/cz-conventional-changelog.svg?style=flat-square)](https://www.npmjs.org/package/cz-conventional-changelog)
[![npm downloads](https://img.shields.io/npm/dm/@slavab89/cz-conventional-changelog.svg?style=flat-square)](http://npm-stat.com/charts.html?package=cz-conventional-changelog&from=2015-08-01)

Part of the [commitizen](https://github.com/commitizen/cz-cli) family. Prompts for [conventional changelog](https://github.com/stevemao/conventional-changelog-angular/blob/master/index.js) standard.

The only change from the original package is that i place the ISSUES section at the `head` part instead of the footer.

When using Bitbucket it allows JIRA issues to be auto-highlighted.

The resulting commit message should look something like:
```
feat(adapter): ABC-123 This is my message

This is the body of the commit

BREAKING CHANGE: Something that breaks!
```
npm package: @slavamak/eslint-config
Description: ESLint sharable configs
Author: Slava Maksimov
Latest version: 1.2.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @slavamak/eslint-config

ESLint shareable configs.

## Installation

To use these configurations in your project, install the package via pnpm:

```bash
pnpm add -D @slavamak/eslint-config
```

## Usage

To use the ESLint configurations, create or update your `eslint.config.js` in your project root:

```javascript
import { configs } from "@slavamak/eslint-config";

export default [configs.ignore, configs.base, configs.node, configs.typescript];
```

## Available Configurations

- `base`: Basic configuration for JavaScript projects.
- `browser`: Configuration for browser environments.
- `node`: Configuration for Node.js applications.
- `react`: Configuration for React applications.
- `typescript`: Configuration for TypeScript projects.
- `remix`: Configuration for Remix applications.
- `ignore`: Configuration for ignoring certain files or patterns.

## Utils

This package also exports all utilities from the `eslint-flat-config-utils` package, which helps manage and manipulate ESLint flat config arrays. You can find more details [here](https://github.com/antfu/eslint-flat-config-utils).

## Example Usage

For a Node.js application without TypeScript:

```javascript
import { configs } from "@slavamak/eslint-config";

export default [configs.ignore, configs.base, configs.node];
```

For a Remix application with TypeScript:

```javascript
import { concat, configs } from "@slavamak/eslint-config";

export default concat(configs.remix, configs.typescript);
```

> [!NOTE]
> We use the `concat` utility here because `configs.remix` is actually an array of multiple configs. So we could use the spread operator or the `concat` utility.

You can easily modify any of configs using the `composer` utility:

```javascript
import { composer, concat, configs } from "@slavamak/eslint-config";

export default concat(
  await composer(configs.remix)
    .overrideRules({
      "n/no-unsupported-features/node-builtins": "error",
    })
    .override("@slavamak/eslint-config/base", {
      rules: {
        "no-console": "error",
      },
    }),
  configs.typescript,
);
```

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
npm package: @slavamak/tsconfig
Description: Shareable TSConfig configurations
Author: Slava Maksimov
Latest version: 1.3.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @slavamak/tsconfig

Shareable TSConfig configurations.

## Installation

To use these configurations in your project, install the package via pnpm:

```bash
pnpm add -D @slavamak/tsconfig
```

## Requirements

This package requires TypeScript version 5.5 or above. Make sure to have the appropriate version installed in your project.

## Usage

To use the TSConfig configurations, add the desired config to the `extends` property in your `tsconfig.json` file:

```json
{
  "extends": "@slavamak/tsconfig/remix.json"
}
```

You can also extend from multiple configurations by providing an array to the `extends` property:

```json
{
  "extends": [
    "@slavamak/tsconfig/base.json",
    "@tsconfig/deno/tsconfig.json"
  ]
}
```

## Available Configurations

This package includes a variety of configurations to suit different project needs. You can extend from any of the following:

- `base.json`: Basic configuration for TypeScript/JavaScript projects.
- `remix.json`: Configuration for Remix applications.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
npm package: @slaviczavik/http-data-parser
Description: A really fast Node.js streaming multipart parser.
Author: Jaroslav Zavodny
Latest version: 2.1.0

[![Build Status](https://travis-ci.com/slaviczavik/http-data-parser.svg?branch=master)](https://travis-ci.com/slaviczavik/http-data-parser)

# Description
An extremely fast Node.js module for parsing form data and primarily file uploads.

# Requirements
Node.js 6.14.3 or higher is required.

# Installation
```
npm i @slaviczavik/http-data-parser
```

# Example

```JS
const HttpDataParser = require('@slaviczavik/http-data-parser')

// A boundary must be extracted from 'content-type' request header.
const boundary '--------------------------034172598905589540726558'
const parser = HttpDataParser(boundary)

parser.on('header', function (data, isLast) {
  // Save headers somewhere...

  if (isLast) {
    // Here you may prepare for handling body data,
    // like create a writable stream and so on.
  }
})

parser.on('data', function (data) {
  // Save body content somewhere...
})

parser.on('part', function () {
  // We reached the end of one body part.
  // Here we can concate body content together.
})

parser.on('end', function () {
  // We reached the end of whole body.
  // No other data will come.
})

req.on('data', function (data) {
  parser.write(data)
})

req.on('end', function () {
  parser.end()
})
```

# API

## Constructor
### `HttpDataParser(boundary)`

| Name | Required | Type | Description | Default
| - | - | - | - | - |
| `boundary` | true | `string` | | `none` |

## Methods
The parser is a Node.js Writable Stream, so you can use the `write` and the `end` methods,
or just only the `pipe` method.

### `write(buffer)`

| Parameter | Required | Type | Description
| - | - | - | - |
| `buffer` | true | `buffer` | Buffer from request body. |

### `end()`
Call this method when there is no more data to be consumed from the stream.

## Events

### `header(data, isLast)`
Emitted every time when a parser find a header part.

| Property | Type | Description
| - | - | - |
| `data` | `buffer` | - |
| `isLast` | `boolean` | Signals if it is a last header part. |

### `data(data)`
Emitted every time when a parser find a content data.

| Property | Type | Description
| - | - | - |
| `data` | `buffer` | - |

### `part()`
Emitted every time when a parser reach the end of one body part.

### `end()`
Emitted when a parser reached the end of request body.
npm package: @slaviczavik/stream-search
Description: Event based module for searching streams.
Author: Jaroslav Zavodny
Latest version: 1.5.0

[![Build Status](https://travis-ci.com/slaviczavik/stream-search.svg?branch=master)](https://travis-ci.com/slaviczavik/stream-search)

# Description
Node.js event based module for searching streams using the Boyer–Moore–Horspool algorithm.

# Requirements
Node.js 6.14.3 or higher is required.

# Installation
```
npm i @slaviczavik/stream-search
```

# Example

## Code

```JS
const StreamSearch = require('@slaviczavik/stream-search')
const search = StreamSearch('AQD')

search.on('part', function (obj) {
  const isMatch = obj['isMatch']
  const start = obj['start']
  const end = obj['end']
  const data = obj['data']

  if (isMatch) {
    console.log(`Found! [${start} - ${end}]`)
  }
  else {
    console.log(`Not found!`)
  }

  if (data) {
    console.log(data.toString('ascii'))
  }
})

search.add('--AQD-QDD-DQD--')
search.end()
```
## Output

```
> Found! [2 - 4]
> --AQD
> Not found!
> -QDD-DQD--
```

# API

## Constructor
### `StreamSearch(needle, limit)`

| Name | Required | Type | Description | Default
| - | - | - | - | - |
| `needle` | true | `string`, `buffer` | The needle what we are searching for. | `none` |
| `limit` | false | `integer` | The maximum number of matches. | `Infinity` |

**Number of matches is reseted after the `end` method calling.**

## Methods

### `add(haystack)`
Call this method every time you receive a new stream data.
If there were some unprocessed data in the previous request, this data will be processed with this new data.

| Parameter | Required | Type | Description
| - | - | - | - |
| `haystack` | true | `string`, `buffer` | Your data you want to search. |

### `end()`
Calling this method you signals that no more data will be passed.
If there are some trailing data (too few to run the algorithm), this data will be emitted back to user.

## Events

### `part(object)`
Emitted every time a match was or was not made. In both case, a processed chunk of data is available.
If match was made, the needle is between start (inclusive) and end (inclusive).

The object contains following properties:

| Property | Type | Description
| - | - | - |
| `isMatch` | `boolean` | Bool value that data contains the needle. |
| `data` | `buffer` | Returned data from the haystack. |
| `start` | `integer`, `undefined` | Start position of needle (if any) in the haystack (inclusive). |
| `end` | `integer`, `undefined` | End position of needle (if any) in the haystack (inclusive). |

**The property end also indicates the end of the data.**
npm package: @slavshik/log
Description: Tiny log with styling for the browser console.
Author: Alexander Slavschik
Latest version: 0.0.21

# @slavshik/log
### As simple as possible
[![Version](https://img.shields.io/npm/v/@slavshik/log.svg)]([https://npmjs.org/package/tinylog](https://www.npmjs.com/package/@slavshik/log))
[![Downloads/week](https://img.shields.io/npm/dw/@slavshik/log.svg)](https://npmjs.org/package/@slavshik/log)
[![License](https://img.shields.io/npm/l/@slavshik/log.svg)](https://github.com/slavshik/log/blob/main/package.json)
### Example

```js
import {log} from "@slavshik/log";
// levels: 1 - fatal, 2 - info, 3 - error, 4 - warn, 5 - debug, 6 - trace (default is 2)
log.setLevel(6); // the larger the number, the higher the verbosity

// simple logging
log.trace("trace message");
log.debug("debug message");
log.info("info message");
log.error("error message");
log.warn("warn message");
log.fatal("fatal message");

// passing params
log.debug("debug message with array:", [1, 2, 3, 4], {a: 1, b: 2});
log.debug("debug message with object:", {a: 1, b: 2});
log.debug("debug message with number:", Math.random());

// using scopes
const scopedLog = log.scope("scope");
scopedLog.debug("debug message");
```
### Screenshots
<img src="https://i.ibb.co/d4k8FPM/logger-chrome.png" alt="Chrome (Dark)" />
<img src="https://i.ibb.co/rGB0NXf/logger-safari.png" alt="Safari" />
npm package: @slawekkolodziej/core
Description: Handles Next.js routing independent of provider
Author: Jan Varho
Latest version: 3.7.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @sls-next/core
> Core library for running serverless Next.js apps

This decouples the core Next.js handler logic from a particular platform.
The types defined are meant to be abstract to use with any provider.
It provides platform-agnostic handlers that can be extended for use on specific platforms.

Code coverage relies on jest configuration:

    "moduleNameMapper": {
      "@sls-next/core": "<rootDir>/packages/libs/core/src/index.ts"
    },

Builds twice, both a commonjs module (dist/index.js) and an ES module (dist/module/index.js).
The former is used by the serverless component, while the latter allows rollup to optimize size.

## build/

Contains logic needed for building manifests.

## route/

Contains routing logic.

Entry functions take manifests and request details and return Route objects.

## handle/

Contains logic for handling routes.

Entry functions take manifests and Events containing request/response.
They return unhandled routes or resolve the route to resp object given.