Skip to content
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

NPM packages are either ignored or analysed fully #43

Open
grahamdyson opened this issue Oct 7, 2019 · 0 comments
Open

NPM packages are either ignored or analysed fully #43

grahamdyson opened this issue Oct 7, 2019 · 0 comments

Comments

@grahamdyson
Copy link
Member

grahamdyson commented Oct 7, 2019

By default JavaScript packages are ignored (see http://devsnicket.com/eunice/javascript/options/#ignore-paths). This means dependencies on their content aren't represented.

People won't normally want the structure and dependencies, from within and between 3rd party packages, to be represented. Doing so would also have an affect on performance.

An intermediate option could be to include packages, but only exports (modules and CommonJS) from their files.

If issue #51 was resolved the minimum required for this issue would be to create items with names of sub-directories. This would need to done for the node_modules directory and sub-directories of the scope sub-directories which are suffixed with the at symbol. This wouldn't need implementing in the JavaScript analyzer which looks inside source files.

@grahamdyson grahamdyson changed the title JavaScript packages are either ignored or analysed fully NPM packages are either ignored or analysed fully Oct 10, 2019
@grahamdyson grahamdyson modified the milestone: backlog Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant