Lyu, Wei-Da

I also prefer option 3. Maybe we can export some functions from the plugin package or create another utility package to reuse some logic. For example, svelte-sys, source mapping utility,...

Seem like the [injection rules](https://github.com/sveltejs/language-tools/blob/6e0396ca18ea5e7da801468eab35cdef43b3c979/packages/svelte-vscode/syntaxes/svelte.tmLanguage.src.yaml#L7) here doesn't work in the markdown code block for some reason. We'll see whether that's possible to fix.

We have [special treatment](https://github.com/sveltejs/language-tools/blob/20ade7cf5cdabc4c1fa05dcd158481db5012583a/packages/svelte-vscode/language-configuration.json#L30) with the script and style tag so that it can be folded without indentation. I don't know if it's possible to show the end tag.

It's technically not a "bug". Because you could also do `bind:this="{}"`. I hesitated to change this as someone might like this style more. Also, it might mess up people's muscle...

What is your use case? We probably also need to know what the target audience for this documentation is. There are already a lot of editor plugins so it might...

There are ways to enhance the typing. https://svelte.dev/docs/typescript#enhancing-built-in-dom-types

It does work in your repo. Are you expecting to have completion for it as well?

The difference is it will be type-check for the element.

There is another way to add custom tag name completion. It's only a local config, so it's not something library authors can leverage, but it's still a good workaround until...

Can we make this configurable? Currently typescript eslint doesn't support zero config type (#2073) and there is also #2053 that we haven't figure out the exact reason. Also, these types...