Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Suggestion
On thev6 branch, we now get typecheck (tsc) complaints inast-spec's fixture for augmentingJSX.IntrinsicElements:
~/repos/typescript-eslint/packages/ast-spec $ yarn typecheckyarn run v1.22.19$ tsc -p tsconfig.json --noEmitsrc/jsx/JSXNamespacedName/fixtures/component-dashed/fixture.tsx:8:24 - error TS2339: Property 'foo' does not exist on type 'JSX.IntrinsicElements'.8 const componentBasic = <foo />; ~~~~~~~src/jsx/JSXNamespacedName/fixtures/component-dashed/fixture.tsx:9:25 - error TS2339: Property 'foo-bar:baz-bam' does not exist on type 'JSX.IntrinsicElements'.9 const componentDashed = <foo-bar:baz-bam />; ~~~~~~~~~~~~~~~~~~~Found 2 errors in the same file, starting at: src/jsx/JSXNamespacedName/fixtures/component-dashed/fixture.tsx:8It happens both for traditional names (e.g.foo) and for TypeScript 5.1's new namespaced names (e.g.'foo-bar:baz-bam') added in#7088. So I don't think it's specific to TS 5.1's namespace changes.
But... why is this happening? Why is the fixture not allowing augmentation ofJSX.IntrinsicElements?
I'm 80% confident this is a silly little mistake I made in mergingmain ->v6, but can't figure it out... :sob