search

npm / registry-issue-archive

An archive of the old npm registry issue tracker
https://npm.community
249 stars 47 forks source link

Missing .tgz files for @types/node 9.4.2 and 9.4.3 #347

Open Jasu opened 6 years ago

Jasu commented 6 years ago

These packages did previously work, now they don't:

curl  'https://registry.npmjs.org/@types/node/-/node-9.4.2.tgz'
{"error":"Not found"}
curl  'https://registry.npmjs.org/@types/node/-/node-9.4.3.tgz'
{"error":"Not found"}
martinratinaud commented 6 years ago

Hi

I noticed the same problem and did this workaround https://medium.com/@martinratinaud/docker-fails-to-build-due-to-not-found-types-node-9-4-2-918d60c2f79e

Hope this helps

tendermario commented 6 years ago

My CI failed due to this as well.

Not sure if this is the right way to do things, so feedback is appreciated. My solution for now is deleting my package-lock.json, and run npm i to update modules given their version limits in the package.json. It updated @types/node to version 10.3.2.

Looking further, It stems from a dependency chain of: cheerio > parse5 > @types/node. jest > jest-cli > jest-environment-jsdom > parse5 > @types/node. We don't actually use cheerio, so I could just remove that package, but the issue with jest still remains.