-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Create Next.js integration package #38089
Labels
duplicate
This issue or pull request already exists
Comments
siriwatknp
added
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
RFC
Request For Comments
enhancement
This is not a bug, nor a new feature
and removed
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
labels
Jul 21, 2023
cc @mui/core |
Related #30858 |
Same as #34575? |
Agree, I am closing this. |
2 tasks
oliviertassinari
removed
RFC
Request For Comments
enhancement
This is not a bug, nor a new feature
labels
Dec 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the problem? 🤔
What are the requirements? ❓
No response
What are our options? 💡
Proposed solution 🟢
Create a new package under MUI repository. The package offers 2 APIs to work with page router and App router (should not deviate much from what we already have in the example repositories).
We could name the folder
mui-nextjs
ormui-nextjs-integration
.The package name can be
@mui/nextjs
or@mui/nextjs-integration
.Resources and benchmarks 🔗
https://docs.tss-react.dev/ssr/next.js
The text was updated successfully, but these errors were encountered: