New issue
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
feat: npm workspaces #21274
feat: npm workspaces #21274
Conversation
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems ok to move ahead with, assuming it fixes the reproduction repos
…ingh/renovate into feat/npm-workspaces
use workspaceDir instead of comparing packgaeFileDir to lockFileDir as lockFileDir will be . when lockFile is in root folder but packageFileDir is an `(empty string)
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤞 should be heavily testes on teal repos
🎉 This PR is included in version 35.63.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Changes
If workspaces present
--workspace=<worksapceName>
optionThis is a test implementation that gets the job done. It still needs some refactoring, dividing into functions and tests and better comments...will add/modify them once we agree on the implementation
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: