JamieMason / JamieMason/syncpack
feat(cli): add support for one-off version groups
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
### Question
I'm using react 17, but in new packages in the monorepo I end up using `npm install react`, which adds react 19
syncpack's solution is to bump everything to v19 instead of having the new arrival match the existing versions.
How can I force syncpack to use v17 instead? Currently the process is very manual
### Code of Conduct
- [x] I agree to follow the [Code of Conduct](https://github.com/JamieMason/syncpack/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start at syncpack's CLI entry point and trace how version groups are currently configured and applied. Confirm how a one-off group should select an existing React 17 version without changing the rest of the monorepo, then add coverage for the reported React 17 versus React 19 scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100