binary-collections 2.0.13 → 2.0.15

package/docs-src/get-latest-workflow-status.md

@@ -0,0 +1,100 @@
+# Get Latest Workflow Status
+
+Fetches and displays the latest GitHub Actions workflow run from the repository — showing the run name, status, conclusion, branch, and a full job-by-job breakdown with each step's result. Useful for quickly checking CI status from the terminal without opening a browser.
+
+## Usage
+
+```bash
+get-latest-workflow-status [options]
+```
+
+### Aliases
+
+This command is available under several names (all invoke the same CLI):
+
+- `get-latest-workflow-status` (default)
+- `get-latest-workflow`
+- `latest-workflow`
+- `wf-status`
+
+### Options
+
+| Flag | Type | Description |
+| :--- | :--- | :--- |
+| `--owner` | `string` | GitHub repository owner (default: auto-detect from git remote or `GH_OWNER` env) |
+| `--repo` | `string` | GitHub repository name (default: auto-detect from git remote or `GH_REPO` env) |
+| `--workflow` | `string` | Filter by workflow filename (e.g. `"test.yml"`) or numeric workflow ID |
+| `--token` | `string` | GitHub access token (overrides `ACCESS_TOKEN` / `GITHUB_TOKEN` / `GH_TOKEN` env vars) |
+| `-h`, `--help` | `boolean` | Show help message |
+
+### Environment Variables
+
+| Variable | Description |
+| :------- | :---------- |
+| `ACCESS_TOKEN` / `GITHUB_TOKEN` / `GH_TOKEN` | GitHub personal access token with `actions:read` scope (required) |
+| `GH_OWNER` | Override repository owner (optional) |
+| `GH_REPO` | Override repository name (optional) |
+
+### Examples
+
+Show the latest workflow run for the current repository:
+
+```bash
+get-latest-workflow-status
+```
+
+Show for a specific repository:
+
+```bash
+get-latest-workflow-status --owner dimaslanjaka --repo bin
+```
+
+Filter by a specific workflow YAML file:
+
+```bash
+get-latest-workflow-status --workflow test.yml
+get-latest-workflow-status --owner dimaslanjaka --repo bin --workflow deploy.yml
+```
+
+Show help:
+
+```bash
+get-latest-workflow-status --help
+```
+
+### Output Example
+
+```
+==============================
+🚀 Latest Workflow Run
+==============================
+Name      : Node.js Package Test
+Status    : in_progress
+Conclusion: null
+Branch    : master
+Run ID    : 26797771514
+URL       : https://github.com/dimaslanjaka/bin/actions/runs/26797771514
+
+==============================
+🧩 Jobs & Steps
+==============================
+
+🧱 Job: 🔨 Build, Pack & Test
+   Status: in_progress | Conclusion: null
+   ✅ Set up job -> success (completed)
+   ✅ ⬇️ Checkout workflow repository -> success (completed)
+   ✅ ⬇️ Setup CI Environment -> success (completed)
+   ⚪ 🧪 Run tests in test/example.test.cjs -> null (in_progress)
+```
+
+### How it works
+
+1. **Authenticate** — Uses `ACCESS_TOKEN` / `GITHUB_TOKEN` / `GH_TOKEN` to call the GitHub API.
+2. **Detect repository** — Owner and repo are auto-detected from the `git remote.origin.url`, or can be overridden with `--owner`/`--repo` flags or `GH_OWNER`/`GH_REPO` environment variables.
+3. **Fetch latest run** — Calls `GET /repos/{owner}/{repo}/actions/runs?per_page=1` to get the most recent workflow run. If `--workflow` is specified, appends `&workflow_id=<name>` to filter by workflow filename or ID.
+4. **Fetch jobs** — Calls `GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs` to retrieve all jobs and their steps.
+5. **Print report** — Renders a formatted terminal report with color-coded icons (✅ success, ❌ failure, ⏭️ skipped, ⚪ pending/in progress).
+
+## Source
+
+See [`src/github-workflows/get-latest-workflow-status-cli.mjs`](../src/github-workflows/get-latest-workflow-status-cli.mjs).

package/docs-src/git-diff.md

@@ -30,4 +30,4 @@ git-diff --ai              # Generate commit message with ChatGPT
 
 ### Source
 
-See [`src/git-diff.js`](../src/git-diff.js) & [`src/git-diff-cli.js`](../src/git-diff-cli.js)
+See [`src/git/git-diff-cli.js`](../src/git/git-diff-cli.js).

package/docs-src/git-fix.md

@@ -31,4 +31,4 @@ Options can be combined: `git-fix --lf-only --permissions`
 
 ### Source
 
-See [`src/git-fix.cjs`](../src/git-fix.cjs) & submodules in [`src/git/`](../src/git/)
+See [`src/git/git-fix.cjs`](../src/git/git-fix.cjs).

package/docs-src/git-purge.md

@@ -14,4 +14,4 @@ Aggressively prunes the git reflog in all `.git` directories, helping reduce rep
 
 ### Source
 
-See [`src/git-purge.cjs`](../src/git-purge.cjs)
+See [`src/git/git-purge.cjs`](../src/git/git-purge.cjs)

package/docs-src/install-opencode-plugins.md

@@ -0,0 +1,86 @@
+# Install OpenCode Plugins
+
+CLI tool that automates the installation of recommended OpenCode plugins. Runs a series of `git clone` and `opencode plugin` commands sequentially to set up a collection of plugins in one invocation.
+
+## Usage
+
+```bash
+install-opencode-plugins [options]
+```
+
+### Aliases
+
+This command is available under several aliases (all invoke the same CLI):
+
+- `install-opencode-plugins` (default)
+- `install-opc-plugins`
+- `opc-plugins`
+
+### What it installs
+
+The tool runs the following commands in order:
+
+1. **opencode-request-logger** — Clones the request logger plugin into `.opencode/plugins/opencode-request-logger`:
+   ```bash
+   git clone https://github.com/Opencode-DCP/opencode-request-logger.git .opencode/plugins/opencode-request-logger
+   ```
+   *Note: Skipped if the folder already exists.*
+
+2. **Register local request-logger plugin** — Installs the cloned plugin from the local path:
+   ```bash
+   opencode plugin .opencode/plugins/opencode-request-logger
+   ```
+
+3. **opencode-agent-memory** — Installs the file memory plugin from a remote tarball:
+   ```bash
+   opencode plugin opencode-agent-memory@https://github.com/dimaslanjaka/opencode-file-memory/raw/refs/heads/main/release/opencode-agent-memory.tgz
+   ```
+
+4. **@tarquinen/opencode-smart-title** — Installs smart title generation:
+   ```bash
+   opencode plugin @tarquinen/opencode-smart-title@latest
+   ```
+
+5. **oh-my-opencode-slim** — Installs the slim OpenCode enhancement pack:
+   ```bash
+   opencode plugin oh-my-opencode-slim@latest
+   ```
+
+6. **@tarquinen/opencode-dcp** — Installs DCP (Deep Context Protocol) support:
+   ```bash
+   opencode plugin @tarquinen/opencode-dcp@latest
+   ```
+
+7. **envsitter-guard** — Installs the environment variable security guard:
+   ```bash
+   opencode plugin envsitter-guard@latest
+   ```
+
+### Options
+
+| Flag | Description |
+| :--- | :--- |
+| `-h`, `--help` | Show help message |
+
+### Example
+
+```bash
+install-opencode-plugins
+```
+
+### How it works
+
+1. The tool iterates through a predefined array of commands (git clone + opencode plugin installs).
+2. Each command runs **sequentially** using `cross-spawn` with `stdio: 'inherit'` (output visible in real time) and `shell: true` (resolves binaries via the user's shell PATH).
+3. If any command exits with a non-zero code, execution stops immediately and an error message is printed.
+4. On success, it prints "All commands executed successfully!".
+
+### Prerequisites
+
+- `git` must be available on `PATH`.
+- `opencode` CLI must be installed and available on `PATH`.
+- The plugins are installed into the current working directory's `.opencode/plugins/` folder.
+
+## Source
+
+See [`src/opencode/install-opencode-plugins-cli.ts`](../src/opencode/install-opencode-plugins-cli.ts).

package/docs-src/kill-night-crows.md

@@ -23,4 +23,4 @@ kill-night-crows
 
 ### Source
 
-See [`src/kill-night-crows.mjs`](../src/kill-night-crows.mjs) & [`bin/kill-night-crows.ps1`](../bin/kill-night-crows.ps1)
+See [`src/kill-night-crows.mjs`](../src/kill-night-crows.mjs) & [`bin/kill-night-crows.ps1`](../bin/kill-night-crows.ps1).

package/docs-src/node-cache-cleaner.md

@@ -24,7 +24,7 @@ node-cache-cleaner [options]
 
 ### Source
 
-See [`src/node-cache-cleaner-cli.ts`](../src/node-cache-cleaner-cli.ts) and [`src/node-cache-cleaner/`](../src/node-cache-cleaner/)
+See [`src/node-cache-cleaner-cli.ts`](../src/node-cache-cleaner-cli.ts).
 
 ---
 
@@ -178,5 +178,5 @@ yarn run rm-node-modules
 
 ### Source
 
-See [`src/rm-node-module-cli.cjs`](../src/rm-node-module-cli.cjs) & [`src/rm-node-modules.cjs`](../src/rm-node-modules.cjs)
+See [`src/rm-node-module-cli.cjs`](../src/rm-node-module-cli.cjs).
 

package/docs-src/node-package-packer.md

@@ -45,4 +45,4 @@ This command is available under the following aliases:
 
 ### Source
 
-See [`src/node-package-packer-cli.mjs`](../src/node-package-packer-cli.mjs) (CLI entry point) and [`src/node-package-packer/build-tarball.mjs`](../src/node-package-packer/build-tarball.mjs) (pack workflow).
+See [`src/node-package-packer-cli.mjs`](../src/node-package-packer-cli.mjs).

package/docs-src/opencode-cli.md

@@ -0,0 +1,155 @@
+# OpenCode CLI
+
+CLI tool for inspecting and managing an OpenCode database. Connects to the local OpenCode SQLite database (`~/.local/share/opencode/opencode.db`) to list sessions and projects, and to delete sessions or projects. Also supports API key rotation from a local keys file.
+
+## Usage
+
+```bash
+opc <command> [subcommand] [options]
+```
+
+### Aliases
+
+This command is available under several aliases (all invoke the same CLI):
+
+- `opc` (default)
+- `opencode-cli`
+
+### Commands
+
+#### `list session`
+
+Lists all sessions in a table format showing slug, title, and version.
+
+```bash
+opc list session
+```
+
+#### `list project`
+
+Lists all projects in a table format showing truncated ID, name, and worktree path.
+
+```bash
+opc list project
+```
+
+#### `delete session <id>`
+
+Deletes a single session and all its descendant sessions by ID.
+
+```bash
+opc delete session <session-id>
+```
+
+#### `delete sessions`
+
+Deletes **all** sessions from the database (irreversible).
+
+```bash
+opc delete sessions
+```
+
+#### `delete project <id>`
+
+Deletes a project's sessions and project record from the OpenCode database (not the real project folder on disk).
+
+The `<id>` is the project UUID shown in the first column of `opc list project`. Run that command first to find the project ID you want to delete.
+
+```bash
+opc delete project <project-id>
+```
+
+#### `auth rotate`
+
+Rotates the active OpenCode API key by picking the first working key from a local keys file. Iterates through available keys (excluding the current one) and tests each against the OpenCode API, selecting the first that returns a valid response.
+
+```bash
+opc auth rotate
+```
+
+Use `--proxy` to route API requests through a proxy server:
+
+```bash
+opc auth rotate --proxy socks5://127.0.0.1:1080
+```
+
+### Options
+
+| Flag | Description |
+| :--- | :--- |
+| `-h`, `--help` | Show help message |
+| `-p`, `--proxy <url>` | Proxy URL for API requests. Supports `http://`, `https://`, `socks4://`, `socks5://` protocols. Format: `protocol://ip:port` or `protocol://user:pass@ip:port` |
+
+### Examples
+
+List all sessions:
+
+```bash
+opc list session
+```
+
+Delete a specific session:
+
+```bash
+opc delete session abc123
+```
+
+Delete a project's sessions and project record from the OpenCode database (ID obtained from `opc list project`):
+
+```bash
+opc delete project 9a3bb589
+```
+
+Rotate to a working API key:
+
+```bash
+opc auth rotate
+# → Rotated OpenCode API key to: my-backup-key
+```
+
+Rotate through a SOCKS5 proxy:
+
+```bash
+opc auth rotate --proxy socks5://127.0.0.1:1080
+```
+
+### How it works
+
+1. **Database check**: On every command except `--help`, the tool first verifies the OpenCode database is accessible via `checkDatabase()`.
+2. **List**: Queries the `session` or `project` table and displays results in formatted tables with dynamic column widths.
+3. **Delete**: Uses recursive SQL (Common Table Expressions) to delete sessions and their descendants, or cascading deletes for project sessions.
+4. **Auth rotate**: Reads `opencode.keys` from the project config (via `getConfig()`), filters out the currently active key, tests each remaining key via `checkOpenCodeApi()`, and sets the first one that responds successfully. If `--proxy` is provided, it's passed through to `checkOpenCodeApi()` which creates a `ProxyAgent` for the HTTP/SOCKS proxy.
+
+### Requirements
+
+For `auth rotate`, add an `opencode.keys` array to your [project config](../readme.md#configuration). Create a `binary-collections.config.{js,cjs,mjs}` file:
+
+```js
+// binary-collections.config.js (ESM) or .cjs (CJS)
+export default {
+  opencode: {
+    keys: [
+      { name: 'primary', key: 'sk-xxxxxx' },
+      { name: 'backup', key: 'sk-yyyyyy' }
+    ]
+  }
+};
+```
+
+Or in `package.json`:
+
+```json
+{
+  "binary-collections": {
+    "opencode": {
+      "keys": [
+        { "name": "primary", "key": "sk-xxxxxx" }
+      ]
+    }
+  }
+}
+```
+
+## Source
+
+See [`src/opencode-cli.ts`](../src/opencode-cli.ts).

package/docs-src/package-resolutions-updater.md

@@ -19,4 +19,4 @@ Scans `package.json` resolutions for GitHub tarball URLs (raw.githubusercontent.
 
 ### Source
 
-See [`src/package-resolutions-updater.mjs`](../src/package-resolutions-updater.mjs) & [`src/package-resolutions-updater-cli.mjs`](../src/package-resolutions-updater-cli.mjs)
+See [`src/package-resolutions-updater-cli.mjs`](../src/package-resolutions-updater-cli.mjs).

package/docs-src/rmpath.md

@@ -35,4 +35,4 @@ rmpath C:\temp\huge-folder
 
 ## Source
 
-See [`src/rmpath-cli.mjs`](../src/rmpath-cli.mjs) (CLI entry point) and [`src/rmpath.mjs`](../src/rmpath.mjs) (core logic).
+See [`src/rmpath-cli.mjs`](../src/rmpath-cli.mjs).

package/docs-src/run-by-checksum.md

@@ -84,4 +84,4 @@ The function returns:
 
 ## Source
 
-See [`src/run-by-checksum-cli.js`](../src/run-by-checksum-cli.js) (CLI) and [`src/run-by-checksum/`](../src/run-by-checksum/) (core logic).
+See [`src/run-by-checksum-cli.js`](../src/run-by-checksum-cli.js).

package/docs-src/submodule-remove.md

@@ -19,4 +19,4 @@ Performs a complete removal of a git submodule:
 
 ### Source
 
-See [`src/submodule-remove.cjs`](../src/submodule-remove.cjs) & [`src/submodule-remove-cli.js`](../src/submodule-remove-cli.js)
+See [`src/submodule-remove-cli.js`](../src/submodule-remove-cli.js).

package/docs-src/upload-backend.md

@@ -0,0 +1,29 @@
+# Upload Backend
+
+Uploads PHP files from the `backend/` directory to a remote server via SFTP. Reads the connection configuration from `.vscode/sftp.json` and deploys all `.php` files into `{remotePath}/php_backend` on the target server.
+
+## Usage
+
+```bash
+node scripts/upload-backend.mjs
+```
+
+### Prerequisites
+
+- An SFTP server configured in `.vscode/sftp.json`
+- PHP files present in the `backend/` directory
+
+### Behavior
+
+1. Reads `.vscode/sftp.json` for host, port, username, and password
+2. Scans `backend/` for all `*.php` files
+3. Connects to the remote server via SFTP
+4. Creates the `php_backend` subdirectory under the configured `remotePath`
+5. Uploads each PHP file into that directory
+6. Prints a confirmation per uploaded file
+
+If no PHP files are found, the script exits with a notice.
+
+## Source
+
+See [`scripts/upload-backend.mjs`](../scripts/upload-backend.mjs).

package/docs-src/vscode-cli.md

@@ -0,0 +1,84 @@
+# VSCode CLI
+
+CLI tool for inspecting VS Code workspace storage directories. Scans the `workspaceStorage` folder under the VS Code user data directory, reads each subdirectory's `workspace.json`, and lists workspace projects with their storage identifiers. Optionally filters to workspaces that have a Copilot memory tool directory.
+
+## Usage
+
+```bash
+vscode-cli <command> [subcommand] [options]
+```
+
+### Aliases
+
+This command is available under the following alias:
+
+- `vscode-cli` (default)
+
+### Commands
+
+#### `list project`
+
+Lists all workspace projects in a table format showing truncated storage ID, folder path, and whether Copilot memory tool data exists.
+
+```bash
+vscode-cli list project
+```
+
+#### `list project --copilot-memory`
+
+Lists only projects that have a Copilot memory tool directory (i.e., those where `GitHub.copilot-chat/memory-tool/memories` exists under the workspace storage directory).
+
+```bash
+vscode-cli list project --copilot-memory
+```
+
+Short aliases: `--copilotMemory`, `--cm`
+
+### Options
+
+| Flag | Description |
+| :--- | :--- |
+| `-h`, `--help` | Show help message |
+| `--copilot-memory` | Filter to projects with Copilot memory tool |
+
+### Examples
+
+List all workspace projects:
+
+```bash
+vscode-cli list project
+```
+
+List only projects with Copilot memory tool data:
+
+```bash
+vscode-cli list project --copilot-memory
+```
+
+### How it works
+
+1. **Scan**: Lists all subdirectories under the VS Code `workspaceStorage` folder (e.g., `%APPDATA%/Code/User/workspaceStorage` on Windows).
+2. **Parse**: Reads `workspace.json` from each subdirectory to extract the workspace `folder` URI.
+3. **Decode**: Converts `file:///` URIs to absolute filesystem paths (e.g., `file:///d%3A/Repositories/project` → `d:/Repositories/project`).
+4. **Filter** (optional): When `--copilot-memory` is specified, only includes entries where `GitHub.copilot-chat/memory-tool/memories` exists on disk.
+5. **Display**: Renders results in a formatted table with dynamic column widths.
+
+### Programmatic API
+
+The workspace scanning logic can also be imported directly:
+
+```ts
+import { listWorkspaceProjects } from './src/vscode/storage.js';
+
+const projects = await listWorkspaceProjects();
+
+// projects is WorkspaceEntry[] with:
+//   storageId: string  — hash-based subdirectory name
+//   folder: string     — absolute filesystem path (decoded URI)
+//   storagePath: string — full path to the workspace storage subdirectory
+//   copilotMemoryDir?: string — path to Copilot memory tool directory (if it exists)
+```
+
+## Source
+
+See [`src/vscode-cli.ts`](../src/vscode-cli.ts).

package/docs-src/workflow-badge.md

@@ -0,0 +1,120 @@
+# Workflow Badge
+
+Generates a detailed SVG badge showing the status of the latest GitHub Actions workflow run. Displays workflow metadata, per-job step breakdown, and aggregated status counts — all in a polished card-style SVG suitable for embedding in READMEs, dashboards, or CI summary pages.
+
+## Usage
+
+```bash
+workflow-badge [options]
+```
+
+### Aliases
+
+This command is available under several aliases (all invoke the same CLI):
+
+- `workflow-badge` (default)
+- `wf-badge`
+- `gh-status-badge`
+- `actions-badge`
+
+### Options
+
+| Flag | Type | Description |
+| :--- | :--- | :--- |
+| `-o`, `--output` | `string` | Write SVG to file instead of stdout |
+| `--owner` | `string` | GitHub repository owner (default: auto-detect from git remote) |
+| `--repo` | `string` | GitHub repository name (default: auto-detect from git remote) |
+| `--workflow` | `string` | Filter by workflow filename (e.g. `"test.yml"`) or numeric workflow ID |
+| `--token` | `string` | GitHub access token (overrides `ACCESS_TOKEN` / `GITHUB_TOKEN` / `GH_TOKEN` env vars) |
+| `--width` | `number` | SVG width in pixels (default: `520`) |
+| `--max-steps` | `number` | Max steps to show per job (default: all). Use to keep badge compact |
+| `-h`, `--help` | `boolean` | Show help message |
+
+### Environment Variables
+
+| Variable | Description |
+| :------- | :---------- |
+| `ACCESS_TOKEN` / `GITHUB_TOKEN` / `GH_TOKEN` | GitHub personal access token (required for API calls) |
+| `GH_OWNER` | Override repository owner (optional) |
+| `GH_REPO` | Override repository name (optional) |
+
+### Examples
+
+Preview badge in terminal (SVG printed to stdout):
+
+```bash
+workflow-badge
+```
+
+Save badge to file:
+
+```bash
+workflow-badge --output badge.svg
+```
+
+Save for a specific repository with custom width:
+
+```bash
+workflow-badge --owner dimaslanjaka --repo bin --output docs/workflow-status.svg --width 600
+```
+
+Keep the badge compact by limiting visible steps per job:
+
+```bash
+workflow-badge --max-steps 5 --output compact-badge.svg
+```
+
+Generate a badge for a specific workflow YAML file:
+
+```bash
+workflow-badge --workflow test.yml
+workflow-badge --owner dimaslanjaka --repo bin --workflow deploy.yml --output deploy-badge.svg
+```
+
+### Output
+
+The generated SVG is a card-style badge with:
+
+- **Accent bar** — color-coded based on overall status (green = passing, red = failing, amber = in progress, grey = cancelled/pending)
+- **Title section** — "Workflow Status" label with status pill
+- **Metadata rows** — workflow name, status, branch, run ID
+- **Jobs breakdown** — each job with its status, plus individual step rows with icons (✓ = passed, ✗ = failed, ◌ = pending, – = skipped)
+- **Footer summary** — aggregated step counts
+
+### PHP Backend
+
+A PHP script is available at [`backend/workflow-badge.php`](../backend/workflow-badge.php) that serves the badge as a live image via HTTP. It spawns the Node CLI, captures the SVG output, and serves it with the correct `image/svg+xml` content type. The PHP backend requires the full project (with the CLI script under `src/` or `lib/`) to be deployed on the server — it does not fall back to a remote tarball.
+
+**Query parameters:**
+
+| Parameter | Required | Description |
+| :-------- | :------- | :---------- |
+| `owner` | yes | GitHub repository owner |
+| `repo` | yes | GitHub repository name |
+| `workflow` | no | Filter by workflow filename (e.g. `test.yml`) or workflow ID |
+| `width` | no | SVG width in pixels (200–2000, default: 520) |
+| `max-steps` | no | Max steps to show per job (1–200, default: all) |
+| `token` | no | GitHub access token (overrides server env) |
+
+**Requirements:**
+- PHP 7.4+ with `proc_open` enabled
+- The project's Node CLI script deployed on the server (`src/github-workflows/workflow-badge-cli.mjs` or `lib/github-workflows/workflow-badge-cli.cjs`)
+- `ACCESS_TOKEN` (or `GITHUB_TOKEN` / `GH_TOKEN`) environment variable set on the server, or pass `&token=...` per request
+
+**Usage as `<img>` tag:**
+
+```html
+<img src="https://your-domain.com/backend/workflow-badge.php?owner=dimaslanjaka&repo=bin" />
+<!-- or using our server -->
+<img src="http://sh.webmanajemen.com/php_backend/workflow-badge.php?owner=dimaslanjaka&repo=bin" />
+```
+
+![badge sample](http://sh.webmanajemen.com/php_backend/workflow-badge.php?owner=dimaslanjaka&repo=bin)
+
+You can optionally add `&width=600`, `&max-steps=5`, `&workflow=test.yml`, or `&token=ghp_xxx` to customize the badge appearance or override the server's GitHub token for a single request.
+
+The script validates all parameters before passing them to the Node CLI, separates `stdout` (SVG) from `stderr` (diagnostics) via `proc_open`, and returns appropriate HTTP error codes for invalid inputs or CLI failures.
+
+## Source
+
+See [`src/github-workflows/workflow-badge-cli.mjs`](../src/github-workflows/workflow-badge-cli.mjs).

package/lib/binary-collections/config-types.cjs

@@ -0,0 +1,17 @@
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+
+// src/binary-collections/config-types.ts
+var config_types_exports = {};
+module.exports = __toCommonJS(config_types_exports);