-
Notifications
You must be signed in to change notification settings - Fork 37
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
require.resolve not being listed as a dependency #42
Comments
Hey @mistic. Thanks for the issue! Can you provide an example of how you're using Based on my assumptions on how you're using it, we'd need to add support for it in the commonjs detective. I could definitely see your future example being a test case here: https://github.com/dependents/node-detective-cjs/blob/master/test/test.js#L33. Here is where we sniff for If you're unfamiliar with ASTs, you're basically iterating through the keys in a big object and looking for a particular part of it (if it exists). Here's a good tool for seeing the AST representation of some code to look for the part of the object that represents I'm super open to a PR in node-detective-cjs with the fix. |
Use native Object.assign
I'm trying to use this module in order to create a list of all the dependencies in use into my application.
However the
require.resolve
is not being listed as a dependency.Any idea how to solve this @mrjoelkemp ?
The text was updated successfully, but these errors were encountered: