[docs] Clarify Next.js + Tailwind CSS v3 integration requirements #46176
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Netlify deploy previewBundle size report |
ZeeshanTamboli
requested changes
May 19, 2025
docs/data/material/integrations/interoperability/interoperability.md
Outdated
Show resolved
Hide resolved
ZeeshanTamboli
changed the title
ZeeshanTamboli
approved these changes
May 22, 2025
There was a problem hiding this comment.
@chaitanyasharma1011 Looks good. Thanks for the pull request!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes #45019 and updates the Material UI documentation to:
Explicitly state that Next.js 13+ users must manually add id="__next" to their tag when using Tailwind CSS
Differentiate instructions between Next.js App Router (__next) and Pages Router (root) configurations
Add troubleshooting guidance for common style conflict scenarios
Update all code examples to reflect modern Next.js practices
Include version warnings to prevent setup errors
I have followed (at least) the PR section of the contributing guide.