bun-workspace

Manage Bun monorepo workspaces and dependencies across multi-package projects.

2|Updated Jan 23, 2026

Search Tags:#dependencies #workspace #monorepo #bun #scripts #cross-package

Ready to run

npx skills add https://github.com/ftc8569/ftcmetrics --skill bun-workspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bun-workspace
Source: https://github.com/ftc8569/ftcmetrics/tree/main/.claude/skills/bun-workspace
Command: npx skills add https://github.com/ftc8569/ftcmetrics --skill bun-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Bun monorepo workspaces and dependencies across a multi-package FTC Metrics project can be error-prone and slow. This Skill provides a centralized approach to managing package scripts, dependency resolution, and cross-package imports to reduce setup time and inconsistencies.

Core Features & Use Cases

Centralized workspace configuration using the root package.json to coordinate all packages.
Seamless cross-package dependency management with workspace:* to ensure consistent versions across packages.
Run package scripts across packages with a single command to accelerate development and testing.
Troubleshoot workspace resolution issues quickly with unified tooling rules and guidance.

Quick Start

From the repository root, run Bun commands to add dependencies, run scripts, and troubleshoot workspace issues.

Frequently Asked Questions about bun-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage cross-package dependencies in a Bun monorepo workspace?▼

Bun monorepo workspace dependencies are managed by configuring the root package.json and using the workspace:* protocol to link cross-package imports. This ensures consistent versions across web, api, db, and shared packages within the project.

Can I run package scripts across multiple workspace packages with a single Bun command?▼

Yes, you can run package scripts across multiple workspace packages with a single Bun command from the repository root. This centralized approach accelerates development and testing across the entire monorepo workspace configuration.

Why does my Bun workspace resolution fail when importing shared packages?▼

Bun workspace resolution fails when cross-package imports are misconfigured in the root package.json. Troubleshooting workspace resolution requires verifying that the workspace:* protocol correctly links the web, api, db, and shared packages.

What is the best way to add a new dependency to multiple packages in a Bun monorepo?▼

The best way to add dependencies in a Bun monorepo is by using root-level Bun commands to coordinate the installation. This centralizes dependency management and ensures versions stay consistent across the workspace.

Do I need a specific root package.json structure for a Bun multi-package workspace?▼

Yes, a Bun multi-package workspace requires a root package.json configured to coordinate all packages. This centralized file defines the workspace boundaries and manages cross-package references for the web, api, db, and shared packages.

How do I troubleshoot inconsistent dependency versions across my Bun workspace packages?▼

Troubleshoot inconsistent dependency versions across Bun workspace packages by applying the workspace:* protocol in your root package.json. This enforces unified tooling rules and ensures consistent versions across all cross-package imports.