ERR_SOCKET_TIMEOUT on node v18

[hassnaseer]

ERR_SOCKET_TIMEOUT on node v18

[hassnaseer]

@raineorshine Please check this.

[hassnaseer]

[raineorshine]

Please fill out a complete issue report including exact steps to reproduce. The other issue was solved two years ago, so whatever problem you are running into is new and requires a complete issue report for me to investigate.

[raineorshine]

The screenshot appears to be a python error unrelated to npm-check-updates.

[hassnaseer]

i have run ncu -u then npm install

[hassnaseer]

this is latest error that i got

[hassnaseer]

but when i revert all things and use node version of 14.0.0 then this is working fine not working on node 18

[hassnaseer]

@raineorshine is this fine for getting the issue

[raineorshine]

Thank you for the additional information.

Are other global npm packages broken, or is it just npm-check-updates?

You can try npx pacote manifest ncu-test-v2 since that is what npm-check-updates uses under the hood.

[hassnaseer]

@raineorshine i ave use this but still same issue

[hassnaseer]

[raineorshine]

I'm sorry, I don't understand.

FWIW, the GitHub test action is passing on node v18, so it is unlikely a bug in npm-check-updates.

You might consider reinstalling node or npm, since you are getting an error before npm-check-updates begins executing.

[raineorshine]

If you're getting an error with npm i, as shown in your last screenshot, then it's an issue with npm or an incompatible package. npm-check-updates does not deal with installing dependencies or anything in node_modules. It only upgrades your package.json.

[hassnaseer]

I got it . But again the question is same i have reinstall aftere deleting the node modules . Only 1 thing that i have change i was using node14 now i am using node 18 . After this npm i also returns the error.

[hassnaseer]

the node modules has installed but when i run the project it shows this error now

[hassnaseer]

@raineorshine
it shows "glob-parent": "~5.1.2", error but its already available in package.json file

[raineorshine]

I'm not able to provide assistance on npm errors or errors in npm packages unrelated to npm-check-updates unfortunately. The fact that the issue occurs when running npm i after upgrading your package.json with npm-check-updates does not imply that the issue is with npm-check-updates.