[docs] Clarify MUI Base != Base UI (1/2) #46978
Open
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
oliviertassinari
added
docs
oliviertassinari
changed the title
oliviertassinari
force-pushed
the
clearify-mui-base
branch
from
8739568 to
9efb963
Compare
Netlify deploy preview
Bundle size report |
oliviertassinari
force-pushed
the
clearify-mui-base
branch
4 times, most recently
from
bcf5074 to
26c0b30
Compare
oliviertassinari
changed the title
oliviertassinari
force-pushed
the
clearify-mui-base
branch
from
e087c16 to
9f49da7
Compare
oliviertassinari
force-pushed
the
clearify-mui-base
branch
from
9f49da7 to
602bf93
Compare
oliviertassinari
changed the title
mapache-salvaje
changed the title
| # MUI Base - Create React App example in TypeScript | ||
|
|
||
| [MUI Base](https://mui.com/base-ui/) is a library of unstyled React UI components and hooks. | ||
| [MUI Base](https://v6.mui.com/base-ui/getting-started/) is a library of unstyled React UI components and hooks. |
There was a problem hiding this comment.
Might be helpful to add (legacy) to these examples for extra clarity? I don't have a strong opinion so feel free to use or discard.
Suggested change
| [MUI Base](https://v6.mui.com/base-ui/getting-started/) is a library of unstyled React UI components and hooks. | |
| [MUI Base](https://v6.mui.com/base-ui/getting-started/) (legacy) is a library of unstyled React UI components and hooks. |
| export default function App() { | ||
| return ( | ||
| <div className="box"> | ||
| <h1>Base UI + Create React App scaffold (TypeScript)</h1> |
There was a problem hiding this comment.
Looks like some of the titles (and directories) still say "Base UI." Honestly I think we should just remove these examples entirely. We don't want people to use MUI Base so we shouldn't give them boilerplates to start with. As long as MUI Base exists it will continue to confuse some people looking for Base UI.
There was a problem hiding this comment.
Ah yes, let's fix this.
As for use case of those examples, I only see making it easier to report regressions for people migrating from MUI Base to Base UI. It's in the v6.x branch, so it's mostly hidden.
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.
In https://www.reddit.com/r/reactjs/comments/1k1gerj/in_2025_whats_the_goto_reactjs_ui_library/, you can find levels of confusion:
Now, when I see: https://www.npmjs.com/package/@mui/base
or https://mui.com/blog/base-ui-2024-plans/. It feels like we add confusion, we dont have a clear separation between the two; Hence this PR and #46979.
We started the work, e.g. #45060, but it doesn't feel like we ever finished it. I don't know if this PR is enough to call it done, but this feels like we're getting closer.