open-index/open-npm huggingface dataset:
npm package: @starbase/memstore
Description: Starbase Memory Store
Author: Mike Fuller
Latest version: 0.0.3

# Memstore
Starbase Memory Store

Portable In-memory key value store for Node.js and The Web. Memstore is an API-compatible datastore based on the [Starbase Database](https://github.com/StarbaseAlpha/Database) API and works as a datastore for [Starbase Channels](https://github.com/StarbaseAlpha/Database).

## Adding Starbase Memstore to your Project

### On the Web
```HTML
<script src="/path/to/memstore.min.js"></script>
```

### On the Web via jsdelivr CDN
```HTML
<script src="https://cdn.jsdelivr.net/npm/@starbase/memstore/memstore.min.js"></script>
```

### In NodeJS
```bash
npm install @starbase/memstore 
```


## Using the Memstore

The API methods for Memstore matches the Starbase Database API. Please see the [Starbase Database Manual](https://github.com/StarbaseAlpha/Database) for examples and further documentation.


## More Information

Starbase Memstore stores data in memory and functions as a data store on Node.js and in the browser. When used in a Node.js application, the data will persist until the application stops or is terminated. In the browser, the data persists until the window/tab is refreshed or closed.

Memory storage is suitable for temporarily storing and managing data in memory. One use case is storing data in the browser that is then displayed to the user. Changes can be made to the memory store data and then exported and saved in a more permanent storage engine or discarded. On the server, a memory store could be used as a cache for frequently accessed data.

Memory stores can write (and often access) data faster than permanent storage engines with some important limitations to consider. The amount of physical memory available to the server or browser should be considered when storing and accessing data from a memory store. Large datasets (many MBs in size) can be slow or sluggish depending on the resources available to the application. It is best to store large amounts of data in a permanent storage engine and use memory storage for caching and managing smaller sets of data.
npm package: @starbeach/chase
Description: Reusable log/debug toolkit for coding agents across multiple projects
Latest version: 0.2.5

# chase

`chase` is a reusable log/debug toolkit for coding agents across multiple projects.

## What it standardizes

- Human UI: `zellij` panes (or any terminal panes)
- Raw logs: `.logs/*.log`
- Agent entrypoint: `chase`
- Snapshot for agents: `.debug/latest.md`

## Install into a target project

Using npm registry package:

```bash
npx @starbeach/chase /path/to/target-project
```

or:

```bash
pnpm dlx @starbeach/chase /path/to/target-project
```

To run `chase` without `./`, install globally once:

```bash
npm i -g @starbeach/chase
```

From this repository (local development):

```bash
./scripts/install.sh /path/to/target-project
```

or:

```bash
./bin/chase-install /path/to/target-project
```

If omitted, target defaults to current directory.

`chase install` starts a setup flow and asks whether to install the bundled skill into `.agents/skills/`.

## Generated files in target project

- `.chase/config.json`
- `.logs/`
- `.debug/`

## Configure per project

Edit `.chase/config.json` in each target project:

```json
{
  "commands": {
    "web": "pnpm dev",
    "app": "pnpm --filter app dev",
    "compose": "docker compose up"
  }
}
```

You can also customize targets, log paths, regex, and bundle hints.

## Daily usage

```bash
chase dev-up web
chase dev-up app
chase dev-up compose

chase errors
chase logs web 120
chase summary
chase debug-bundle
```

`chase debug-bundle` writes `.debug/latest.md` for agent-first troubleshooting.

## Agent-first usage

Use structured output for automation:

```bash
chase describe --output json
chase errors --output json
chase logs web 120 --output json
chase summary --output json
chase debug-bundle --output json
```

Safety flag:

```bash
chase dev-up web --dry-run --output json
```

## Codex Skill

This repository includes a reusable skill:

- `skills/chase-log-debug/SKILL.md`

Use this skill when an agent should follow a strict `chase`-first debug flow.

For non-interactive environments, set `CHASE_INSTALL_SKILL=1` (install) or `CHASE_INSTALL_SKILL=0` (skip).

## Versioning and Release

This repository uses Changesets.

```bash
# add release note
npm run changeset

# bump package version from pending changesets
npm run version-packages

# publish to npm
npm run release
```

## Agent operating rule (recommended)

Tell agents to use this order:

1. Read `.debug/latest.md`
2. Run `chase errors`
3. Run `chase logs <target> <lines>` as needed

## Design notes

- Keep entrypoints stable (`chase`) across projects.
- Swap internals later (compose/k8s/cloud logs) without changing agent workflow.
- Keep project-specific behavior in `.chase/config.json` only.
- Keep runtime logic in global `chase`; do not vendor shared scripts into each project.
npm package: @starbeam-dev/dev-mode
Description: Simple scripts to use when developing packages
Latest version: 0.9.1

# dev-mode

[![standard-readme compliant](https://img.shields.io/badge/standard--readme-OK-green.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme)

## <center>⚠️🚧⚠️ Under Construction ⚠️🚧⚠️</center>

**This package is currently in a very early stage of development. It is currently being developed for the `starbeam-dev` family of repositories and should probably not be used (yet) outside of that context.**

---

A development dependency that provides scripts that you can run during during development.

It currently contains a single script:

- `dev-tests`: Runs `vitest` from the `tests` directory relative to the current git root.

## Table of Contents

- [Install](#install)
- [Assumptions](#assumptions)
- [Usage](#usage)
- [API](#api)
- [Maintainers](#maintainers)
- [Contributing](#contributing)
- [License](#license)

## Install

```
$ pnpm i -D dev-mode
```

## Assumptions

At the moment, the `dev-mode` script is extremely opinionated and makes the following assumptions:

- Tests are in the `tests` directory relative to the current git root
- Your project uses vitest. The `vitest` dependency is either in a `package.json` directly inside of `tests` or in the repo root.
- Typechecking is done using `vitest typecheck`.

## Usage

Add the following to your `package.json`:

```json
{
  "scripts": {
    "test:specs": "dev-tests"
  }
}
```

If you also want to use `dev-mode` to typecheck your project, add the following to your `package.json`:

```json
{
  "scripts": {
    "test:specs": "dev-tests",
    "test:types": "dev-tests typecheck"
  }
}
```

## API

## Maintainers

[The Starbeam team](https://github.com/starbeamjs/.github/blob/main/TEAM.md).

## Contributing

See [the contributing file](CONTRIBUTING.md)!

PRs accepted.

Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification.

## License

MIT © 2023 Yehuda Katz
npm package: @starbeam-dev/typedoc-theme
Description: A TypeDoc theme and plugin for projects using Starbeam Dev.
Author: Yehuda Katz
Latest version: 1.0.1

# @starbeam-dev/typedoc-theme

A TypeDoc theme and plugin for projects using Starbeam Dev

## Usage

```shell
npm install --save-dev @starbeam-dev/typedoc-theme
```

```json
{
  "plugin": ["@starbeam-dev/typedoc-theme"],
  "theme": "@starbeam-dev"
}
```

## Features

- 🌸🦋 A prettier version of the default theme
- 🫧🧹 Dynamically removes categories from the navigation that don't have any members _based on the currently selected filters_.
- 🥇 `@primary` overloads: If an overload is marked `@primary`, it will be moved to the top of the overload list, with additional whitespace following it. This allows you to put the primary documentation alongside the most general overload, even though it needs to appear last for type system reasons.
- 📋 Inlining: If a type declaration is marked with `@inline`, all references to that type declaration will be replaced with the body of the declaration.

## Limitations

- 🔍⚠️ Non-exhaustive: This theme was built for packages using `starbeam-dev` and may not fully cover all TypeDoc features (but patches are welcome!).
- 🧷 Somewhat brittle: This theme was built on top of the CSS, DOM structure and HTML of TypeDoc's default theme. These details are not really public API. It is also built on assumptions of TypeDoc as of 0.25 and TypeScript as of 5.2.2. These assumptions may change and would break the theme.

## Maintainers

[The Starbeam team](https://github.com/starbeamjs/.github/blob/main/TEAM.md).

## Contributing

See [the contributing file](CONTRIBUTING.md)!

## License

MIT © 2023 Yehuda Katz