open-index/open-npm huggingface dataset:
npm package: @steremoon/lib1
Description: Library 1
Author: kirinnee
Latest version: 0.0.3

﻿## Library 1
Library 1

## Getting started
### Client Depedencies

### Usage
 
## Contributing
Please read [CONTRIBUTING.md](CONTRIBUTING.MD) for details on our code of conduct, and the process for submitting pull requests to us.

## Versioning
We use [SemVer](https://semver.org/) for versioning. For the versions available, see the tags on this repository.

## Authors
* kirinnee

## License
This project is licensed under the MIT - see the [LICENSE.md](LICENSE.MD) file for details
npm package: @steremoon/lib2
Description: libaray 2 
Author: kirinnee
Latest version: 0.0.2

﻿## Library 1
libaray 2 

## Getting started
### Client Depedencies

### Usage
 
## Contributing
Please read [CONTRIBUTING.md](CONTRIBUTING.MD) for details on our code of conduct, and the process for submitting pull requests to us.

## Versioning
We use [SemVer](https://semver.org/) for versioning. For the versions available, see the tags on this repository.

## Authors
* kirinnee

## License
This project is licensed under the MIT - see the [LICENSE.md](LICENSE.MD) file for details
npm package: @sterensoftware/hmx
Description: HMX is a small library for writing simpler, more declarative React Components. It embraces using React for its strengths as a rendering library, and separating such rendering from the "functional core" of application business logic.
Author: Copyright
Latest version: 0.2.2

# HMX

HMX is a small library for writing simpler, more declarative React Components. It embraces using React for its strengths as a rendering library, and separating such rendering from the "functional core" of application business logic.

---

## Installation

```
npm install --save @sterensoftware/hmx
```

## Available Components

## `Render`

```
<Render when={[boolean expression]}>{props =>
  [more JSX]
}</Render>
```

`Render` is a component that simply renders its child component when the given expression is truthy (otherwise `null`).  `Render` tries to be lenient; above is the recommmended form.

_Note: If your code has trouble evaluating children of `Render` due to e.g. missing state, double-check that you're wrapping those children with a component function.  Otherwise, those children will be **always** be evaluated, even when never displayed. (How silly!)_

## `WithState`

```
<WithState from={ownProps => ({[additional state props]})}>{mergedProps =>
  [state-dependent JSX]
}</WithState>
```

`WithState` leverages(/is declaritive syntactic sugar for) `connect` from `react-redux` to make it easy to source `state` from your application's "core".
npm package: @sterensoftware/hmx-testing
Description: HMX Testing supports React Component unit-testing by facilitating the mocking of the 3rd party dependencies: `react`, `react/jsx-runtime`, `react/jsx-dev-runtime`, and `@sterensoftware/hmx`.
Author: Copyright
Latest version: 0.2.1

# HMX Testing

HMX Testing supports React Component unit-testing by facilitating the mocking of the 3rd party dependencies: `react`, `react/jsx-runtime`, `react/jsx-dev-runtime`, and `@sterensoftware/hmx`.

It was designed and built to support true unit-testing of simple, declarative (logic-less) Components.


---


## **Installation**

```
npm install -D @sterensoftware/hmx-testing
```


## **Usage**

## Mocking `@sterensoftware/hmx`

```
jest.mock('@sterensoftware/hmx', () => jest.requireActual('@sterensoftware/hmx-testing').hmx())
```
or
```
jest.mock('@sterensoftware/hmx', () => jest.requireActual('@sterensoftware/hmx-testing').hmx({ debug: true }))
```

Replaces [HMX](https://www.npmjs.com/package/@sterensoftware/hmx)'s `WithState` component function with a mock (`jest.fn()`) that returns an object with `from` and `render`.

Passing `{ debug: true }` will result in output to the console.


## Mocking `react`

```
jest.mock('react', () => jest.requireActual('@sterensoftware/hmx-testing').react())
```
or
```
jest.mock('react', () => jest.requireActual('@sterensoftware/hmx-testing').react({ debug: true }))
```

Use to mock `React.createElement` when testing with the "classic" runtime (or older versions of React).  Will evaluate functional components and yield each element as an object with a `tagName`, `props`, and `children`.

Passing `{ debug: true }` will result in output to the console.


## Mocking `react/jsx-runtime` or `react/jsx-dev-runtime`

```
jest.mock('react/jsx-runtime', () => jest.requireActual('@sterensoftware/hmx-testing').jsx())
```
or
```
jest.mock('react/jsx-runtime', () => jest.requireActual('@sterensoftware/hmx-testing').jsx({ debug: true }))
```
or
```
jest.mock('react/jsx-dev-runtime', () => jest.requireActual('@sterensoftware/hmx-testing').jsx())
```
or
```
jest.mock('react/jsx-dev-runtime', () => jest.requireActual('@sterensoftware/hmx-testing').jsx({ debug: true }))
```

Use consistent with however you chose/choose to setup the "automatic" runtime to evaluate functional components and yield each element as an object with a `tagName`, `props`, and `children`.

Passing `{ debug: true }` will result in output to the console.
npm package: @sterensoftware/sniplates
Description: Helper library enabling programatic usage of variable-based TextMate snippets.
Author: Copyright
Latest version: 0.3.0

# Sniplates

Helper library enabling programatic usage of variable-based TextMate snippets.

---

## Installation

```
npm install --save @sterensoftware/sniplates
```

## Available named imports

## `loadSnippetTemplates`

```
await loadSnippetTemplates(<file path(s)>)
```

`loadSnippetTemplates` will resolve with an object with a `render` method, as well as access to any raw `templates` and `snippets`.
npm package: @stereo-bot/lavalink
Description: An easy-to-use package for interacting with Lavalink based off Erela.js & Lavaclient
Author: DaanGamesDG
Latest version: 1.2.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

<h1 align="center">@stereo-bot/lavalink</h1>

> An easy-to-use package for interacting with Lavalink with built-in Spotify and Deezer support (plugins must be added to the plugins array in-order to work). based off [Erela.js](https://github.com/MenuDocs/erela.js) & [Lavaclient](https://github.com/lavaclient)

- [Documentation](https://lavalink.stereo-bot.tk)

## Install

```sh
yarn add / npm install @stereo-bot/lavalink
```

## Usage

Extremely simple example

```js
const { Client } = require("discord.js");
const { Manager, Deezer, Spotify } = require("@stereo/lavalink");

const client = new Client({ intents: ["GUILD_VOICE_STATES", "GUILD_MESSAGES", "GUILDS"] });
const manager = new Manager(nodes, options);

client.on("ready", () => {
	console.log("ready");
	manager.init(client.user.id);
});

client.ws.on("VOICE_STATE_UPDATE", (data) => manager.voiceStateUpdate(data));
client.ws.on("VOICE_SERVER_UPDATE", (data) => manager.voiceServerUpdate(data));

client.on("messageCreate", async (message) => {
	if (message.content.includes("-start")) {
    const song = message.content.replace("-start", "");
		const player = manager.create({ guild: message.guild.id });
		const song = (await player.search(song, message.author.id, "yt")).tracks[0];

    if (!song) return message.reply("no song found");

		player.queue.add(song);
		player.setVoice(message.member.voice.channelId);
		player.setText(message.channelId);

    message.reply(`Successfully enqueued ${song.title}`);

		player.connect();
		player.play();

	}
);

manager.on("socketConnect", (socket) => console.log(`Socket online: ${socket.options.id}`));
manager.on("socketError", ({ socket, error }) =>
	console.log(`Socket error (${socket.options.id}): ${error.message ?? error.stack}`)
);

client.login("token");
```

## Author

👤 **DaanGamesDG**

- Website: https://daangamesdg.wtf/
- Email: <daan@daangamesdg.wtf>
- Twitter: [@DaanGamesDG](https://twitter.com/DaanGamesDG)
- Github: [@DaanGamesDG](https://github.com/DaanGamesDG)

## Donate

This will always be open source project, even if I don't receive donations. But there are still people out there that want to donate, so if you do here is the link [@PayPal](https://paypal.me/daangamesdg). Thanks in advance! I really appriciate it <3

## Lisence

Project is licensed under the © [**MIT License**](/LICENSE)

---
npm package: @stereobooster/cookie
Description: Tiny cookie library
Latest version: 1.1.5

# @stereobooster/cookie

Minimal cookie library (< 550B compressed) for browser. Fork of [Cookie component](https://github.com/component/cookie).

## Installation

```sh
yarn add @stereobooster/cookie
```

## Example

```js
// set
cookie("name", "tobi");
cookie("name", "tobi", { path: "/" });
cookie("name", "tobi", { maxage: 60000 }); // in milliseconds
cookie("species", "ferret");

// get
var name = cookie("name");
// => "tobi"

var cookies = cookie();
// => { name: "tobi", species: "ferret" }

// clear
cookie("name", null);
```

## License

MIT
npm package: @stereobooster/cyto-nodejs
Description: Render graphs on the server side with Cytoscape.js, getting image file as output
Author: stereooboster
Latest version: 0.0.2

# cyto-nodejs

Rendes graphs on the server side with Cytoscape.js, getting image file as output. This package is alternative to [cytosnap](https://github.com/cytoscape/cytosnap), but uses `jsdom` instead of Puppeteer.

Can be used like this:

```
npx @stereobooster/cyto-nodejs -s g2.json -d g2.svg
```

## TODO

- [ ] github actions to run tests
npm package: @stereobooster/cyto-snap
Description: Render graphs on the server side with Cytoscape.js, getting image file as output
Author: stereooboster
Latest version: 0.0.3

# cyto-snap

~~Full of hacks~~ Experimental package to demo how one can use Tauri instead of Puppeteer or Playwright.

Render graphs on the server side with Cytoscape.js, getting image file as output. This package is similar to [cytosnap](https://github.com/cytoscape/cytosnap), but is uses Tauri instead of Puppeteer.

## TODO

- Finish configuration of github actions
  - [ ] check release flow
  - [ ] add action to create releses for tags and publish Tauri installers to release
- write more tests
  - [ ] test `jpg`
  - [ ] test `STDIN` / `STDOUT`
  - test edge cases
    - [ ] none existent file
    - [ ] none existen folder
    - [ ] broken JSON
    - [ ] wrong values is JSON
  - [ ] test all [the rest of layouts](https://js.cytoscape.org/#extensions/layout-extensions) 
- [ ] Add TypeScript signatures

## Development

1. Install `rustup` or similar
   1. Install rust
2. Install `pnpm`
   1. Instal node packages `pnpm install`
3. Build `pnpm tauri build`, `pnpm tauri-postbuild`
4. Test `pnpm test`
npm package: @stereobooster/facets
Description: Client-side (though you can run it on the server) faceted search engine
Author: stereobooster
Latest version: 0.1.1

# Facets

**Facets** is a client-side (though you can run it on the server) faceted search engine.

> Facet - any of the definable aspects that make up a subject (as of contemplation) or an object (as of consideration)

**Facets** main purpose is to do the faceting aspect of the search. Text search is outsourced to other libraries, for example, you can use:

- [QuickScore](https://github.com/fwextensions/quick-score)
- [MiniSearch](https://github.com/lucaong/minisearch)
- [Fuse.js](https://github.com/krisk/fuse)
- [flexsearch](https://github.com/nextapps-de/flexsearch)
- and you can write an adapter for any other text search engine

The main secret ingredient is [TypedFastBitSet.js](https://github.com/lemire/TypedFastBitSet.js/) - a fast set data structure. Using it and standard `Map` allows us to build an inverted-index data structure. From there, it's a pretty straightforward implementation.

## Demo

It is easier to show than explain. [See online demo here](https://facets-demo.stereobooster.com/).

## Is it ready for production?

The demo works, as you can see, but beyond that, there was no exhaustive testing. There are still rough edges. API can change.

## TODO

- default values for facet by type
  - number
    - sort by value asc
    - `showZeroes=false`
- [initialization](/notes/initialization.md)
- [memoization](/notes/memoization.md)
- `​maxValuesPerFacet`
- `facets: "price"`
- numeric filter
  - support `>` (not just `>=`), `<` (not just `<=`)
  - support multiple ranges e.g `[{ from, to }, { eq }, { neq }]`
- more tests
- errors and warnings, for example
  - warn if people try to use text search without providing text index
- [benchmarks](https://github.com/tinylibs/tinybench)
  - performance seems to be good (except numeric range filter), but in order to be sure we need to do benchmark
- benchmark memory
  - https://www.valentinog.com/blog/node-usage/
  - I'm curious if using TrieMap would allow to save memory
npm package: @stereobooster/facets-instantsearch
Description: InstantSearch.js adapter for facets
Author: stereobooster
Latest version: 0.1.0

# facets-instantsearch

[InstantSearch](https://github.com/algolia/instantsearch) adapter for [facets](https://github.com/stereobooster/facets)

## TODO

- add tests
  - [SearchRequestAdpater.test.js](https://github.com/typesense/typesense-instantsearch-adapter/blob/master/test/SearchRequestAdpater.test.js)
  - [Add search parameters with JSON](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/rules-query-parameters/)
  - [numericFilters](https://www.algolia.com/doc/api-reference/api-parameters/numericFilters/)
  - [facetFilters](https://www.algolia.com/doc/api-reference/api-parameters/facetFilters/)
  - [filters](https://www.algolia.com/doc/api-reference/api-parameters/filters/)
- update readme
  - [instantsearch-itemsjs-adapter](https://github.com/unplatform-io/instantsearch-itemsjs-adapter/blob/main/README.md) is a good example
- implement `processingTimeMS`