<a href="https://pacwich.dev" <img src="./workspaces/web/documentation-website/src/pages/public/images/png/bwunster-pacwich-subtitled-wide1400x400.png" alt="pacwich logo" width="100%" / </a
<br/
pacwich
<subLatest: 0.6.0</sub
Monorepo tooling that works on top of Bun, npm, and pnpm workspaces. Zero config required. AI-friendly and human-friendly documentation. Has an affected graph and rules for workspace code sharing. Comes with a CLI and TypeScript API.
To get started, all you need is a repo using workspaces for nested JavaScript/TypeScript packages. This adds enhanced features on top of plain workspaces, like getting metadata about the monorepo and running scripts across workspaces.
Start running some CLI commands right away in your repo, or take full advantage of the TypeScript API and its features.
Full Documentation: https://pacwich.dev
- Overview page
- Getting Started Guide
- Changelog: GitHub Releases
Terminology
The definitions of workspace and project differ between package managers and monorepo tooling.
In pacwich, the word workspace is closer to how it's used in npm and Bun, a workspace being a nested package in a monorepo. Not necessarily all packages are workspaces, but all workspaces are packages.
The project is synonymous with your root where workspaces are defined, often the root of your git repository as well.
This means you have a root project that has some number of workspaces. The root package is not considered a workspace by default, but it optionally can be.
Docs: Glossary page
#### Note: bun-workspaces This is the continuation of the bun-workspaces package that only worked with Bun. See the migration guide for more information. Read the blog post about motivations and development strategy. You can also instruct an agent to read https://pacwich.dev/intro/bun-workspaces-migration/index.md to assist with migration. Thanks to most core code and tests carrying over from bun-workspaces, pacwich inherits its maturity to a large degree.