Carl Reid

> There is also a performance issue with compiling the moment I use react-babylonjs with next.js, that makes working with it very tedious. Not sure yet, but could be related...

I believe the transpile is needed because nextjs is expecting precompiled code and the babylonjs core is not shipped as such. However, that is actually only for the _server_ side...

> closing for inactivity, feel free to comment if this is still an issue I just hit the same thing, so there must be an issue somewhere. Just not sure...

> none of the client generators I can find work satisfactorily I have come to the same conclusion. I didn't try [OpenAPITools](https://github.com/OpenAPITools/openapi-generator), as I'd rather not have to install Java...

@jasonsoden Do you have an example of how you achieved that? @AndrewCraswell I see a mention in the README about working on a v3. Maybe server side rendering was considered...

@piksel Me again 🙈 Is there something blocking this from being released?

No worries, take it easy 😊

It seems the artifact from the previous build has expired, is it possible you could re-trigger the build / release this version? Was just about to host the pre-release package...

Wonderful! Thank you 😊 In which case, I'll wait until next week to see if you managed to make it through with a release before trying to host the artifact.

Okay, this seems to be a problem between `react-final-form-arrays` (3.0.0) and `react-final-form` (5.1.1). After updating `react-final-form` to 6.0.0 it works, as shown here: https://codesandbox.io/s/react-final-form-field-arrays-8cy2h