-
Notifications
You must be signed in to change notification settings - Fork 27.1k
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
Issues with libraries #119
Comments
@nsantini Any luck integrating Material-UI? I am facing a |
Haven't been able to make it work with material-ui, I have been able to make it work with react-bootstrap though. |
I got slightly further with react-toolbox, but without webpack to load the SASS, it won't work. One idea would be to convert all the SASS into CSS and then insert them into the page via |
Ran into this issue as well with material-ui... confused as to what the source might be though |
Has anybody succeeded with any of the existing UI toolkit using Next.js? |
FYI, I have just reported an issue, which seems to reveal the root cause of the issue we encounter in most of the UI toolkits: #204. Please, have a look and maybe you will have a good guess of how this can be fixed. |
I have succeeded in hacking Next.js to work with React-MD in #221, and it can be also hacked to work with Material-UI, but I have no idea on how to solve the hacks as I have a very little experience with NodeJS world. Thus, I put all my findings into the comments to the PR. I hope somebody will make sense out of my proof of concept and implement a proper PR. |
@nsantini how did you manage to get react-bootstrap working? |
@jonaswindey for me, it just worked... what sees to be your issue? |
Nevermind, apparently you have to manually load the bootstrap from a CDN |
@jonaswindey did you add the css from react-bootstrap? |
@jonaswindey you got it, boostrap is different than matarial-ui in that css is separate and uses className to apply styles, material-ui uses inline styling applied to the components |
In general I recommend you load the CSS through The reason for this is obvious: why ship more CSS than is actually needed? eg: why ship an entire stylesheet of tools, inputs, textareas, radio buttons if you're only going to use a dropdown menu in a certain page? For an example of this mindset check out http://jxnblk.com/rebass/ by @jxnblk
|
That said, our goal is to make the framework work with everything that works with React. For that we're exposing the webpack / babel config you can extend. The method we're going with is: #222 |
Custom webpack config is now supported: https://github.com/zeit/next.js#customizing-webpack-config |
Closing in favor of custom webpack config. If your issue is not solved. Please do re-open this one. Or create a new one 👍 |
@timneutkens I am not sure what to do with my custom webpack config to fix this issue. #232 |
@cyrus-za do you manage to solve the issue with injectTapEventPlugin? |
This helps |
Thanks @vozni4iy that helps |
+1 |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Im using material-ui to create my components, every time I click on something like a menu or a radio button that is supposed to change the view somehow I get:
Uncaught Error: addComponentAsRefTo(...): Only a ReactOwner can have refs.
I wonder if this is a conflict with this particular library or if other react libraries suffer the same with nextjs.
The text was updated successfully, but these errors were encountered: