-
Notifications
You must be signed in to change notification settings - Fork 123
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
Unexpected token error in REPL but not locally #354
Comments
Error originally reported in janosh/svelte-multiselect#80. |
I think this is because of this change. https://github.com/janosh/svelte-multiselect/pull/75/files#diff-7d86c55b55f23806b2be4051d790e7c775fd5fa4e1ad3fc2da59eb51ce25c0e9R3 I took diff between 4.0.6 and 5.0.0. And due to |
Transferring this to the |
@baseballyama I thought that strange remnant from the type import might be the issue too at first but later v5 releases of <script>import { createEventDispatcher } from 'svelte';
import { get_label, get_value } from './';
import CircleSpinner from './CircleSpinner.svelte';
// ... |
Same here: |
Just noticed that version 7.0.2 of @gyurielf Apparently the fix was to remove a circular import between @Conduitry Maybe this also helps point at how to make the REPL more robust? |
Describe the bug
svelte-multiselect
stopped working in the REPL in v5.0.0. The previous v4.0.6 release is working fine.The error message v5 raises is: Unexpected token (Note that you need plugins to import files that are not JavaScript)
Sadly the REPL gives no stack traces. I've been looking through the changes I introduced between these 2 releases but nothing jumps out. v5 works fine when used locally too. I was also looking through the REPL compiler's JS output but couldn't spot any issues. Any debugging advice would be great.
Reproduction
v:4.0.6 (working): https://svelte.dev/repl/4279890dae0942caa860e74f2e7a8a6f?version=3.48.0
v5.0.0 (broken): https://svelte.dev/repl/ea202bd627134d898802a11cfaf8ff0e?version=3.48.0
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: