Unfortunately yes. It does interfere with Svelte plugin's nice thing.
It's quite a subjective matter. I just cannot live without emmet. I'm not a front end developer, so all I do is type the same boiler plate code again and again to have a prototype up and running. For that emmet comes useful.
I don't have a problem with editing the props manually because no matter what, the Svelte compiler will take care of it. Neither does the Svelte plugin provides any intelisense feature.
This is the reason I went with this setup. I'll try to find a workpath which works for the both sides.
Thanks for leaving this comment ;)
Nice work! Looking forward to see your series. It will be fun exploring the routes, async communication etc.
All the best!
Jonathan Greaves
Full Stack Dev
Your emmet advice is good, to help with HTML etc. but associating .svelte files with .html removes all of the niceties the VS Code Svelte plugin adds.
Svelte files associated with html:
<svelte:window on:keydown="{handleKeydown}" />and when not associated with html
<svelte:window on:keydown={handleKeydown} />