-
Notifications
You must be signed in to change notification settings - Fork 323
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
npm run dev
not working
#9847
Comments
I have also tried the polyglot ydoc server mode (described in #9528), with the same result |
It works now. Since a clean build didn't help but the issue turned out to be transient anyway, I think it must have been caused by a zombie process. |
I’m facing the same issue now. Both clean build and reboot didn’t help. |
I faced this once, and running |
Emptying browser cache helped with the issue. |
I just encountered this on OS X. This worked:
|
Still getting this a lot. More efficient workaround:
|
Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?
Is this a regression?
What issue are you facing?
After #9528,
npm run dev
isn't working. The page is blank, and there is an error "504 (Outdated Optimize Dep)" in the console. The error occurs even in a clean build of the repo.Expected behaviour
The dev server should be usable
How we can reproduce it?
No response
Screenshots or screencasts
Logs
No response
Enso Version
develop after 5995a00
Browser or standalone distribution
Chromium
Browser Version or standalone distribution
chromium
Operating System
MacOS
Operating System Version
No response
Hardware you are using
No response
The text was updated successfully, but these errors were encountered: