Make `@mui/icons-material` independent from `@mui/material` in the future?
Open
@mnajdova is already working on this.
Since Dec 19, 2022.
scope: icons
type: new feature
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary 💡
Are there any plan to make @mui/icons-material that not depends on @mui/material in the future?
I'm working on a side project that use @mui/joy. The auto import vscode intellisense sometime import components from @mui/material instead of @mui/joy.
I can't remove @mui/material because @mui/icon-material rely on that package.
Examples 🌈
No response
Motivation 🔦
Better DX and smaller bundle size.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.