Lyu, Wei-Da

Do you have a reproducible? It might have something to do with the error from typescript. It seems to have something to do with auto-import and module path. You can...

Can you still reproduce the problem? I can reproduce the error in the stack trace. But I can't reproduce it in emmet. (Doesn't remember if I could reproduce it in...

@shirakaba The JSDoc type support doesn't have to be as feature-rich as a typescript. I doubt a lot of people would type generic components with it. Also because we're using...

The second error (`Cannot call methods on an unopened document`) is probably relevant. I can't reproduce this on windows. So I need some more info to narrow down the possibilities....

Does the problem persist when you remove the commented-out import from `MyComponent4`? If not then the problem is just that. We could enhance our auto-import filtering with a more semantic...

You misunderstood. I mean remove the commented-out import. Not uncomment it. If you already have the import it definitely shouldn't suggest an auto import. We have a check for existing...

Should we keep it extend the `svelte.JSX.DOMAttributes` for a little while? Because this would probably break the custom DOM typedef in the new transformation. Or we can create some migration...

Have you tried following [this doc](https://github.com/sveltejs/language-tools/tree/master/packages/svelte-vscode#usage-with-yarn-2-pnp) for yarn 2 pnp ?

You can try setting logging the message between language-server and the extension: 1. add this config `"svelte.trace.server": "verbose"` 2. open the output channel near the integrated terminal, chose `svelte`, and...

Wondering if the tsserver reuses the same language service for both the react project and the svelte project. Can you try if adding a `jsconfig.json` to the svelte project root...