[core] Restrict import path with ESLint

[oliviertassinari]

A step to fix https://github.com/mui/mui-toolpad/pull/3417/files#r1572992179 at the root.

https://eslint.org/docs/latest/rules/no-restricted-imports

[mui-bot]

Netlify deploy preview

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

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 7a8175d

[oliviertassinari]

We should rename this one to @mui/internal-docs. @mui/docs was exporting public packages, it's not the case anymore.

[Janpot]

I suspect that our move to the exports field in package json will make this rule largely irrelevant. When those deep imports simply don't exist anymore in the world of typescript. And consequently vscode won't suggest it anymore neither in its auto-import.

[oliviertassinari]

Oh yes, this will be great once we have package.json exports 🙌. We will need to fix the violations we have in the codebase to get there. I think rule will help us get there, e.g. If MUI X relies on private modules, best to caught it before we break them 😁

[Janpot]

Yes, we decided to test more integrations before merging and we're running into a few issues. e.g. I suspect this one will be a blocker vercel/next.js#64796.