-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
"File not found: undefined" on a brand new project #800
Comments
Interesting. Any idea what file it's looking for? There should be verbose output in the terminal if you run |
Just checked on my linux box and there it works fine. Maybe it's an OS dependent thing? |
Or an existing attached service worker perhaps? |
That would make a LOT of sense because I was hacking on a preactcli app, in the same browser, and it's using I wish the error could have been better. ...until I get the same intuition as @rschristian. Shall I close this or shall we morph it to be about a rogue service worker and the poor error message? PS. Simply going into the devtools and unregistering the existing service worker makes it so the site works again. |
Besides, I should have figured it was service workers because I did get:
on the stdout. |
Yeah I'm thinking it might be worth creating a special case for & automatically unregistering Not sure if that's going to interfere with any users though. |
Fixed with #802 . We'll cut a new release for wmr soon. |
Describe the bug
Can't go to http://localhost:8080 after having
npm start
.To Reproduce
Steps to reproduce the behavior:
cd /tmp
npm init wmr repro-overlay-bug
cd repro-overlay-bug
npm start
open http://localhost:8080
Note that I haven't touched any files at all. Just run
npm init
andnpm start
.Expected behavior
I can actually see the sample Home page that is built for a split second but then it goes away.
Running
npm run build
andPORT=8080 npm run serve
followed by going to http://localhost:8080 works fine.Bug occurs with:
wmr
orwmr start
(development)wmr build
(production)wmr serve
Desktop (please complete the following information):
Additional context
We really should have a GitHub Action that tests
npm start
and going to the sample app in debug mode. It would have caught this bug.The text was updated successfully, but these errors were encountered: