[examples] Align dependency versions with the rest of the repo#4436
[examples] Align dependency versions with the rest of the repo#4436LukasTy merged 9 commits intomui:masterfrom
Conversation
commit: |
Bundle size report
Check out the code infra dashboard for more information about this PR. |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Doesn't look relevant, actually; it's a disturbance. 🙈
cc @mj12albert
| tailwindcss(), | ||
| ], | ||
| resolve: { | ||
| tsconfigPaths: true, |
There was a problem hiding this comment.
After vite bump it was warning that vite-tsconfig-paths is no longer necessary
| }), | ||
|
|
||
| shellComponent: RootDocument, | ||
| notFoundComponent: () => <p>Page not found</p>, |
There was a problem hiding this comment.
Was complaining that this route doesn't exist
| return ( | ||
| <html lang="en"> | ||
| // Use suppressHydrationWarning to avoid https://github.com/facebook/react/issues/24430 | ||
| <html lang="en" suppressHydrationWarning> |
There was a problem hiding this comment.
Very noisy console after updates when opening started application on a browser with extensions (no warning in incognito window).
Claude Opus 4.6 reviewOverallClean, well-scoped maintenance PR. Most changes are correct and straightforward. A few items worth addressing before merge. Issues1. Stale comment in
|
Good question. I believe in core the idea was to define those with very wide version https://github.com/mui/material-ui/blob/master/examples/material-ui-express-ssr/package.json#L9. |
|
@Janpot, do you see any advantages of this approach? If someone were to use these examples to start a new project, they would likely want more specific dependency versions anyway. |
That's a less maintenance approach, but one that I fear could introduce the most unexpected issues without us noticing. 🙈 |
|
Either way (with |
I think the idea is that we don't want to spend a lot of time on maintaining these examples and keeping their versions up-to-date. And so this method was introduced to prevent end-users from accidentally outdated and potentially insecure versions. A potential compromise could also be to "pin" them to their major (e.g. |
|
I want to merge this to fix the broken examples. |
brijeshb42
left a comment
There was a problem hiding this comment.
LGTM in the short term
Follow-up on #4400.
Tip
Would it make more sense to not ignore
examples/folder in renovate so that these don't go out of sync?cc @mui/infra
Summary
tanstack-start-tailwind-cssandvite-cssexamples to match repo-wide versions (TanStack Router/Start, Tailwind CSS, ESLint, TypeScript, lucide-react, etc.)pnpm-lock.yamlfrom thetanstack-start-tailwind-cssexample — the root lockfile is sufficientvite-tsconfig-pathsplugin with Vite's built-inresolve.tsconfigPathsoption and remove the now-unused dependencynotFoundComponentto the TanStack Start root route to suppress the missing route warningsuppressHydrationWarningon the<html>element to avoid noisy console warnings caused by browser extensions (facebook/react#24430)