-
Notifications
You must be signed in to change notification settings - Fork 44
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
Support --discoverNodeModules
option like WCA does it
#123
Comments
The 'lifecycle' of the analyzer is:
We can only know which imports/node_modules to analyze when we're analyzing the source code, at which compilation has already happened. Currently there's no good solution to this yet. As a temporary workaround, you can specify the dependencies/node_modules you want to analyze in the export default {
globs: ['node_modules/my-dependency/**/*.js'],
} |
Thanks for fast response, still not sure this will help to override last entry the way you suggest
|
ah yes we should allow that then. But we'd also need to ignore Edit: Maybe we should have some similar logic, if the user has provide a glob including |
Hi, there. I would like to use https://github.com/break-stuff/cem-tools/tree/main/packages/vs-code-integration to writing Custom Elements with https://github.com/material-components/material-web ( manifest file not supplied ) , but due to the limitations of this issue, I have not been able to do so. Since custom-elements-manifest analyzer@0.9.0 uses globby, I tested it with `globby' alone. https://gist.github.com/wtnabe/bedac43ed85b5ad6f71e6d3b78edb6ad#file-result-txt As a result, I found that the current It would be better to put the I have come up with a solution based on the assumption that
In most cases, this should work fine. If there is no need to change the settings in How about this ? |
web-component-analyzer is allowing to drill down to
node_modules
folder, it's essential functionality for my project and it's a show stopper for this tool.https://github.com/runem/web-component-analyzer/blob/1a71064c66a38923aab783e3885feefccfd19589/src/cli/analyzer-cli-config.ts#L23
The text was updated successfully, but these errors were encountered: