-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade next #218
Upgrade next #218
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/oacore/dashboard/2i9fjcko1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will review the rest later, sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, remove breaking changes with :root
selector replacing it with html
. Apart from that it looks good to me.
Why are you obliged to rename all the CSS file with .module
suffix?
How the design
library is supported now?
It's how nextjs distinguish postcss files from regular ones. I don't like it but it is what it is.
It's guaranteed that design css files will be imported before any local ones. |
fa9f6b7
to
b80ae14
Compare
any updates? |
@Sebastp Not yet. We are still waiting for fixing this bug vercel/next.js#11946 |
@viktor-yakubiv So the bug regarding CSS order has been just fixed. We can use the canary version and merge or wait for version 9.3.6. What do you prefer? |
If waiting drains you because of unclosed task, let's merge. Otherwise let's wait. |
🎉 |
In the first commit, I removed the deprecated getInitialProps method and did appropriate changes. It was pretty straightforward. Nonetheless, the second commit is more interesting.
I decided to switch to the new postcss default support in NextJS. There were some breaking changes. I had to rename all
css
files tomodule.css
and move variables to classes.:root
selector is not supported. There is a bug reported so when it gets fixed we can move them back. (Maybe it is even better as is now. I find it as a correct solution).The reason why I decided to switch it was mainly because hot reaload didn't work very well and also we had some problems with css from design repo. This has been all fixed now.
We will need to postpone this. CSS in dev mode is imported incorrectly. See vercel/next.js#10148