@marick Yes, #monorepos have advantages, but are not without downsides:
* tags apply to the whole repo, which is awkward for versioning and releasing independent artefacts
* carbon/money costs can be relatively high when "safe" changes, e.g. to docs or website, trigger expensive CI checks
* all or nothing in terms of private/public,
access control (e.g. limiting write access to certain subcomponents), issue management, fork maintenance, and continuous deployment
Question for people using #MicroFrontends and #Monorepos: What do your #integration tests look like?
The #Google model of monorepos always builds everything at HEAD, but doing so would not catch version skew issues that come with independent deployments. That implies that your integration tests _cannot_ just build and run everything at HEAD, you actually have to deploy each change individually to a staging environment and alert on failures.
That feels like a much more complex setup than I'm used to seeing for integration tests. Do people actually do this or is version skew a giant blind spot for microfrontend testing?
#microfrontends #monorepos #integration #google
Just learned about https://www.pantsbuild.org anyone using it? A build engine on top of Rust and Tokio seems like it could be promising
We've created an official feed for Rush Stack, a collection of open source build tools for large scale #TypeScript #monorepos! If you use Mastodon and #NodeJS tooling, follow us to show your interest!
#typescript #monorepos #nodejs
🎉 We've created an official feed for RushJS, the build orchestrator for large scale #TypeScript #monorepos! If you use Mastodon and #NodeJS tooling, follow us to show your interest!
#nodejs #monorepos #typescript
Does anyone have a ELI5 for the trend towards #monorepos now? Not even 4 years ago we were moving AWAY from monolithic structures, now we're moving back??