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
Upgrade from 4.8.0 - 4.9.0: unterminated string literal error during svelte-check, build fails #402
Comments
This looks like it could be related to #401 |
Hey, @mlandisbqs 👋 Thanks for the report! Can you share your file content or at least all identifiers beginning with |
That's more than enough and is probably the culprit. This helps a lot, thanks! |
@kaisermann I'm sure you have enough info, but just in case: I just ran into the same thing with this code:
and can confirm that removing |
This breaks in 4.8.0 for me. Only 4.7.4 and older worked. |
Found the culprit, will prepare a PR shortly |
Fixes #402 Co-authored-by: Simon Holthausen <simon.holthausen@accso.de>
Fix released in v4.9.4 🎉 . Thanks @dummdidumm! |
Describe the bug
Isolated to 4.9.0 code changes (4.8.0 compiles the same code without the bug):
https://github.com/sveltejs/svelte-preprocess/compare/v4.8.0...v4.9.0?short_path=61c21cb#diff-96443e2ca98f566a13837889beb8b5a9da9d97c396ad64bc3a28dbf0e3557f37
After the upgrade -- the generated code contains unterminated string literal which typescript then fails to compile.
This happens right here in the code (line 140, src/transformers/typescript.ts):
^-- the codestores array includes an entry like this
["'"]
Logs
Expected behavior
codestores should be captured without a single quote value in the array.
Information about your project:
Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10)
Your operating system: (e.x. OS X 10, Ubuntu Linux 19.10, Windows XP, etc)
MacOs 10.15.4
svelte-preprocess
version (Please check you can reproduce the issue with the latest release!)4.9.0 (same problem on latest release)
Whether your project uses Webpack or Rollup
rollup
The text was updated successfully, but these errors were encountered: