-
Notifications
You must be signed in to change notification settings - Fork 237
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
Node Engine Not Specified (Diff output w/diff versions) #48
Comments
Wow, great find! I jump between node versions too and haven't seen this issue. Are you using With Can you do a |
The goal of |
Thnx for getting back quickly. I am using Could it be a npm version issue? didn't think to test that 'til now. I am running on 2.14.7. Also run your test using |
I miss understood and I thought it was running too fast. Adding a Also, adding a print to log while using Keep me posted and let me know if you want me to open another issue (enhancement request) related to this. Thnx -j |
It sounds like you might have your If you don't want to do that, you can try re-installing with each version of Can you tell me what registry you are using for each version of node?
It's just strange that the error is that it can't get to the registry. If you'd like to discuss the recursive option further can you open a new issue to keep them separated? |
I'm going to close this as it doesn't seem like an issue with |
I sent a PM to your public email. |
What Node engine
npm-check
is attended to be ran in? The engine is not specified in thenmp-check
package.json?e.g.:
I happen to notice after switching to a different Node release, a known-outdated dependency was not being detected anymore. I ran tests using v0.10.3, v0.12.0 & v4.2.1 and with each node environment,
npm-check
outputted different results (see attached screenshot) as well withnpm-check -u
. If I ran the same test within the same Node environment, the results were consistent with that node version.Also, I have known outdated dependencies at
--depth=3
and--depth=7
andnode-check
misses them. I tested by randomly picking a module at various depths and:and it missed them.
Also, Thnx for spending the extra time implementing the interactive mode! The Team will love it once I know I can use it. -j
The text was updated successfully, but these errors were encountered: