-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
404 /@npm/@npm/[package-name] - npm registry lookup failed #903
Comments
For completeness, here's a full output when I run (In this case both
Another run with This time I noticed the the line
|
maybe same with #919 |
Describe the bug
When running wmr in dev/watch mode I often get the following error when I try to view the page in my browser:
The error is not very consistent, sometimes the page loads but at least ~50% of the time I see the error and I have to exit, delete the
.cache
folder and restart wmr and hope it works.It's not very consistent with which package it can't find, either. Most of the time it's one package, sometimes multiple. So far, I think I've only seen the following packages not being found:
The packages in question are present in the
node_modules
folder. I checked the.cache/@npm
folder, and if the error occurs, the packages are missing there, so it seems wmr (silently) fails to cache the package?This issue makes working with wmr pretty impossible for me :(
Note: Not entirely sure if deleting the
.cache
folder is required but from my observations so far, restarting wmr without deleting the.cache
folder just causes the same error with the same package every time I reload the page. When I do delete the cache folder, it either works or I get another 404 but not always the same package.To Reproduce
Steps to reproduce the behavior:
npm start
localhost:8080
Expected behavior
I expect no 404 errors
Bug occurs with:
wmr
orwmr start
(development)wmr build
(production)wmr serve
Desktop (please complete the following information):
Additional context
#882 covers the same issue but has been closed by the reporter without a clear description of the cause and/or how to fix it. Another user reported he's (also) seeing this issue with the
filter-obj
package.This problem occurs whether I run wmr via PowerShell or a Ubuntu terminal (WSL 1.x). Note: I do run the WSL terminal in the same (windows mounted) folder, so
/mnt/c/path/to/project
.The text was updated successfully, but these errors were encountered: