Closed antony closed 5 years ago
This is almost certainly a bug in Svelte and not in Sapper, although I'm not sure why I'm having trouble reproducing it with Svelte alone. Moving the issue to the Svelte repo.
I should've written a test when I fixed this the first time in #3186, maybe then this wouldn't have snuck through 😬
@Conduitry wow - I reviewed all the commits and I didn't spot this :)
Fixed in 3.12.1.
@Conduitry This still happens for me, even after updating to 3.12.1. Could it be because Sapper still uses 3.6.9?
The devdependency of "svelte": "^3.6.9"
in Sapper won't have any effect on what version of Svelte it's using in your installation. What does running npm ls svelte
display?
We're using 3.12.1.
If you have a small repro, please open a new issue with it.
Describe the bug It seems that after upgrading to Svelte 3.12.0, using an @ in an attribute value causes a compiler error on the client.
This works as expected in 3.11.0
Logs
To Reproduce https://github.com/beyonk-adventures/sapper-attribute-issue
Expected behavior The bundle should compile correctly.
Information about your Sapper Installation:
Sapper 0.27.0+
Svelte 3.12.0
Dynamic application
Rollup (haven't tried webpack)
Severity It's annoying and broken, but can be worked around temporarily.
Additional context This only occurs in Sapper projects, yet occurs on the client-side build.