Track pnpm workspace for each component #1578
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given a large pnpm workspace based monorepo, cdxgen will now precisely track the exact workspace(s) that resulted in the given components.
Following properties are available:
internal:workspaceRef
- bom-ref for the workspace component. This will be a component of typeapplication
and could be found undermetadata.component.components
.internal:workspaceSrcFile
- package.json file with the workspace definition.internal:is_workspace
- A boolean indicating that the dependent component is also a workspace.Also improved the logic to identify component version information for packages that are installed using a github url.