3 ms·
A well structured pnpm monorepo and a plugin system / architecture has made all the difference for us at Lowdefy [0]. Additionally we’ve architected a way to b
by gervwyk 2y ago
A well structured pnpm monorepo and a plugin system / architecture has made all the difference for us at Lowdefy [0].
Additionally we’ve architected a way to build complex web apps using config - not everyone’s cup of tea, but with a small team we are building a LOT of complex apps for customers. We are really happy with how this is scaling and we have all the flexibility we need on project.
The config first approach might be controversial, but have a look at the Lowdefy repo, after a few years of iterations it works well for us.
https://github.com/lowdefy https://github.com/lowdefy
- gervwyk 2y agoIt’s worth adding that each customer app, is setup in its own monorepo which contains the app config and apps specific plugins. With a dependency on the main repo. Thus a updated framework version is easy to roll out to customer apps, while allowing custom components to be used where as needed.
- pixelready 2y agoNeat. Is lowdefy sort of like React Admin (if they were all-in on YAML)?
- gervwyk 2y agoPretty much. But you can do a lot more. For example, we’ve built advance CRMs which share data between 5 companies, many customer portals, order management apps, ticketing systems, and even an MRP like app, as well as many BI apps.
- theogravity 2y agoTo add on as another example, I recently created a monorepo for three npm packages I publish that depend on each other (not in a circular dep way). It uses pnpm + turbo + changesets + syncpack to publish and manage the versions for cross-deps: https://github.com/theogravity/datadog-transports https://github.com/theogravity/datadog-transports