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
JavaScript error when loading REPL on the website #3160
Comments
If you look at the Network panel for the request/asset the REPL is making, you'll probably find that it's a Google 404 page. There's some Cloud Run issues happening today (affecting more than svelte.dev) and we're kinda at the mercy of their ability to find a solution right now. If you can confirm for us, that'd be great – thanks! |
What I was seeing before and what I'm seeing now is that https://svelte.dev/workers/bundler.js is getting truncated, not that it's a 404, and this is the syntax error that browser doesn't like. This might be related to GCR issues or it might be because we need to increase the memory allocation. |
I've increased the memory limit and https://svelte.dev/workers/bundler.js isn't getting truncated anymore for me, and the REPL is working again (when things don't 404). |
bundler.js is getting truncated for me again :-/ |
I'm experiencing the same problem on the |
I'm also seeing bundler.js being truncated, FWIW. |
Same here, bundler.js just contains an exclamation mark:
|
looks like the problem everywhere! |
me too! |
Google have announced that this issue was resolved, so this should be fixed. At worst you might need to do a hard refresh if it cached a bad version. I'll be optimistic and close this, but shout if you see it again |
Same issue |
Happens again: https://svelte.dev/repl/hello-world?version=3.53.0 |
See #8010 |
Trying to load the Svelte REPL (https://svelte.dev/repl/hello-world?version=3.6.3
) keeps showing "loading Svelte compiler..." while giving the following error in the console:
Uncaught SyntaxError: missing ) after argument list
(bundler.js:1:63505)Tested browsers on macOS Mojave (10.14.5):
The text was updated successfully, but these errors were encountered: