RedwoodJS in a monorepo

Anyone running/tried to run RW w/ NX/Bazel/Buck/Rush? What was your experience?

1 Like

No experience, but it depends on if the tool in question supports yarn’s workspaces, since that is how Redwood manages its sub-projects api and web.

I stumbled upon NX and I think I’m in love. Not sure how Redwood would fit in there tho but would be awesome if someone with more experience in both projects could elaborate if these two could integrate well, technically speaking.

1 Like

NX has so much trouble keeping their primary React module (NextJS) updated to current major version that it’s probably not a good idea to even use their monorepo framework. The docs / videos never updated. So good luck building a new module for RedwoodJS.

Given the pace that Redwood updates, I don’t think NX will be able to keep up since they have trouble keeping up with NextJS. Work can only start when NX team actually starts documenting so people can build/update bindings without being in the dark or takes support seriously.

Had this problem with both NextJS and React Native with NX. That’s why my OP was also asking about agnostic monorepo tooling-- I was considering moving off of NX.

1 Like

Thanks for your feedback!

I quickly understood that the NX documentation is lagging behind after going thru their React documentation, finding some outdated examples, so I will move with caution and try it out on simple sites that easily could fit in a monorepo. It also gives me a chance to try NextJS.

We’ll see where NX is heading and maybe in the future it could be a fit. Sorry for hijacking thread for a second :slight_smile:

1 Like

Nah don’t apologize for that. We need more people trying stuff out. I was disheartened that there was no response to this thread for months, haha.

1 Like