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.
I'm the maintainer of webpack-license-plugin, so I have quite extensive experience with license compliance and reaching it with JavaScript build tools.
I was having the problem that your plugin didn't find any licenseTexts, even though the
/LICEN[CS]E/i
files were in the appropriate node_modules subdirectories. Turns out this is a problem that theglob
library has had on windows (turns out, even on WSL for windows, which I'm using) for years when you use it with thenocase
option.To fix this, I removed the
nocase
option and instead adjusted the glob pattern fromLICENSE*
to[lL][iI][cC][eE][nN][sS][eE]*
. It's not nice, but it circumvents any problems finding these files on windows.Because of my experience with the webpack plugin linked above, I also know that a few projects name their files LICENCE instead of LICENSE, so i included this option in the new glob pattern, making it
[lL][iI][cC][eE][nN][cCsS][eE]*
.