jsprops | Prototype level , OOP | Plugin library

Answered in Discord, reposting here:

You can't define arbitrary methods on the component like that. See that ...component? That's spread a record with static fields and updating a few fields like you did, e.g. render.

Also, you can't directly pass a ReasonReact component into a next method, I believe. It's probably asking for a react component class. See the interop section on how to expose the underlying js class for the js side.

In the meantime you can probably just wrap that component in a thin layer of js component that defines the getInitialProps

So you'd have a reactjs component that has getInitialProps, that renders a ReasonReact component that exposed the underlying class through interop. If I'm understanding you right, you'd also write ReasonReact bindings to that js wrapper if you're using that wrapper from Reason. Which makes this process a bit contrived, but you're hitting a pathological case here.

As an side: ideally, the Next.js API would ask for a component class, and a getInitialProps on the side, a totally agnostic function that's not attached onto the component class. That'd greatly simplify the binding process on the Reason side.