Comments (8)
Wow, great find! I jump between node versions too and haven't seen this issue.
Are you using nvm
or n
to choose the node version?
With n
the node_modules
directory is shared across node versions which can cause weird problems.
Can you do a which npm-check
and npm-check --version
on each of them?
from npm-check.
from npm-check.
Also, I have known outdated dependencies at --depth=3 and --depth=7 and node-check misses them. I tested by randomly picking a module at various depths
The goal of npm-check
is to see what in your package.json
could be updated, it doesn't check the dependencies of the packages you depend on. I might add a recursive option, but it's going to take a long time to query the registry for hundreds of modules so I'm not sure how useful it will be.
from npm-check.
Thnx for getting back quickly. I am using nvm
. Which = /home/ubuntu/workspace/node_modules/.bin/npm-check
with all three Node releases and 4.0.3 is the same as well.
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 $ npm-check
. I see in your screen shots you used $ npm-check -u
. It's prevalent if you drop the interactive mode.
from npm-check.
The goal of npm-check is to see what in your package.json could be updated, it doesn't check the dependencies of the packages you depend on. I might add a recursive option, but it's going to take a long time to query the registry for hundreds of modules so I'm not sure how useful it will be.
I miss understood and I thought it was running too fast.
Adding a --recursive
flag would be a huge enhancement being the sole purpose of us using this module is for security checking. I realize it would take a long while to run thru everything but it would flag obsolete modules. Them we can sift thru them and investigate if they may have had vulnerabilities. We have a tool for that too but it only works if its in the nps database (I'm an advocate for redundancy testing).
Also, adding a print to log while using --recursive
would be going above and beyond. Then our TODO.md generator can sniff the log for use later.
Keep me posted and let me know if you want me to open another issue (enhancement request) related to this.
Thnx -j
from npm-check.
with all three Node releases and 4.0.3 is the same as well
It sounds like you might have your prefix
hardcoded in the npmrc
, which was a common practice before nvm
.
If you don't want to do that, you can try re-installing with each version of node
to see if it fixes the problem, however I just tried your setup and didn't have your issue.
Can you tell me what registry you are using for each version of node?
npm config get registry
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?
from npm-check.
I'm going to close this as it doesn't seem like an issue with npm-check
. Feel free to leave more feedback if you figure out what was not working.
from npm-check.
I sent a PM to your public email.
from npm-check.
Related Issues (20)
- [v6.0.1] NPM reports moderate issues in dependencies
- bug(pnpm): devDependencies arenβt updated if pnpm package manager HOT 1
- FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
- CLI option for PNPM
- Update `package-json` to 7 HOT 2
- Support package alias
- bundled module having npm-check as dependency using ncc is throwing Error: Cannot find module '/Users/username/Home/Projects/project-name/dist/parser/coffee' while running
- Stale packages not detected if 'parent' node_modules already has the updated versions
- Updates fail because it uses `yarn` instead of `npm` HOT 6
- monorepo workspace/package is showing `NPM ERR! Registry error Package <Package_Name> could not be found`
- Tests failing HOT 3
- _css_loader@undefined
- Displays the change logs between versions
- Ignore outdated dependencies HOT 2
- Request for New Release of npm-check HOT 2
- npm-check incorrectly flags partial SCSS files as unused dependencies HOT 1
- When I run npm-check, I get an error saying '@ in JSON at position 3324'.
- Yarn 4 fails with --color=always
- is this package still maintained? HOT 3
- update depcheck version please
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from npm-check.