Consuming projects can't find `JSX.IntrinsicElements` after v2.1.2
See original GitHub issueIn v2.1.2 consuming projects can’t find the JSX.IntrinsicElements
interface. forgo
is exporting JSX
, but forgo.createElement
isn’t detecting that.
This was introduced by the merge of 812177f (my commit, my bad). I’m not sure why this didn’t turn up when I tested of that commit.
I’ll have a PR up once I identify a fix.
Prior to v2.1.2, forgo
declared namespace createElement
with namespace JSX
inside of it. 812177f switched the full module import (import "./jsxTypes"
) to a types import (import type "./jsxTypes"
) to fix an esbuild issue, and that means the old way of declaring the createElement
namespace doesn’t work.
I’m trying to determine a new way to do that, and also why that’s necessary in the first place. I can’t find any documentation indicating TS JSX needs a createElement
namespace. So presumably there’s another way to go about the problem.
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top GitHub Comments
@spiffytech Tested on CodeSandbox. https://codesandbox.io/s/forgo-todos-typescript-9v0iy
It works! 🥳
Haha. I’ll try this today, and publish a new version. Thanks.