[core] Update monorepo

[oliviertassinari]

Propagate mui/material-ui#41901

[oliviertassinari]

It fails because @mui/docs wasn't released with a version that is compatible with @mui/monorepo yet.

It works for Base UI mui/base-ui#333 and MUI X mui/mui-x#12861 because we don't use @mui/docs there yet.

I still struggle to connect the dots to why npm dependency > git dependency for docs infra.

• dependencies: it seems that pnpm can solve this, by not using the workspace syntax, and by not publishing to npm (to avoid silent bugs).
• build step: not needed, we can configure Next.js in the dependent, the same way as in the source
• code isolation: having one or multiple units of code doesn't seem to make a difference. What seems to matter is no leaking abstractions. e.g. micro-services aren't solving the problem.
• else?

[Janpot]

I still struggle to connect the dots to why npm dependency > git dependency for docs infra.

The problems you encounter are caused by moving @mui/docs to the published variant before fully removing the monorepo dependency. Now we ended up with two code dependencies that have some shared assumptions about which version is used, but which are imported through two different release cycles.

My initial preference was to keep aliasing it from the monorepo dependency until we could fully replace, but the team is eager to move forward with publishing.

Similar problems will appear when introducing a different release process for internal and external packages. Unfortunately so far I haven't been able to convince the team about this yet. Will keep trying to find the right argument.

In general it's simple: a hybrid of monorepo+aliasing and published packages will cause more problems than either of those on their own. I am going to be clear about the following, if we're moving forward with published npm packages we're going to have a worse system until:

1. we remove the monorepo dependency completely
2. we adopt the same release cycle for internal packages and external ones

I also agree that we should have tried a git dependency first (still the format of npm packages, but unpublished), at least as a stopgap solution.

[oliviertassinari]

Something is off with the latest version mui/mui-x#12861 (comment)

[Janpot]

Revoking my review, I didn't look at the CI

[Janpot]

monorepo is up to date now, so I just kept the change to the config.
Added a few more comments around @mui/docs as well

[oliviertassinari]

It looks great, thanks