305 karma · joined May 5, 2021
It’s not so bad, working with just tsc can be a little more cumbersome as you have to running it multiple times to get esm and common js and it’s slower than some alternatives. I see it more akin to using a makefile than an anti pattern.
https://web.archive.org/web/20220525180921/https://www.wired...
We just wanted to use vercel for hosting and previews but after the quote we ended up going with aws amplify.
Been waiting for this basic feature of the weather app.
- Cypress: https://www.cypress.io
- Playwright aws lambda: https://github.com/PauloGoncalvesBH/running-playwright-on-aw...
- Checkly: https://www.checklyhq.com
For a little more on microfrontend this is a good description on the idea: https://micro-frontends.org/
As for the debate, we have a monorepo/microfrontend now and it is quite a bit of work to maintain it and certain parts of it are starting to show the lack of resources put into it. We can't deploy easily individually, our tests are very slow, and crucially our organization thinks there is significant risk in a deployment so they have set a very complicated and long QA process for us to get deployments to production.
Realistically I think it is an organizational issue and I've been leaning towards multirepo due to the restricted resources and it would be easier to put some of this work on the teams making the individual parts themselves.