Skip to content
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

Closed
1 of 2 tasks
kazcw opened this issue May 2, 2024 · 6 comments
Closed
1 of 2 tasks

npm run dev not working #9847

kazcw opened this issue May 2, 2024 · 6 comments
Labels
--bug Type: bug --regression Important: regression -gui triage

Comments

@kazcw
Copy link
Contributor

kazcw commented May 2, 2024

Discord username

No response

What type of issue is this?

Permanent – Occurring repeatably

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

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

Screenshot 2024-05-02 at 09 06 19

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

@kazcw kazcw added --bug Type: bug triage labels May 2, 2024
@kazcw
Copy link
Contributor Author

kazcw commented May 2, 2024

I have also tried the polyglot ydoc server mode (described in #9528), with the same result

@kazcw kazcw added --regression Important: regression -gui labels May 2, 2024
@kazcw
Copy link
Contributor Author

kazcw commented May 2, 2024

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.

@kazcw kazcw closed this as completed May 2, 2024
@vitvakatu
Copy link
Contributor

I’m facing the same issue now. Both clean build and reboot didn’t help.

@vitvakatu vitvakatu reopened this May 8, 2024
@vitvakatu
Copy link
Contributor

image

@Frizi
Copy link
Contributor

Frizi commented May 8, 2024

I faced this once, and running npm run dev -- --force once helped to clear up the issue. That causes vite to force recreate the optimized dependencies bundle instead of using one from cache.

@vitvakatu
Copy link
Contributor

Emptying browser cache helped with the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug --regression Important: regression -gui triage
Projects
Status: 🟢 Accepted
Development

No branches or pull requests

3 participants