pacwich
lightweight new monorepo tooling on top of Bun, NPM, or pnpm
Last verified:
What is pacwich?
Pacwich is monorepo tooling that works on top of Bun, npm, and pnpm workspaces. It provides a CLI and TypeScript API for orchestrating package.json scripts across workspaces, enabling developers to manage complex monorepo projects without requiring a specific package manager. The tool decouples monorepo tooling from your package manager, giving you flexibility in your development workflow.
Key features include zero configuration required to get started, script orchestration for plain package.json scripts, a debuggable and configurable affected graph, workspace code sharing rules enforcement, and optional config files written in JSON or TypeScript/JavaScript. Pacwich also includes AI integrations with Skills, AGENTS.md files, an MCP Server, and /llms.txt support for better AI assistant compatibility.
Pacwich is designed for JavaScript and TypeScript developers working on monorepo projects. It's particularly useful for teams using Bun, npm, or pnpm workspaces who need better script orchestration and workspace management. The tool is the continuation of the deprecated bun-workspaces package, offering minimal to no changes for existing users with a mostly backwards compatible CLI and API.
pacwich pricing
Pricing model: Freemium
Core features remain free with no artificial paywalls for local features. The package is free to use with CLI global install via bun add -g pacwich or local install via bun add -d pacwich. No paid tiers or pricing plans are mentioned on the website.
pacwich pros
- Zero configuration required to get started
- Works with Bun, npm, and pnpm workspaces
- Includes both CLI and TypeScript API
- Orchestrates plain package.json scripts
- Decouples monorepo tooling from package manager
- Debuggable and configurable affected graph
- Enforces rules for workspace code sharing
- Config files in JSON or TypeScript/JavaScript
- AI integrations with Skills and AGENTS.md
- Includes MCP Server support
- /llms.txt support for AI assistants
- Backwards compatible with deprecated bun-workspaces
- Minimal changes needed for bun-workspaces migration
- Simple, straightforward package structure
- Anti-lock-in philosophy prevents user retention complexity
- Parity between CLI and API functionality
- Thorough documentation with Intellisense support
- Core features remain free with no paywalls
- List workspaces with JSON output options
- Run scripts across multiple workspaces in parallel or series
pacwich cons
- Only supports JavaScript/TypeScript projects
- Requires Bun for installation commands
- No built-in visual dashboard
- Local cache feature still on roadmap
- Advanced script orchestration not yet available
- Limited to workspace script composition
- No cloud-based features mentioned
- Config is optional which may cause inconsistency
Frequently asked questions about pacwich
What is Pacwich?
Pacwich is monorepo tooling that works on top of Bun, npm, and pnpm workspaces. It provides a CLI and TypeScript API for orchestrating package.json scripts across workspaces, enabling developers to manage complex monorepo projects.
How do I install Pacwich?
You can install globally with bun add -g pacwich, or locally to devDependencies with bun add -d pacwich. The pacwich command works in package.json scripts even without global install, and you can call it locally using bunx pacwich.
Is Pacwich compatible with bun-workspaces?
Yes, Pacwich is the continuation of the deprecated bun-workspaces package. bun-workspaces users can expect minimal to no changes on average, with a mostly backwards compatible CLI and API. A migration guide is available.
What package managers does Pacwich support?
Pacwich works on top of Bun, npm, and pnpm workspaces, allowing you to decouple monorepo tooling from your specific package manager.
Does Pacwich require configuration files?
No, Pacwich requires zero configuration to get started. However, you can write optional config files in JSON or TypeScript/JavaScript if you need custom settings.
What AI integrations does Pacwich include?
Pacwich includes AI integrations with Skills, AGENTS.md files, an MCP Server, and /llms.txt support for better compatibility with AI assistants.
Can I run scripts across multiple workspaces?
Yes, Pacwich orchestrates package.json scripts across workspaces. Scripts run in parallel by default, but you can also run them in series using --dep-order. You can target specific workspaces, multiple workspaces, or use matching specifiers like globs and aliases.
What is the affected graph in Pacwich?
Pacwich includes a debuggable and configurable affected graph, which helps determine which workspaces and scripts need to run based on changes in your monorepo.
Are there paid features in Pacwich?
No, core features remain free with no artificial paywalls for the local features of the package. The guiding principles state that core features should remain free for the life of the project.
What features are on the Pacwich roadmap?
The roadmap includes a local cache for caching workspace script output and results, plus more advanced script orchestration for flexibly composing various workspace scripts into arbitrarily complex workflows, rather than only running one script across workspaces in parallel or series.