open-index/open-npm huggingface dataset:
npm package: @launchscout/wc-context
Description: Fork of original wc-context to export a couple things
Author: Luiz Américo Pereira Câmara
Latest version: 1.0.1

# wc-context

> A comprehensive context implementation for web components

### Features

&nbsp; &nbsp; ✓ Small and fast. No Internet Explorer support<br>
&nbsp; &nbsp; ✓ Flexible ways to define context providers and consumers<br>
&nbsp; &nbsp; ✓ Ability to provide or consume one or more contexts per element<br>
&nbsp; &nbsp; ✓ Context can be provided or consumed by any HTML element<br>
&nbsp; &nbsp; ✓ Context can be identified by string or unique identifier<br>
&nbsp; &nbsp; ✓ Works with shadow dom and slotted content (handles timing issues)<br>
&nbsp; &nbsp; ✓ Easy to implement unit tests. Most of the time, same as components without context<br>
&nbsp; &nbsp; ✓ Builtin integration with LitElement<br>
&nbsp; &nbsp; ✓ Builtin ContextProvider ([Reactive Controller](https://lit.dev/docs/composition/controllers/)) with primitives for lazy loading<br>
&nbsp; &nbsp; ✓ Builtin context-provider and context-consumer elements<br>
&nbsp; &nbsp; ✓ Conforms with the [Context protocol](https://github.com/webcomponents-cg/community-protocols/blob/main/proposals/context.md)<br>
&nbsp; &nbsp; ✓ Full code coverage<br>

### Live example

- Lit integration: [Shadow DOM](https://codesandbox.io/p/sandbox/wc-context-example-shadow-dom-vite-nkymx3) /

### Usage

Check the documentation https://blikblum.github.io/wc-context/

### License

MIT
Copyright © 2023 Luiz Américo Pereira Câmara aka blikblum
npm package: @launchthatbot/github-openclaw-plugin
Description: GitHub integration plugin for OpenClaw with LaunchThatBot-managed onboarding and fallback auth modes.
Latest version: 0.1.0

# @launchthatbot/github-openclaw-plugin

GitHub operations plugin for OpenClaw instances managed by LaunchThatBot.

## Features

- Managed onboarding via LaunchThatBot GitHub App.
- Disconnect-safe auth modes: `managed_app`, `byo_app`, `pat_fallback`.
- Role gating for `junior` vs `senior` agents.
- Native tools for repo listing, PR workflows, branch creation, checks, and status.

## Install

```bash
openclaw plugin install @launchthatbot/github-openclaw-plugin
```

## Required config (managed mode)

- `authMode`: `managed_app`
- `managedConnectionId`
- `managedSessionToken`

Optional:

- `brokerBaseUrl` (default `https://launchthatbot.com`)
- `agentRole` (`junior` default)

## Fallback config

- BYO app mode: `authMode=byo_app`, `byoInstallationToken` (+ optional app/installation ids)
- PAT fallback mode: `authMode=pat_fallback`, `patToken`

## Commands

- `/github-status` prints active mode, role policy, and remediation hints.
npm package: @launchthatbot/mcp
Description: LaunchThatBot MCP server for Cursor IDE — manage deployments, agents, and infrastructure from your editor
Latest version: 0.3.0

# @launchthatbot/mcp-server

MCP (Model Context Protocol) server for [LaunchThatBot](https://launchthatbot.com) — manage your OpenClaw agent deployments, infrastructure, and credentials directly from Cursor IDE.

## Quick Start

### 1. Get an API Key

Go to **LaunchThatBot Dashboard → Settings → API Keys** and create a new key.

### 2. Add to Cursor

Add this to your `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "launchthatbot": {
      "command": "npx",
      "args": ["-y", "@launchthatbot/mcp-server"],
      "env": {
        "LAUNCHTHATBOT_API_KEY": "ltb_sk_..."
      }
    }
  }
}
```

### 3. Use It

Once configured, you can ask Cursor things like:

- "List my LaunchThatBot servers"
- "Show me the status of my agents"
- "Create a new deployment on Hetzner"
- "What's my dashboard overview?"

## Available Tools

### Servers
- `list_servers` — List all VPS servers with status and region
- `get_server` — Get details for a specific server
- `set_server_attachment` — Attach or detach a server

### Deployments
- `list_deployments` — List deployments for a server
- `get_deployment` — Get deployment details
- `create_deployment` — Provision a new VPS with OpenClaw
- `redeploy` — Reinstall OpenClaw on a server
- `get_job_status` — Check provisioning job progress

### Agents
- `list_agents` — List all agent configurations
- `get_agent` — Get agent details
- `create_agent` — Create a new agent config
- `update_agent` — Update an agent config
- `delete_agent` — Delete an agent config
- `discover_agents` — Find unregistered agents on a server
- `sync_agent` — Push agent config to its server

### Health & Events
- `get_agent_health` — Check OpenClaw instance health
- `get_agent_events` — Get recent instance events

### Dashboard
- `get_overview` — Server count, agent count, health breakdown
- `list_convex_connections` — List Convex cloud connections
- `list_discord_connections` — List Discord bot connections

### Audit
- `list_audit_events` — Get server audit trail

### Credentials
- `list_credentials` — List VPS provider credentials (masked)
- `add_credential` — Add a new provider API token

### Import
- `import_handshake` — Validate one-time import token and fetch RSA public key
- `import_push` — Push exported config and encrypted secrets payload

## Environment Variables

| Variable | Required | Description |
|---|---|---|
| `LAUNCHTHATBOT_API_KEY` | Yes | Your API key (starts with `ltb_sk_`) |
| `LAUNCHTHATBOT_API_URL` | No | Override the API endpoint (for development) |

## Links

- [LaunchThatBot](https://launchthatbot.com)
- [Dashboard](https://launchthatbot.com/admin)
- [Discord](https://discord.gg/launchthatbot)
npm package: @launchtray/hatch-cdk
Description: This project contains AWS CDK stacks and constructs for deploying Hatch-based web services.
Latest version: 0.23.0

# hatch-cdk
This project contains AWS CDK stacks and constructs for deploying Hatch-based web services.

## HatchService
This CDK Stack can be used to deploy a service built on hatch-server (including projects using the microservice and 
webapp templates). See HatchService props documentation for more details.
npm package: @launchtray/hatch-mock-server
Description: This project is a TypeScript library which provides a mock server for testing.
Latest version: 0.23.0

# hatch-mock-server
This project is a TypeScript library which provides a mock server for testing.

## Usage
The mock server can be started via the `mock-server` command, e.g. within a script defined in package.json.
To set the port that is used, set the PORT environment variable, e.g.:
```
    "start:service-mock": "PORT=8080 mock-server",
```
Interacting with the mock server (e.g. within a test) is done via the `MockServerClient` class:
```typescript
  const mockClient = new MockServerClient({
    host: 'localhost',
    port: 8080,
  });

  ...

  // Refer to SimpleMockResponseOptions for the full list of options
  await mockClient.mockSimpleResponse({
    path: '/api/my-api',
    method: 'GET',
    statusCode: 200,
    queryParams: {'id': '123'},
    responseBody: 'Hello, world!',
  });
```
npm package: @launchtray/hatch-rpc
Description: This project is a TypeScript library that contains type definitions and helper classes  for making remote procedure calls (RPC).
Latest version: 0.23.0

# hatch-rpc
This project is a TypeScript library that contains type definitions and helper classes 
for making remote procedure calls (RPC).

`rpc.ts` contains type definitions for generic RPC interfaces.

`json-rpc.ts` contains a basic implementation of this interface using a json-rpc implementation
that delegates to a generic transport interface for sending and receiving data.
npm package: @launchtray/hatch-rpc-node
Description: This project is a TypeScript library that provides remote procedure call (RPC) utilities for node-based projects. It includes RPC transport implementations (which can be used by classes in `hatch-rpc`) for worker threads and child processes, as well as hi
Latest version: 0.23.0

# hatch-rpc-node
This project is a TypeScript library that provides remote procedure call (RPC) utilities
for node-based projects. It includes RPC transport implementations (which can be used by
classes in `hatch-rpc`) for worker threads and child processes, as well as higher-level
utilities for sending a ReadableStream across an RPC interface.
npm package: @launchtray/hatch-scim2-api
Description: This project is a TypeScript API project that defines or generates an  [OpenAPI Specification](https://swagger.io/specification/).
Latest version: 0.21.0-alpha.55

# hatch-scim2-api
This project is a TypeScript API project that defines or generates an 
[OpenAPI Specification](https://swagger.io/specification/).

API projects such as this one are typically used as inputs to an auto-generated client and/or 
server SDK project, which are in turn often used by webapp projects to define and interact 
with HTTP-based APIs in a type-safe, consistent way.

Defining an OpenAPI specification using JSON or YAML directly can be cumbersome and 
error-prone. This project is meant to encapsulate the definition of an API, using tools
to cut down on cumbersome boilerplate and assist with merging together multiple type
and API definitions.

## Specification formats
There are multiple formats that this project can use for defining an OpenAPI specification.

### Spot
Optionally (and by default), this project can use a
[Spot file](https://github.com/airtasker/spot/wiki/Spot-Syntax) to define an OpenAPI
specification. Spot uses a
[TypeScript-based DSL](https://github.com/airtasker/spot/wiki/Spot-Syntax) to define
APIs with minimal boilerplate. Spot APIs can be generated by adding `--spot [input-spot-file]`
to the build scripts in package.json.

### YAML (or JSON)
This project can use raw YAML or JSON OpenAPI specification files as inputs. Note that
since JSON or YAML APIs can be generated by adding `--spec [input-spec-file]`to the build scripts in package.json.

### Combining formats
Multiple specification formats can be used in this project. The generator will merge outputs
together as necessary. This is governed by the ordering of `hatch-api` arguments in the `build`
and `build:watch` scripts in package.json. In the case of merge conflicts, the first argument
precedence. For example, this command will allow definitions in api-overrides.yaml to override
definitions in the api.ts Spot file:

```hatch-api --spec src/api-overrides.yaml --spot src/api.ts```

The above is the default used by this project: a Spot specification that can be overridden by
a raw YAML OpenAPI specification.
npm package: @launchtray/hatch-webpack-config
Description: This project is a library containing functions for easily configuring Webpack 5 for a TypeScript-based web  application. The webpack configuration used by this library is based on the one used by the  [Razzle](https://github.com/jaredpalmer/razzle) projec
Latest version: 0.23.0

# hatch-webpack-config
This project is a library containing functions for easily configuring Webpack 5 for a TypeScript-based web 
application. The webpack configuration used by this library is based on the one used by the 
[Razzle](https://github.com/jaredpalmer/razzle) project, which as of this writing was no longer maintained. 
Up until creation of this library, Hatch relied heavily on the TypeScript features of Razzle directly. This library
is a paring down of Razzle (with some enhancements) to include only what is needed by Hatch. 

This library works best with the [Heft Webpack Plugin](https://heft.rushstack.io/pages/plugins/webpack/). Here is an
example Heft config using this plugin:
```json
{
  "$schema": "https://developer.microsoft.com/json-schemas/heft/v0/heft.schema.json",
  "aliasesByName": {
    "start": {
      "actionName": "build-watch",
      "defaultParameters": ["--clean", "--webpack5:serve"]
    }
  },
  "phasesByName": {
    "build": {
      "phaseDescription": "This phase compiles the project source code.",
      "cleanFiles": [{ "sourcePath": "dist" }, { "sourcePath": "build" }],
      "tasksByName": {
        "webpack": {
          "taskPlugin": {
            "pluginPackage": "@rushstack/heft-webpack5-plugin"
          }
        }
      }
    }
  }
}
```
And here is an example webpack.config.js file (which is the default filename used by the above plugin) which makes 
use of this library:
```js
'use strict';
const {createWebappConfig} = require("@launchtray/hatch-webpack-config");
module.exports = createWebappConfig({appDirectory: __dirname});
```

With the above setup, simple "build" and "start" scripts (to build production bundles, and to run a dev server,
respectively) can be added to a project's package.json using the following Heft commands:
```json
"start": "heft start",
"build": "heft build --clean",
```
npm package: @launchtray/react-pdf-renderer
Description: <p align="center">   <img src="https://user-images.githubusercontent.com/5600341/27505816-c8bc37aa-587f-11e7-9a86-08a2d081a8b9.png" height="280px">   <p align="center">React renderer for creating PDF files on the browser and server<p>   <p align="center">
Latest version: 1.6.12
npm package: @launchtree/sdk-core
Description: ⚒️ An SDK for building applications on top of LaunchTree
Author: sethphiny
Latest version: 0.1.3

# Launchtree SDK Core

[![npm version](https://img.shields.io/npm/v/@launchtree/sdk-core/latest.svg)](https://www.npmjs.com/package/@launchtree/sdk-core/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@launchtree/sdk-core/latest.svg)](https://bundlephobia.com/result?p=@launchtree/sdk-core@latest)

## Multichain Token Launchpad

This code supports multichain. Built for launchtree
This code is shared across Launchtree TypeScript SDKs.
npm package: @launchware/eslint-config-react
Description: ESLint configuration for LaunchWare react projects
Author: Dan Pickett
Latest version: 0.2.0

# LaunchWare's eslint-config-react

This is the default eslint configuration for LaunchWare's React projects.

## Installation

```bash
yarn add -D @launchware/eslint-config-react
```

## Usage

You need to add the following to your `eslint.config.js` (or equivalent) file:

```javascript
const launchEslint = require("@launchware/eslint-config-node")

module.exports = [
  // ... existing ESLint configs
  ...launchEslint.default.configs.recommended,
  {
    settings: {
      "files": ["**/*.{ts}"],
      "import/resolver": { typescript: { project: "./tsconfig.test.json" } },
    },
  },
]
```