open-index/open-npm huggingface dataset:
npm package: @livecommands/js
Description: LiveCommands Framework - JavaScript implementation
Author: LiveCommands Maintainer
Latest version: 0.1.0

# @livecommands/core

> **Build CLI tools you'll love to maintain.**

The LiveCommands Framework brings commands to life through runtime discovery, intelligent help generation, and fluent interfaces that make CLI tools a joy to use and maintain.

## Philosophy

LiveCommands was born from the frustration of building CLI tools that become unmaintainable. We believe CLI development should be:

- **Fast** - Get from idea to working feature without fighting your tools
- **Clean** - Write code you'll be proud to read six months from now
- **Self-Documenting** - Your code *is* your documentation, always in sync
- **Discoverable** - Let users explore naturally, without digging through manuals

## Coming Soon

This is a placeholder package for the LiveCommands ecosystem. The actual implementation is currently being developed.

Follow our progress:
- [Specification](https://github.com/livecommands/spec)
- [LiveCommands/Lua](https://github.com/livecommands/lua)
- [LiveCommands/Java](https://github.com/livecommands/java)

## License

MIT
npm package: @livecycle.io/rrweb-snapshot
Description: rrweb's component to take a snapshot of DOM, aka DOM serializer
Author: yanzhen@smartx.com
Latest version: 1.1.7

# rrweb-snapshot

[![Build Status](https://travis-ci.org/rrweb-io/rrweb-snapshot.svg?branch=master)](https://travis-ci.org/rrweb-io/rrweb-snapshot) [![Join the chat at https://gitter.im/rrweb-io/rrweb-snapshot](https://badges.gitter.im/rrweb-io/rrweb-snapshot.svg)](https://gitter.im/rrweb-io/rrweb-snapshot?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

Snapshot the DOM into a stateful and serializable data structure.
Also, provide the ability to rebuild the DOM via snapshot.

## API

This module export following methods:

### snapshot

`snapshot` will traverse the DOM and return a stateful and serializable data structure which can represent the current DOM **view**.

There are several things will be done during snapshot:

1. Inline some DOM states into HTML attributes, e.g, HTMLInputElement's value.
2. Turn script tags into `noscript` tags to avoid scripts being executed.
3. Try to inline stylesheets to make sure local stylesheets can be used.
4. Make relative paths in href, src, CSS to be absolute paths.
5. Give an id to each Node, and return the id node map when snapshot finished.

#### rebuild

`rebuild` will build the DOM according to the taken snapshot.

There are several things will be done during rebuild:

1. Add data-rrid attribute if the Node is an Element.
2. Create some extra DOM node like text node to place inline CSS and some states.
3. Add data-extra-child-index attribute if Node has some extra child DOM.

#### serializeNodeWithId

`serializeNodeWithId` can serialize a node into snapshot format with id.

#### buildNodeWithSN

`buildNodeWithSN` will build DOM from serialized node and store serialized information in `__sn` property.
npm package: @livecycle/cli
Description: livecycle cli tool
Author: livecycle
Latest version: 0.1.11

Livecycle CLI - Link your preview environment to livecycle

<!-- toc -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->
# Usage
<!-- usage -->
```sh-session
$ npm install -g @livecycle/cli
$ livecycle COMMAND
running command...
$ livecycle (--version)
@livecycle/cli/0.1.11 darwin-arm64 node-v16.20.0
$ livecycle --help [COMMAND]
USAGE
  $ livecycle COMMAND
...
```
<!-- usagestop -->
# Commands
<!-- commands -->
* [`livecycle help [COMMAND]`](#livecycle-help-command)
* [`livecycle link`](#livecycle-link)

## `livecycle help [COMMAND]`

Display help for livecycle.

```
USAGE
  $ livecycle help [COMMAND] [-n]

ARGUMENTS
  COMMAND  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for livecycle.
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.1.19/src/commands/help.ts)_

## `livecycle link`

Link a url to livecycle document

```
USAGE
  $ livecycle link --api-key <value> --url <value> [--from-git <value>] [-d <value>] [--ref <value>]
    [--revision <value>] [--revision-timestamp <value>] [--author-email <value>] [--author-name <value>]
    [--author-avatar <value>] [--logs-url <value>] [--status done|progress|error]

FLAGS
  -d, --description=<value>     (required when not using git context) Description of the preview env
  --api-key=<value>             (required) API key for the service, can be generated by accessing user settings at
                                https://livecycle.dev
  --author-avatar=<value>       Author avatar url
  --author-email=<value>        (required when not using git context) Author email of the preview env
  --author-name=<value>         (required when not using git context) Author name of the preview env
  --from-git=<value>            Infer whatever fields possible from git, value is the base directory to be used
  --logs-url=<value>            Url to the build logs
  --ref=<value>                 (required when not using git context) Project ref - used to group playgrounds
                                Example: git://provider/owner/repo#branch
                                project://projectName#arbitraryDocumentName
  --revision=<value>            (required when not using git context) Revision of the preview env
  --revision-timestamp=<value>  (required when not using git context) Revision timestamp of the preview env
  --status=<option>             Status of the preview environment
                                <options: done|progress|error>
  --url=<value>                 (required) Url to be linked to the document

DESCRIPTION
  Link a url to livecycle document

EXAMPLES
  $ livecycle link --api-key DEh4uk0t.MCBGhR_pC --url https://yourawesomesite.com --from-git .
  Document linked to url succesfuly
```
<!-- commandsstop -->
npm package: @livecycle/sdk
Description: livecycle sdk
Author: livecycle
Latest version: 0.1.11

# ![Livecycle Logo](./assets/livecycle-logo-light.svg "Livecycle")
=================

This package is designed to give a solution for those who wish to use livecycle collaborative features
with their own preview environments.

Livecycle package is bundled with an sdk and a cli.

The sdk is used to create an agent within your html document to allow livecycle collaboration magic to happen.
While the CLI is used to link between your preview environment url to livecycle playground.

Setting up is as simple as it gets.


## Livecycle SDK
Integrate livecycle with your existing preview environment and enjoy contextual collaboration tools.


## Prerequisite

The livecycle SDK is intended to be used with projects that already have a working preview environment setup and wish to use livecycle collaboration solution.

If you or your team don't have a preview environment as part of your flow, you could use our end to end solution.

[read more](https://docs.livecycle.io/docs)

## Installation - with a package manager

```
npm i livecycle
```
or

```
yarn add livecycle
```

Initialize livecycle at the root of your project

```
import Livecycle from 'livecycle-sdk'


await Livecycle.init().catch(console.error)
```

## Browser Support

Livecycle can be used in any browser that supports es2018 features and above.


## How does it work?

We use the sdk to embed a script tag in your DOM that runs an agent in the background.

The agent job is to provide a communication channel between your environment and the livecycle application.
npm package: @livedigital/client
Description: [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://choosealicense.com/licenses/mit/) [![npm version](https://img.shields.io/npm/v/@livedigital/client.svg?style=flat)](https://www.npmjs.com/package/@livedigital/client) ![release
Author: vlprojects
Latest version: 3.55.1

# [LiveDigital](https://livedigital.space/) SDK
[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://choosealicense.com/licenses/mit/) [![npm version](https://img.shields.io/npm/v/@livedigital/client.svg?style=flat)](https://www.npmjs.com/package/@livedigital/client) ![release](https://github.com/vlprojects/livedigital-sdk/actions/workflows/release.yml/badge.svg)

## Installation

Use the package manager [npm](https://pip.pypa.io/en/stable/) or [yarn](https://yarnpkg.com/) to install livedigital-client.

```bash
yarn add @livedigital/client
```

## Usage

```
import Client from '@livedigital/client';

const client = new Client();
```

## Plugins
Now you can use the noise reduction and virtual backgrounds functionality. To do this, copy all the files from the
/files directory to the root directory of your project. Or your can specify the path in Client param staticFilesPath
And add tsvb-web.js scripts to your index.html
```
<script src="%PUBLIC_URL%/esdk/3.5.8/tsvb-web.js"></script>
```

## Development
### Submodules

To pull submodules required for the library build, use these commands:

```shell
git pull --recurse-submodules
git submodule update --init --recursive
```

## Debugging
### Log Levels
LiveDigital client uses the [debug](https://www.npmjs.com/package/debug) module to log to the browser console.

There are three log severities:

- **debug**: verbose information logged to console.info
- **warn**: warning messages logged to console.warn
- **error**: error messages logged to console.error

All the logs generated by LiveDigital client have a namespace starting with “LiveDigital”
plus colon, followed by the log severity in upper case plus colon (just if “warn” or “error”),
and followed by the internal component name (if any) and the log message.

### Enable Logging
By default, logging is turned off. In order to enable it, the debug key in the browser's
localStorage must be set.
>Check the [debug](https://www.npmjs.com/package/debug) module documentation for further information regarding how to filter specific log messages based on namespace matching rules.

### Example
Within the <head> section of your HTML app:
```
<script>
  window.localStorage.setItem('debug', 'LiveDigital:*');
</script>

<script src='/js/your-bundled-app.js'></script>
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @liveflow-io/kotlin-graphql-resolvers
Description: Not in use, be aware, maybe will be used in the future
Latest version: 0.0.2

# @liveflow-io/kotlin-graphql-resolvers

Not in use, be aware, maybe will be used in the future

## Config options

###`package?: string`

@description Customize the Java package name. The default package name will be generated according to the output file path.

@example

```yml
generates:
  src/main/kotlin/my-org/my-app/Resolvers.kt:
    plugins:
      - kotlin
    config:
      package: custom.package.name
```



### `enumValues?: EnumValuesMap`

@description Overrides the default value of enum values declared in your GraphQL schema.

@example

```yml
config:
  enumValues:
    MyEnum:
      A: 'foo'
```


@default Iterable
@description Allow you to customize the list type

@example

```yml
generates:
  src/main/kotlin/my-org/my-app/Types.kt:
    plugins:
      - @liveflow-io/kotlin-graphql-resolvers
    config:
      listType: Map
```

listType?: string


### `enumsPackage?: string`
@default true

@description Generates enums import, to be used in conjunction with `generateTypes`

@example

```yml
generates:
  src/main/kotlin/my-org/my-app/Types.kt:
    plugins:
      - @liveflow-io/kotlin-graphql-resolvers
    config:
      enumsPackage: 'com.example.enums.'
      generateTypes: true
      generateEnums: false
```


### `generateEnums?: boolean`

@default true

@description Generates enums, you can set false to disable enum generation

@exampleMarkdown

```yml
generates:
  src/main/kotlin/my-org/my-app/Enums.kt:
    plugins:
      - @liveflow-io/kotlin-graphql-resolvers
    config:
      generateEnums: true
      generateTypes: false
```

###`generateTypes?: boolean`

@default true

@description Generates types only, to be used in conjunction with `enumsPackage` to get enums from somewhere

@example

```yml
generates:
  src/main/kotlin/my-org/my-app/Types.kt:
    plugins:
      - @liveflow-io/kotlin-graphql-resolvers
    config:
      generateEnums: false
      generateTypes: true
      enumsPackage: 'com.example.enums.'
```
npm package: @livefolio/cli
Description: Livefolio CLI
Author: Livefolio
Latest version: 0.1.2

# @livefolio/cli

Command-line interface for Livefolio market data, built on `@livefolio/sdk`.

## Install

```bash
npm install -g @livefolio/cli
```

## Setup

Copy the example env file and fill in your Supabase credentials:

```bash
cp .env.example .env.local
```

For local development with `supabase start`, the defaults in `.env.example` work out of the box.

## Usage

```bash
# Load env and fetch historical series
livefolio --env .env.local market series SPY

# Fetch multiple symbols at once
livefolio --env .env.local market series SPY QQQ

# Get real-time quotes
livefolio --env .env.local market quotes SPY QQQ

# Output is CSV (symbol,timestamp,price), pipe-friendly
livefolio --env .env.local market series SPY | head -5
# symbol,timestamp,price
# SPY,2025-01-10T16:00:00Z,590.25
# SPY,2025-01-11T16:00:00Z,592.10
# SPY,2025-01-12T16:00:00Z,588.50

# Fetch a strategy definition
livefolio --env .env.local strategy get bCicNI7OI2x

# Evaluate a strategy (signals, allocation, indicators)
livefolio --env .env.local strategy evaluate bCicNI7OI2x

# Evaluate as of a specific date
livefolio --env .env.local strategy evaluate bCicNI7OI2x --at 2025-05-12T21:00:00Z

# With env vars exported, --env is not needed
export SUPABASE_URL=https://your-project.supabase.co
export SUPABASE_ANON_KEY=your-anon-key
livefolio market series SPY > spy.csv
```

## Commands

| Command | Description |
|---------|-------------|
| `market series <symbols...>` | Fetch historical daily series for one or more symbols (CSV) |
| `market quotes <symbols...>` | Get current price for one or more symbols (CSV) |
| `strategy get <link_id>` | Fetch a strategy definition and output as JSON |
| `strategy evaluate <link_id> [--at <date>]` | Evaluate a strategy and output the result as JSON |

## Development

```bash
npm install
npm run build
npm test             # run tests
node dist/cli.js --env .env.local market series SPY
```

## CI/CD

- PRs to `main` run build, tests, and enforce a version bump
- Merges to `main` auto-publish to npm and create a GitHub release

Before merging, bump the version:

```bash
npm version patch
```

## License

MIT
npm package: @liveframe/liveframe
Description: Client JS for LiveFrame.io Frame Capture SaaS
Author: LiveFrame.io
Latest version: 1.0.3

# LiveFrame JS Client

Send user streams to the LiveFrame service.

## Installation

Require the package using npm:

```bash
npm i @liveframe/liveframe
```

## Usage

```js
import LiveFrame from 'liveframe';

const liveframe = new LiveFrame({
    token: token,
    options: options
});

liveframe.video.addStream({
    type: type,
    stream: new ImageCapture(stream_track),
});
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License
[MIT](./LICENSE.md)
npm package: @livefyre/urnlib
Description: A Livefyre URN utility.
Author: jaklaassen
Latest version: 1.0.0

# urnlib.js
A library for handling Livefyre URNs.

## Example
    urnlib = require("urnlib");
    var urnStr = 'urn:livefyre:network=livefyre.com:site=123456:collection=100000';
    var urn = urnlib.parse(urnStr);
npm package: @livekit-vue/vue-bar-visualizer
Description: Vue 3 BarVisualizer component with state-driven highlights for LiveKit Agents. No Tailwind required.
Latest version: 0.2.1

### Vue BarVisualizer

Vue 3 BarVisualizer component. Visualizes audio levels as animated bars and supports agent state-driven highlight animations. No TailwindCSS required.

### Install

Build locally and add as a file dependency (or publish to your registry):

```bash
cd vue-components
pnpm install
pnpm build
```

Then in your app `package.json`:

```json
{
  "dependencies": {
    "@livekit-vue/vue-bar-visualizer": "file:../vue-components"
  }
}
```

### Usage

Basic usage with a MediaStreamTrack:

```vue
<script setup lang="ts">
import { ref, onMounted } from "vue";
import { BarVisualizer } from "@livekit-vue/vue-bar-visualizer";

const micTrack = ref<MediaStreamTrack | null>(null);

onMounted(async () => {
  const stream = await navigator.mediaDevices.getUserMedia({ audio: true });
  micTrack.value = stream.getAudioTracks()[0] ?? null;
});
</script>

<template>
  <BarVisualizer :track="micTrack" state="listening" :bar-count="15" />
  <!-- Place inside a container with a defined height. Default is 5rem. -->
</template>
```

#### Global install (plugin)

```ts
// main.ts
import { createApp } from "vue";
import App from "./App.vue";
import { VueBarVisualizer } from "@livekit-vue/vue-bar-visualizer";

createApp(App).use(VueBarVisualizer).mount("#app");
```

Using a MediaStream:

```vue
<BarVisualizer :track="myStream" state="speaking" />
```

Custom bar template via slot:

```vue
<BarVisualizer :track="micTrack">
  <template #bar="{ highlighted, index, style }">
    <div :style="{
      ...style,
      width: '0.25rem',
      borderRadius: '0.25rem',
      backgroundColor: highlighted ? 'var(--lk-fg, #0ea5e9)' : 'var(--lk-va-bg, #94a3b8)',
      transition: 'height 150ms ease-out, background-color 150ms ease-out'
    }" />
  </template>
  <!-- Each bar also gets data-lk-highlighted and data-lk-bar-index attributes -->
  <!-- And uses CSS variables --lk-va-bg and --lk-fg by default -->
  <!-- Default container: flex layout, 0.25rem gap, 5rem height -->
  <!-- Default bar: 0.25rem width, rounded, background uses CSS vars -->
  <!-- When highlighted adds class lk-highlighted and bg var --lk-fg -->
  <!-- Provide your own #bar slot to fully customize markup -->
  
</BarVisualizer>
```

### Props

- state?: 'connecting' | 'initializing' | 'listening' | 'thinking' | 'speaking'
- barCount?: number (default 15)
- track?: MediaStreamTrack | MediaStream | null
- options?: { minHeight?: number; maxHeight?: number } heights in percent (0-100)

### Notes

- Requires browser environment with WebAudio API.
- Customize colors via CSS variables on a container:
  ```css
  .my-container {
    --lk-va-bg: #94a3b8;
    --lk-fg: #0ea5e9;
  }
  ```