Self closing textarea throws unexpected token

[ejoflo]

After installing the Svelte for VS Code extension, one of my .svelte files is producing errors in the <style> section of the code. The error is related to closing brackets in the CSS.

The following problems are reported:
'}' expected.
Unexpected token. Did you mean {'}'} or }?

My .svelte file works just fine and everything compiles without error so this is more of a minor annoyance. I am not sure how to reproduce this because like I mentioned, it was a previous file that I opened after installing the Svelte for VS Code extension. I have not seen this issue in my other files for the same project, just this one in particular. Screenshot below.

[jasonlyu123]

The problem is not style tag. It's something before it. Could you provide the code before or a minimum reproducible?

[ejoflo]

The problem is not style tag. It's something before it. Could you provide the code before or a minimum reproducible?

Had an issue pasting the code here. Here's a REPL with the entire .svelte file:

https://svelte.dev/repl/ff4656c237e04679b46fd00c5126ccc8?version=3.24.0

[jasonlyu123]

similar to #251 but in a different package

[jasonlyu123]

The problem is the self-close textarea. The parser we use doesn't support it. We'll see what can we do to fix it. You can replace it with a close tag<textarea></textarea> and the error will disappear.

[ejoflo]

The problem is the self-close textarea. The parser we use doesn't support it. We'll see what can we do to fix it. You can replace it with a close tag<textarea></textarea> and the error will disappear.

Got it, thanks. When using Prettier extension it automatically creates a self-close tag <textarea /> so it would definitely be a nice addition to support self closing tags. Cheers.

[ignatiusmb]

Turns out it's not just <textarea> but <iframe> too. Not sure why these 2 particular tags are throwing these errors but not others.

[jasonlyu123]

Every tag that can't self close in HTML would trigger it because we use an HTML parser. For now, the easiest way to avoid this is to put markup after script and style