-
Notifications
You must be signed in to change notification settings - Fork 278
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
[sitecore-jss-dev-tools] Update sitecore packages metadata generation logic to account for monorepos #1949
Conversation
…ackage-lock instead of node-modules
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.
Would it also make sense to cleanup some of the test-data package lock files for better maintainability?
…endencies the have smaller files
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.
Looks good to me! It's much cleaner now 👍
See some comments below. However I approved in advance
Description / Motivation
Previously getMetadata() was generating the metadata about the used sitecore packages through traversing the node-modules folder of the application. This approach does not work in a monorepo setup.
This PR addresses the problem by making some updates of the logic that gathers the metadata - it uses the
npm query
command to gather the information of the used sitecore packages and their exact version.Testing Details
Types of changes