David Sancho

I'm facing the same problem trying to work with reason-react-native. I'm using Expo. Is there any solution? Can I monkey-patch the fonts?

Sneaking into here ^^. Ast_helper usually brings more control over the creation of Ast nodes, for example attributes are always empty on Ast_builder. How would you see this in the...

The workaround for now is to disable the build of fsevents with a resolution: ```json "resolutions": { "fsevents": { "source": "no-source:", "override": { "build": "true" } } } ```

Inside `package.json` or `esy.json` @jerobarraco

This error occurs when you have nested esy.json folders and try to install on the inner folder.

Would be great to document how to work with transitive dependencies. In the context of depending on an opam package and those have pinned dependencies or dev dependencies.

Hey @johnhaley81 Could you share a repo where I can look into it? Without digging much, The issue comes from importing a component that it's undefined instead of a fn....

Hey @johnhaley81, did you solve the problem? Is there something that can we do?

Hey, seems that the JSX 2 syntax was changed. https://github.com/draftbit/bs-storybook/commit/2d7b1c3e00b8d1ee84044c0a1217076a43fea241 Maybe the version of npm doesn't match with the status of master. I will try to sync them, thanks.

Hey @BlueHotDog Their API isn't something doable in Reason that translates one-to-one, the CSF module relies hardly on JavaScript type weakness which is almost impossible to bind in Reason: -...