bun-workspaces has been deprecated and is now developed as pacwich, which supports Bun, npm, and pnpm workspaces, with a mostly backwards compatible CLI and API. Users can expect little to no disruption beyond the package name change and config file name changes.
A full migration guide covering all differences between the packages is available at https://pacwich.dev/intro/bun-workspaces-migration
Installation docs are available at https://pacwich.dev/intro/getting-started
You can also instruct an LLM agent to read https://pacwich.dev/intro/bun-workspaces-migration/index.md to assist with migration.
Read the launch blog post about the motivations and development strategy.
bun-workspaces will not receive further releases save for critical security patches, if necessary. This website will stay up at least through 2026. Once decommissioned, documentation will be consolidated to the package README.
Concept: Script Execution Order
Overview
Using the workspace configuration, you can set an "order" value to sort the execution order of a script per workspace.
You may want to run scripts in series (--parallel=false in the CLI or option parallel: false in the API) instead of the default parallel so that
each script completes before the next one starts.
Default Order
By default, workspaces are sorted in alphanumerical order of their relative path from the project root.
Configured vs. Default Order
Workspace scripts with
an "order" value will be executed before workspaces with no "order" set for the same script, falling back to the default order.
Example
In this example, any other workspaces in the project with an "order" for the "start" script less than 10 will be executed before this workspace,
and any workspaces with an "order" for the "start" script greater than 10 will be executed after this workspace.
{
"alias": "myApp",
"scripts": {
"start": {
"order": 10
},
"test": {
"order": 20
}
}
}