-
Notifications
You must be signed in to change notification settings - Fork 72
Issue with .svelte.js files and Svelte 5 #238
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
Comments
Can you provide a reproduction? |
dummdidumm
added a commit
to sveltejs/svelte
that referenced
this issue
Oct 9, 2024
Similar to a change that was part of #10459 Fixes sveltejs/svelte-loader#238
Merged
5 tasks
dummdidumm
added a commit
to sveltejs/svelte
that referenced
this issue
Oct 9, 2024
…ap (#13546) Similar to a change that was part of #10459 Fixes sveltejs/svelte-loader#238
dummdidumm
added a commit
that referenced
this issue
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This might not be a problem in svelte-loader but rather in the svelte compiler, but the issue shows itself in svelte-loader.
When I created a
xxx.svelte.js
file which got included in my webpack build I started getting a wierd error aboutError: callback(): The callback was already called.
. But that error turned out to not be the real error, it was just that an error was thrown here:svelte-loader/index.js
Line 97 in f2a7bc1
Which triggered this line:
svelte-loader/index.js
Line 101 in f2a7bc1
And since the error occured inside the callback the error became
callback(): The callback was already called
.The real error was:
I don't know what the cause is here, but if I stop passing
js.map
tocallback()
the error goes away so I guess it's something with Svelte 5s sourcemaps for.svelte.js
files that causes it.This is the contents of
js.map
when the error happens:The text was updated successfully, but these errors were encountered: