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
[BUG] Generated bom fails to include package luxon
#1237
Comments
nope. not intended for now. see #778 (comment) A fix would be, if "luxon" added a (proper) name to the package they defined in |
💁 |
possible solution: if component has no name, then add it anyway with a name like |
@tomsontom could you pullrequest/help shape a setup for regression tests? |
I'll take a look next week |
luxon
should be fixed by #1284 |
Describe the bug
If luxon is used in the application. The plugin fails include it in the output.
To Reproduce
Setup
Use luxon
Change app.component.ts to look like this:
Run build
Expected behavior
I would expect that
dist/.bom/bom.json
to contain luxonScreenshots or output-paste
luxon not contained
Environment
Additional context
The reason luxon is not contained in the output is that "node_modules/luxon/src" contains a filed named "package.json" with the following content
See https://github.com/moment/luxon/blob/3125686af82d9a25c7267a1cf1eb838a3d41144f/src/package.json#L1 and so cyclone is unable to find a name and skips luxon in the output.
A possible fix would be to make
cyclonedx-webpack-plugin/src/_helpers.ts
Line 28 in ac87cd7
package.json
The text was updated successfully, but these errors were encountered: