You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NX is the successor to Lerna, which Gutenberg uses. So you can get an idea of how it works if you think about WP.
Why?
Essentially for code sharing and faster/effecient builds.
Imagine you're an agency that has 4 plugins, 3 themes, a desktop app, a website, and a few backend apps. Sharing code between all of these while maintaining separate build and release workflows is a pain. A monorepo solves that.
Create block sets you up with a primitive monorepo in that it will build multiple blocks for you. It stops there though. It also sets you up to release the blocks as a single plugin.
Create block could start building out similar features the other tools provide, OR someone could build (on stream) integrations for the other tools.
Building the perfect mono repo specific to WordPress would be nice though, but a lot of work.
The text was updated successfully, but these errors were encountered:
Might be worth exploring setting up a monorepo for agency or larger product type development.
Two popular tools
NX: https://nx.dev/
Overview of NX: https://egghead.io/courses/scale-react-development-with-nx-4038
Turborepo: https://turborepo.org/
NX is the successor to Lerna, which Gutenberg uses. So you can get an idea of how it works if you think about WP.
Why?
Essentially for code sharing and faster/effecient builds.
Imagine you're an agency that has 4 plugins, 3 themes, a desktop app, a website, and a few backend apps. Sharing code between all of these while maintaining separate build and release workflows is a pain. A monorepo solves that.
Create block sets you up with a primitive monorepo in that it will build multiple blocks for you. It stops there though. It also sets you up to release the blocks as a single plugin.
Create block could start building out similar features the other tools provide, OR someone could build (on stream) integrations for the other tools.
Building the perfect mono repo specific to WordPress would be nice though, but a lot of work.
The text was updated successfully, but these errors were encountered: