Using reason-apollo in node.js

[studious]

We use reason-apollo in a mono-repo when developing.

We started with client side ReasonReact code but have now started adding some server side graphql queries. This is breaking due to reason-apollo compiling with import * style notation.

What is the best approach for solving this?

[baransu]

It should depend on your bsconfig.json. If you setup

"package-specs": {
  "module": "commonjs"
}

it should compile to require

[studious]

We are using a mono repo with yarn so our client side and sever side node_modules end up in the same directory when in dev.

Would commonjs work for both?

[emmenko]

You can make it work for both:

• compiling to ESM will require that you run your server code through babel to transpile it to CJS
• compiling to CJS will require that you instruct webpack but you loose e.g. the ability to do tree shaking

I would opt for the first option, to output ESM and to transpile the server side code with babel.

[thangngoc89]

package-specs actually accepts an array so you can tell bsb to output commonjs and es6 at the same time (but double compilation speed)

[Gregoirevda]

What solution did you pick @studious ?

[studious]

All of our reason applications use commonjs with a webpack/babel step for front end.