[erlich]

> I recently adopted a codebase (and a team)

Are you in charge? How big is the team? Is it a startup? Is the software making money? How important are new features to make money / gain clients?

Usually with a rewrite, you will end up implementing features in both codebases. This can slow you down a lot, kill team morale for those working on the old project, etc.

First, move to a monorepo. Put all the old monolithic stuff in one package, and pull out parts of the app into small clean packages going forwards.

Then use microfrontend architecture. Implement one page/feature/component cleanly using a new framework with a separate build. If you use Webpack, check out the Federation feature.

However, if you want to move to something like Next.js (with the new turboback which is not webpack anymore) then the microfrontend stuff might be more hassle than it's worth, because Next has a more integrated deployment solution too.

[l0rn]

Well I'm not in charge, but I think my input has a high influence in the decision making. The company is a multi billion dollar international multi, so cost is not really the issue here. It's more an organizational problem. Therefore I also don't think moving to a specific framework or a new design pattern will help us by a lot. It's more transforming the current state to _any_ consistent pattern with a certain level of quality. And I'm trying to figure out whether the team would benefit from a radical or iterative approach.