While this is true to some extend, the alternative options (Module Federation in Vite or esbuild) are really weak at the moment. For instance, for Vite you have a couple of plugins - one which is really new and totally buggy, one which is actually made for Native Federation and returns an incompatible result, and one which only returns esm + Module Federation v1. The latter you cannot use as remote from Webpack or rspack - you can only use as a host (or make Vite - Vite doable). Let's not talk about the esbuild one (this one is even more alpha / buggy - not at all usable for production). So overall I don't think the statement is wrong. If you do Module Federation you most likely do rspack or Webpack (which are both quite the same - just a different engine).
Module Federation isn't bound to webpack anymore
While this is true to some extend, the alternative options (Module Federation in Vite or esbuild) are really weak at the moment. For instance, for Vite you have a couple of plugins - one which is really new and totally buggy, one which is actually made for Native Federation and returns an incompatible result, and one which only returns esm + Module Federation v1. The latter you cannot use as remote from Webpack or rspack - you can only use as a host (or make Vite - Vite doable). Let's not talk about the esbuild one (this one is even more alpha / buggy - not at all usable for production).
So overall I don't think the statement is wrong. If you do Module Federation you most likely do rspack or Webpack (which are both quite the same - just a different engine).
@@FlorianRappl That makes sense. I don't have much experience outside of that ecosystem (as you correctly guessed 😅)
Vite(rolldown) will offically support Module Federation 2.0 next year.