Burton Smith

My plugin relies on this type being set in the manifest

I think that should work for me.

Oh, this is fantastic! Thank you!

@jasonlyu123 do you have a working example of this? It doesn't seem to work in my sample app.

Yeah, here's a simple repo. https://github.com/break-stuff/svelte-custom-elements-demo

I have added a `additional-svelte-typings.d.ts` to the `/src` directory and updated the `tsconfig.json` to `"include": ["src/**/*"]` (basically just followed the steps in the docs).

Yes, I don't see any difference in having it vs not having it in my repo.

Yeah, I created a package to generate that, but it would be nice if devs would only have to set one thing for types and autocomplete. https://www.npmjs.com/package/custom-element-vs-code-integration

Interesting... @usrrname Are you creating a proxy object in the light DOM that the label then references rather than the custom element?

Was this comment meant for something else?