-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Why do we need @material/core ? #335
Comments
I get your point.
Until a new version of notistack is released which is independent of MUI, you'll have to have it installed. This won't impact your bundle size significantly if you've enabled tree shaking. |
Although I'm interested to know how (if at all) you're customising styling of the snackbars @gothraven |
@iamhosseindhv I'm actually using the provider |
Such a boomer. Was really excited for trying Notistack until I got this error. I guess I'll stick to react-toastify for now. |
Just checked the logs and this is still a problem after 2 years and mentioned a couple of times of the past few years 😄 yarn add notistack@alpha works, but isn't documented correctly. |
Hey @Yard-Daniel . The alpha version is a WIP which doesn't have dependency on MUI and will be published as the stable release. |
I just installed notistack in a CRA and when i did
yarn start
I have got this errorAnd I started asking myself why do I need @material-ui ? I don't want to use it! and why the docs doesn't even mention this ?!
Expected Behavior
I expect this to work without me needing to install @material-ui
Your Environment
The text was updated successfully, but these errors were encountered: