We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, syncpack will fail in the following case:
// packages/ui/package.json { "name": "@monorepo/ui", "version": "1.0.0" }
// apps/store/package.json { "name": "store" "dependencies": { "@monorepo/ui": "workspace:^" } }
Error would be:
= Default Version Group ======================================================== ✘ @monorepo/ui workspace:^ → 1.0.0 apps/store/package.json > dependencies [LocalPackageMismatch]
This is undesirable because workspace:^ is the default version specifier used by pnpm add --workspace @monorepo/ui.
workspace:^
pnpm add --workspace @monorepo/ui
To make a monorepo work, one needs to add custom syncpack config: https://jamiemason.github.io/syncpack/examples/pnpm-workspace-protocol/
Syncpack should support local packages with workspace:^ and workspace:* version ranges without any additional config.
workspace:*
No response
The text was updated successfully, but these errors were encountered:
Thanks a lot @VanTanev, I made a start on this on the v14 branch after our chat. The next alpha release will include some changes for this 👍
Sorry, something went wrong.
No branches or pull requests
Description
Currently, syncpack will fail in the following case:
Error would be:
This is undesirable because
workspace:^
is the default version specifier used bypnpm add --workspace @monorepo/ui
.To make a monorepo work, one needs to add custom syncpack config: https://jamiemason.github.io/syncpack/examples/pnpm-workspace-protocol/
Suggested Solution
Syncpack should support local packages with
workspace:^
andworkspace:*
version ranges without any additional config.Optional comments
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: