Comment by koakuma-chan

4 months ago

I used Next.js with mui.com at one point, and after each change in dev mode it took 10s to recompile. I don’t touch anything that has to do with Vercel ever since then.

5 comments

koakuma-chan

theogravity 4 months ago

Next.js doesn't play well with barrel packages (large packages that export everything into the main entrypoint file). It's a known issue (but rarely mentioned when you read about working with Next.js):

https://github.com/vercel/next.js/issues/48748

I've never used MUI, but assuming that MUI is a barrel package, and you do the following:

  import { Component } from "mui";

Next.js ends up compiling the entire package instead of just that component you need. If MUI has their components exported into separate files, an optimization would be:

  import { Component } from "mui/path/to/component";

koakuma-chan 4 months ago
I switched to Astro plus tailwind and never looked back. If you are interested though, imports are a pretty big thing in mui https://mui.com/material-ui/guides/minimizing-bundle-size/.
- aurareturn 4 months ago
  
  To be honest, if you're making a content site such as a marketing site or blog, it really doesn't matter what you use. You can use Next, Astro, Gastby, HTML/CSS etc. Doesn't matter.
  Next.js excels when you have a complex app with interactions, SSR requirements, CSR requirements, backend requirements, etc.
  
  1 reply →

kylehotchkiss 4 months ago

That sounds like a MUI problem, not a next problem. What a clunky UI framework. Next plus tailwind remains lightning fast for me.