Upgrade to @rescript/react with bindings that use reason-react

[dan003400]

Is there a way to upgrade your project to @rescript/react when using bindings that are still using reason-react?

We are seeing errors from bindings that still use reason-react - make inconsistent assumptions over interface React

Thanks!

[ryyppy]

Can you join the discussion within this issue? Would be interesting to see what dependencies are out there.

TL;DR: Quickest workaround right now is copying the third-party bindings into your project until package maintainers bumped their codebases to @rescript/react.

Related topic:

[Discussion] reason-react -> @rescript/react Migration Path

Some might have noticed that there is already a @rescript/react package, which is a simple ReScript syntax port of reason-react with a few renamed module names (and very old apis removed). We didn’t do much advertisement around it just yet, because we are still doing some fine-tuning for edge-cases where existing reason-react users experience problems in their migration (it involves some simple breaking changes). There is one particular migration issue that is more related to package management…

[dan003400]

Makes sense, wanted to see if there was something I possibly missed, as I can see an upgrade like this being a lift for some projects if they are currently replying on a lot of bindings.

Thanks @ryyppy