[docs] Fix Next.js v13.5.1 <title> SEO regression

[oliviertassinari]

Fix the SEO regression introduced from #40423

Use the same fix as in mui/mui-x#11182.

Preview: https://deploy-preview-40302--material-ui.netlify.app/

[mui-bot]

Netlify deploy preview

https://deploy-preview-40302--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 1c61afe

[oliviertassinari]

Rebased on HEAD

[oliviertassinari]

Problem looks solved:

[oliviertassinari]

It looks like Netlify builds are failing 40% of the time on HEAD since we merged this PR. https://app.netlify.com/sites/material-ui/deploys?filter=master labels the origin pretty clearly to be here.

I think we need to either revert #40302 and #40423 or fix it.

Is this what #41111 tries to do? Unfortunately, it's not helping. Strange as this doesn't happen on MUI X.

[michaldudak]

@Janpot found a failing build prior to this change: https://app.netlify.com/sites/material-ui/deploys/65c3bb5ccb8fee00087cbe74

We're trying different approaches to handle this and you can see our attempts among PRs.

[Janpot]

@Janpot found a failing build prior to this change: https://app.netlify.com/sites/material-ui/deploys/65c3bb5ccb8fee00087cbe74

And this is what led me to believe it could've been connected to the next.config.mjs change that was merged earlier that day. Sadly reverting back to next.config.js did produce a failing build as well.

The change right before that is the Next.js update. We could indeed try reverting to 13.4.19.

update: nope, reverting Next.js produced a failing build

Otherwise I guess we could start bissecting and open a PR that reverts to a specific commit, and go backwards until we can't reproduce anymore. Or until we can safely state it's a platform issue on latest netlify images.

04b3bf8b4527b843f2f2bf52278f763d6f80ec41: ✅
3cd55d3c9245348940e4235713eb50c8d09d4a02: ✅
bcb6ef282642490942d5ffab3e324c095c06e82f: ✅

I'm stopping this effort unless #41132 turns out not to fix it

[Janpot]

@oliviertassinari Any idea what caused us to add this --threads=3? It doesn't seem to translate anywhere in the output: 'export' setup.

edit: got it, netlify resource issues it seems

edit 2: checked the next.js source code and it seems that option is now coming from experimental.cpus.