-
Notifications
You must be signed in to change notification settings - Fork 26.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
Fixed bug where styled-jsx examples don't work because of a wrong plugin #23414
Conversation
@@ -13,8 +13,7 @@ | |||
"next": "^10.0.0", | |||
"sass": "^1.32.4", | |||
"react": "17.0.1", | |||
"react-dom": "17.0.1", | |||
"styled-jsx-plugin-sass": "^1.0.0" |
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.
In fact, we still need to have @styled-jsx/plugin-sass
in devDependencies
and sass
should be in devDependencies
.
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.
Actually, we don't need @styled-jsx/plugin-sass
because styled-jsx
is shipped with NextJS
and it works out of the box.
And yeah, you are right. I will put sass
in dev dependencies now.
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.
Yes styled-jsx
is there out of the box in next
but it is not the case for this plugin, to use it, you need to install it on your own.
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.
Actually, you are right. My bad. I added it now.
moved `sass` in devDependencies
added `sass` in devDependencies
added `@styled-jsx/plugin-sass` to devDependencies
added `@styled-jsx/plugin-sass` to devDependencies
…gin (vercel#23414) ## Bug Fixes vercel#23293. Problem was that `styled-jsx-plugin-sass` was used instead of `@styled-jsx/plugin-sass` so it didn't work. You can refer to the issue that is linked for more info.
Bug
Fixes #23293.
Problem was that
styled-jsx-plugin-sass
was used instead of@styled-jsx/plugin-sass
so it didn't work.You can refer to the issue that is linked for more info.