question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consuming projects can't find `JSX.IntrinsicElements` after v2.1.2

See original GitHub issue

In 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:closed
  • Created 2 years ago
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
jeswincommented, Feb 13, 2022
1reaction
jeswincommented, Feb 2, 2022

I may throw TypeScript into a volcano if this somehow still isn’t fixed

Haha. I’ll try this today, and publish a new version. Thanks.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Typescript complains Property does not exist on type 'JSX ...
Property 'div' does not exist on type 'JSX.IntrinsicElements'. I think the root cause was vscode (me) accidentally editing type definitions in node_modules ...
Read more >
Property does not exist on type 'JSX.IntrinsicElements'
Open your terminal in the root directory of your project (where your package.json file is) and run the following command. shell.
Read more >
@react-three/drei - npm
Start using @react-three/drei in your project by running `npm i ... it won't be responsive and you have to calculate aspect ratio yourself....
Read more >
@react-three/drei NPM | npm.io
It makes children invisible while rendering to the internal buffer so that they are not included in the reflection. type Props = JSX.IntrinsicElements['group'] ......
Read more >
material-ui/core/CHANGELOG.md - UNPKG
71, v4 doesn't have official support for React 17 like v5 has. Use it at your own risk. 72, - Fix right-to-left support...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found