Closed xavi7th closed 1 year ago
I can second that I am getting the same error when using svelte-loader 3.1.1. I have not been able to find a workaround
same issue using esbuild, hooked in native svelte.compile
Is this still an issue? If so, could you provide more details? Minimal repro project would be ideal, but if you don't have it, I can look at a real project which breaks for you.
Hello @bershanskiy. Yes this is still an issue for me. If you are ok with it I could add you to a private repo which breaks for me.
I have noticed that using Laravel 8 and the latest Svelte breaks the devtools.
If you are ok with it I could add you to a private repo which breaks for me.
Yes, that could help to find root cause and create a minimal reproduction steps.
If you are ok with it I could add you to a private repo which breaks for me.
Yes, that could help to find root cause and create a minimal reproduction steps.
Invite sent. I am available to answer any questions you might have. Thanks once again.
@bershanskiy any updates here?
@bershanskiy any updates here?
Current extension logic is rather odd and requires significant rework to fix all quirks. I created a few PRs, some of which were already merged, and 4 more are still open and unreviewed. At this time, I'm not sure how to proceed to minimize merge conflicts/breakage.
Describe the bug I just updated to version 3.0.0 of svelte-loader and I noticed that it broke dev tools. When I downgraded back to ^2.13.0 everything works fine.
To Reproduce Steps to reproduce the behavior:
Additional context I believe it has to do with this change in the new svelte-loader:
compiler options must now be specified under compilerOptions
. I have not tested this supposition though.Thanks for your work with the devtools. It's been so helpful that I am not updating svelte-loader yet for just this reason.