open-index/open-npm huggingface dataset:
npm package: @ojshua/zmq-request
Description: zeromq REQ with renewed socket and Promise response
Author: ej.santoemma@gmail.com
Latest version: 0.2.3

__zeromq REQ with renewed socket and Promise response__

This package wraps a REQ socket from the [zeromq](https://www.npmjs.com/package/zeromq) package.

Reusing the same REQ socket for repeating requests in an async environment (Node.js) is not easy, as 0MQ requires to read the reply before sending a new one.

This package opens a new socket, sends the request, waits for the reply, closes the socket and resolves the Promise.

```javascript
const
  log = console.log,
  Request = require('zmq-request'),
  zmq = require('zeromq');

// minimal echo server
rep = zmq.socket('rep').bindSync('tcp://*:3000');
rep.on('message', raw => rep.send(raw));

const request = new Request({ port: 3000 });
request
  .send({ ok: true })
  .then(log)   // { ok: true }
  .catch(log)
  .then(() => rep.close())
```

Multiple parallel requests
```javascript
const
  log = console.log,
  Request = require('zmq-request'),
  zmq = require('zeromq');

// minimal echo server
rep = zmq.socket('rep').bindSync('tcp://*:3000');
rep.on('message', raw => rep.send(raw));

const request = new Request({ port: 3000 });
Promise.all([
  request.send({ data: 1 }),
  request.send({ data: 2 }),
  request.send({ data: 3 }),
  request.send({ data: 4 }),
  request.send({ data: 5 })
])
  .then(log)  // [ { data: 1 }, { data: 2 }, { data: 3 }, { data: 4 }, { data: 5 } ]
  .catch(log)
  .then(() => rep.close());
```
npm package: @ojuras/terminalplayer
Description: Allows you to play .mp3 and .wav sounds on the Windows terminal
Author: Felipe "Juras" Sartore
Latest version: 1.0.2

# terminalPlayer
Allows you to play .mp3 and .wav sounds on the Windows terminal

## Installation

    npm i @ojuras/terminalplayer

## Examples

```javascript
const tPlayer = require('@ojuras/terminalplayer');

tPlayer.playFrom('./sample.mp3');

tPlayer.playFrom('./../../sound.wav');

tPlayer.playFrom('C:/Program Files/audioSamples/track1.mp3');
```

## License

MIT
npm package: @ojvazquez/node-trace
Description: Simple node tracing library
Author: Walberto Ibarra
Latest version: 1.0.1

# node-trace

[![js-semistandard-style](https://img.shields.io/badge/code%20style-semistandard-brightgreen.svg?style=flat-square)](https://github.com/Flet/semistandard)

Simple node tracing library (ES6) for logging to stdout, stderr and JSON files using [bunyan](https://github.com/trentm/node-bunyan).

## Installation

```
$ npm i -S @ojvazquez/node-trace
```

## Example

```js
const Trace = require('@ojvazquez/node-trace');

// Should call init() once before using the library.
Trace.init({
  appName: 'node-trace',
  logFolder: './logs',
  isDev: false
});

Trace.info('Hello world');

try {
	throw new Error();
} catch(err) {
	Trace.error('Something went wrong', err);
}
```

**Note**: Add `logs/` to your *.gitignore* file.

## API

> All functions on class Trace are **static**, meaning you that should not instance it.

### Trace.init([options])

> Should call this function once before using the library.

`options`: an optional object containing some configuration:
- **appName**: the name of your application, defaults to `node-trace`
- **logFolder**: where to store the log files, defaults to `logs/`
- **isDev**: whether to output to files or stdout, defaults to false if
*NODE_ENV* is *test* or *production*

### Trace.fatal(msg, [err])

> The service/app is going to stop or become unusable now. An operator should definitely look into this soon.

`msg`: String, message to log on *error.json* file.

`err`: Object (optional), exception stack.

### Trace.error(msg, [err])

> Fatal for a particular request, but the service/app continues servicing other requests. An operator should look at this soon(ish).

`msg`: String, message to log on *error.json* file.

`err`: Object (optional), exception stack.

### Trace.warn(msg, [fields])

> A note on something that should probably be looked at by an operator eventually.

`msg`: String, message to log on *warn.json* file.

`fields`: Object (optional), merged into the log record.

### Trace.info(msg, [fields])

> Detail on regular operation.

`msg`: String, message to log on *info.json* file.

`fields`: Object (optional), merged into the log record.

### Trace.debug(msg, [fields])

> Anything else, i.e. too verbose to be included in "info" level.

`msg`: String, message to log on *info.json* file.

`fields`: Object (optional), merged into the log record.

### Trace.trace(msg, [fields])

> Logging from external libraries used by your app or very detailed application logging.

`msg`: String, message to log on *info.json* file.

`fields`: Object (optional), merged into the log record.
npm package: @ok2ju/simple-multi-peer
Description: WebRTC multi-peer made simple
Author: Alexey Vakulich
Latest version: 0.2.1

# Simple Multi Peer

WebRTC multi-peer communication made simple (using [simple-peer](https://github.com/feross/simple-peer))

**Note**: This is a fork of [simple-multi-peer](https://github.com/nihey/simple-multi-peer). Many thanks to Nihey Takizawa

# Installation
```
$ npm install --save @ok2ju/simple-multi-peer
```

# Usage

As a signalling server it is recommended to use [peer-hub](https://github.com/nihey/node-peer-hub).

```javascript
import SimpleMultiPeer from 'simple-multi-peer';

const Peers = new SimpleMultiPeer({
  server: 'ws://localhost:3000', // Your signaller URL.
  room: 'foobar',                // Which 'room' you'll be using to communicate with your peers
                                 // (all peers in the same room will be signalled to each other).
  callbacks: {                   // Connection related callbacks
    connect: (id) => {},         // -> 2 peers are connected
    close: (id) => {},           // -> a connection is closed
    data: (id, data) => {},      // -> any data is received
    stream: (id, stream) => {},  // -> audio/video stream
  },
  peerOptions: {},               // SimplePeer options (check https://github.com/feross/simple-peer#peer--new-simplepeeropts)
  connectionOptions: {},         // Socket.io connection options (see https://socket.io/docs/client-api/#manager)
});

// Send data over a dataChannel to all peers
Peers.send("I'm alive!!!");
```
npm package: @ok8omk/vinput
Description: Vi like input component in React
Author: ok8omk
Latest version: 1.0.2

# Vinput

Vi like `<input>` React Component.

## Try it

[:octocat: Github pages](https://ok8omk.github.io/Vinput)

## Component Interface

```js
/**
 * [Vinput]
 * @param  {string} [name]                         Input name props.
 * @param  {number} [width=500]                    Component width.
 * @param  {number} [fontSize=24]                  Component font size.
 * @param  {string} [fontFamilies=["Inconsolata"]] Component font families. monospace fonts are recommended.
 */
```

## Font configuration

By default, this component uses Inconsolata font.
Therefore append this link tag in head tag.

```html
<link
  href="https://fonts.googleapis.com/css?family=Inconsolata&display=swap"
  rel="stylesheet"
/>
```

If you wanna use another font, inject the font reference.
Also you have to assign correspond font for Vinput arguments.

## Usage Example

```tsx
<Vinput
  name="email"
  width={1024}
  fontSize={18}
  fontFamilies={["Noto", "Inconsolata"]}
/>
```
npm package: @ok_engineering/llamalabs_studio
Description: The official TypeScript SDK for LlamaLabs Studio.
Author: LlamaLabs
Latest version: 1.0.3

# LlamaLabs Studio SDK

The official TypeScript/JavaScript client for the [LlamaLabs Studio](https://llamalabs.studio) Unified AI Gateway.

LlamaLabs provides a single, unified interface to interact with the world's most powerful frontier models (OpenAI, Anthropic, Google Gemini, DeepSeek, Mistral, and Perplexity) without managing multiple API keys or dealing with varying payload structures.

## Installation

```bash
npm install @ok_engineering/llamalabs_studio
```

## Quick Start

```typescript
import { LlamaLabs } from '@ok_engineering/llamalabs_studio';

// Automatically picks up process.env.LLAMAKEY
const client = new LlamaLabs();

async function main() {
  const response = await client.chat.completions({
    model: 'claude-opus-4-6', // Route to any model in the LlamaLabs Zoo!
    messages: [{ role: 'user', content: 'Explain quantum computing in one sentence.' }]
  });
  
  console.log(response.output);
}

main();
```

## Authentication

The SDK requires a LlamaLabs API Key (LlamaKey). You can generate one in the **Developer Bridge** within your LlamaLabs Studio dashboard.

You can either pass it explicitly during initialization:
```typescript
const client = new LlamaLabs({ apiKey: 'LL-your-key-here' });
```
Or set it as an environment variable (recommended):
```bash
export LLAMAKEY="LL-your-key-here"
```

## License

MIT
npm package: @okaapp/oka-ui-sv
Description: OKA UI Svelte components library for the Appta software platform
Latest version: 0.4.6

# OKA UI for Svelte

OKA Tech UI Svelte component library built for the Appta software platform, offering a collection of customizable, accessible, and themeable components.

## Installation

```bash
npm install @okaapp/oka-ui-sv
```

### Required Peer Dependencies

This library requires the following peer dependencies to be installed:

```bash
npm install svelte@^5.0.0 @sveltejs/kit@^2.22.0 bits-ui@^2.9.8 phosphor-svelte@^3.0.1
```

## Setup

### 1. Style Provider

All components must be wrapped in the `OKAStyleProvider` component for proper styling. Add it to your root layout file:

```svelte
<!-- src/routes/+layout.svelte -->
<script lang="ts">
    import { OKAStyleProvider } from "@okaapp/oka-ui-sv";
</script>

<OKAStyleProvider>
    <slot />
</OKAStyleProvider>
```

### 2. Theme Setup

To avoid Flash of Unstyled Content (FOUC), add the following script to your app's HTML file:

```html
<!-- src/app.html -->
<body>
    <div>%sveltekit.body%</div>
    <script>
        const savedTheme = localStorage.getItem('theme') || 'default-light';
        document.body.classList.add(savedTheme);
    </script>
</body>
```

## Available Themes

OKA UI comes with several built-in themes:

- Light themes:
  - `default-light`
  - `neutral-light`
  - `nord-light`

- Dark themes:
  - `default-dark`
  - `neutral-dark`
  - `nord-dark`

- Fengshui themes:
  - `fengshui-kim` (Metal)
  - `fengshui-moc` (Wood)
  - `fengshui-thuy` (Water)
  - `fengshui-hoa` (Fire)
  - `fengshui-tho` (Earth)

## Components

### Core Components as of 0.4.2

- Avatar
- Badge
- Button
- Checkbox
- Dialog
- Input
- Loading
- Pagination
- PinInput
- Select (Single & Multi)
- Separator
- Sidebar
- Tooltips

### Usage Example

```svelte
<script>
    import { Button, Avatar, Badge } from "@okaapp/oka-ui-sv";
</script>

<Button variant="primary">Click me</Button>

<Avatar src="/path/to/image.jpg" alt="User avatar" size="md" />

<Badge color="success">Complete</Badge>
```

## Theme Switching

The library includes a `ThemeSwitcher` component for easy theme management:

```svelte
<script>
    import { ThemeSwitcher } from "@okaapp/oka-ui-sv";
</script>

<ThemeSwitcher />
```

## Contributing

Contributions are welcome! Please read our contributing guidelines before submitting pull requests.

## License

MIT License - see LICENSE file for details.

## Acknowledgments

Built with:
- [Svelte](https://svelte.dev)
- [SvelteKit](https://kit.svelte.dev)
- [bits-ui](https://bits-ui.com)
- [phosphor-svelte](https://github.com/phosphor-icons/svelte)