Patrick Pircher

hmmm, this needs a way to distinguish exactly between svg elements and html elements... would need to add a parameter to `emitElement` when in svg context

😞 then i give up. would have been nice to have this

what about this? https://www.npmjs.com/package/html-element-attributes

I think making a pr to https://www.npmjs.com/package/html-element-attributes to generate a d.ts would then make ut usable

Would also need https://github.com/wooorm/svg-element-attributes

well, I couldn't give up just yet :) i build an own element.d.ts based on various packages from woorm. its all interfaces, so it should be possible to augment them...

this is also beeing worked on in #663, i mean the attributes autocomoplete/validation

@NullVoxPopuli any idea how I can fix this: ``` Error: node_modules/@glimmer/interfaces/index.d.ts(1,2[9](https://github.com/typed-ember/glint/actions/runs/7698348329/job/20977417907?pr=696#step:5:10)): error TS2834: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider...

> Does skipLibCheck help? > > Otherwise, glimmer has more bugs we need to fix (all relative imports should always use extensions when using node16, so it shouldn't be too...