Individual lockfile per workspace
- [x] I'd be willing to implement this feature - [ ] This feature can already be implemented through a plugin **Describe the user story** I believe the best user story are the comments in this issue: https://github.com/yarnpkg/yarn/issues/5428 **Describe the solution you'd like** Add support for generating a lockfile for each workspace. It could be enabled via configuration option like `lockfilePerWorkspace`? **Describe the drawbacks of your solution** As this would be opt-in and follow well known semantics, I'm not sure there are any drawbacks to implementing the feature. One could argue if it should be in the core or implemented as a plugin. I personally don't have a preference of one over the other. **Describe alternatives you've considered** This could be implemented in the existing `workspace-tools` plugin. I'm unsure if the hooks provided by Yarn would allow for this, though. **Additional context** https://github.com/yarnpkg/yarn/issues/5428
Posted by migueloller on Apr 20, 2020, 6:37 PM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
Individual lockfile per workspace
- [x] I'd be willing to implement this feature - [ ] This feature can already be implemented through a plugin **Describe the user story** I believe the best user story are the comments in this issue: https://github.com/yarnpkg/yarn/issues/5428 **Describe the solution you'd like** Add support for generating a lockfile for each workspace. It could be enabled via configuration option like `lockfilePerWorkspace`? **Describe the drawbacks of your solution** As this would be opt-in and follow well known semantics, I'm not sure there are any drawbacks to implementing the feature. One could argue if it should be in the core or implemented as a plugin. I personally don't have a preference of one over the other. **Describe alternatives you've considered** This could be implemented in the existing `workspace-tools` plugin. I'm unsure if the hooks provided by Yarn would allow for this, though. **Additional context** https://github.com/yarnpkg/yarn/issues/5428
Comments (0)
No comments yet. Start the discussion.