-
Notifications
You must be signed in to change notification settings - Fork 28
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
Filter scoped modules correctly #37
base: main
Are you sure you want to change the base?
Conversation
Fixes microsoft#25 A valid node module name is either `\w+` or `@\w+/\w+` never `@\w+`. This is enough of a hairy internal implementation detail that filter should probably not be exposed even as an (undocumented) option. But leaving alone for now as changing the pattern has been a useful workaround.
Thank you so much for this!! 🙂 FYI, I think the tests will break when using Yarn PnP, since then there won't be a node_modules folder. |
This fixes the problems described in #45 and #43 for me. If anyone else cares, this PR can also be used as a workaround by adding the new LicenseCheckerWebpackPlugin({
allow: "(Apache-2.0 OR BSD-2-Clause OR BSD-3-Clause OR MIT OR 0BSD)",
filter: /(^.*[/\\]node_modules[/\\]((?:@[^/\\]+[/\\])?(?:[^@/\\][^/\\]*)))/,
... Would still be better if this could be merged and released :) |
…ugin` Filter scoped modules correctly in `license-checker-webpack-plugin` to fix an error while building. See also: microsoft/license-checker-webpack-plugin#37
anychance microsoft will actually review this? |
Part of the issue may the that the maintainer now works at twitter not ms. Maybe @unindented could suggest a former colleague I could bug about taking over package? |
1 similar comment
Part of the issue may the that the maintainer now works at twitter not ms. Maybe @unindented could suggest a former colleague I could bug about taking over package? |
Have same issue with
|
Fixes #25
A valid node module name is either
\w+
or@\w+/\w+
never@\w+
.This is enough of a hairy internal implementation detail that filter should probably not be exposed even as an (undocumented) option. But leaving alone for now as changing the pattern has been a useful workaround.
There are some other implications from the webpack 5 changes to
fileDependencies
and the current code behaviours but those will need a bit more discussion to address I think.