'JsxParser' cannot be used as a JSX component.

[codegdo]

Hi,

When I updated latest react 18.0.0. I have a warning highlight in typescript 'JsxParser' cannot be used as a JSX component.

Any ideas?

Thanks you for the library.

[Ghoral]

Hey I am getting the same error..any fix or workaround on this ?

[frandevel]

Same error here:
TS2786: 'JsxParser' cannot be used as a JSX component. Its instance type 'JsxParser' is not a valid JSX element. Types of property 'refs' are incompatible.
I guess this is something related to some method not returning ReactNode (what React 18 expects) but instead returning a JSX.Element
Any light on this? Thanks in advance

[frandevel]

Could it be that upgrading the types for React to v18 would solve the issue?

[frandevel]

@TroyAlford is there any way we could contribute to fix the issue? I can go for a pull request, but I cannot push any branch to create the PR.

[rick-yao]

This is due to the React version mismatch , I upgraded to v18 locally and the error is gone. But seems pr is blocked according to @frandevel @TroyAlford

[ShafSpecs]

Anyone solved it yet? Still facing the same issue

[henricop]

Any solution ? The code works, but it's not cool

[frandevel]

As @TroyAlford stated in some comment/email, the problem is that React went as a lonely rider with the element and attribute naming, making it a bit cumbersome to have nice compatibility with the library

[TroyAlford]

I'd be happy to take a PR here to support the React 18 typing. The proper return type is probably React.ReactNode rather than JSX.Element. Changing the React version probably warrants a major version bump.

[YossiSaadi]

Any news about this?
Thanks for this great lib btw!

[elitebyte]

I implemented the suggestion from @TroyAlford and upgraded the repo to React 18. I have made a PR. If you are looking for a temporary fork until PR gets merged feel free to use this:

In package.json:

"dependencies": {
    "react-jsx-parser": "github:EliteByte/react-jsx-parser#develop"
}

[frandevel]

@TroyAlford any update about the PR from @elitebyte ? It would be awesome to unlock the potential upgrades.

[TroyAlford]

Despite my remarkable slowness, which I apologize for, I just gave a review to that PR. Happy to continue this discussion there.

[frandevel]

@elitebyte , @TroyAlford
I created a PR with your suggestions on the @elitebyte repository. Feel free to have a look:
elitebyte#1

[TroyAlford]

I've just released v2.0.0-beta.0 which should resolve this. Could those of you subscribed to this please verify that this fixes the issues you've been seeing?

I don't want to publish a regular 2.0.0 version until I get verification that it actually resolves this and doesn't break your downstreams.