-
Notifications
You must be signed in to change notification settings - Fork 15
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
Doesn't work with latest styled-jsx #8
Comments
Unfortunately I am not working on this kind of stuff (web) anymore so i am afraid i won't be able to help much, at least not until I will be back on a web project. Sorry |
Really too bad, since I was loving using scss with Next.js. Since the security update, I have to upgrade 2.4.1, and can't figure out how to fix the scss loading. Hope that someone is able to come along and adapt the solution. |
Logged my fix here @Yuripetusko |
Actually, getting the same error again. Unsure what the issue is. |
@Yuripetusko, have you found any solution? |
@tgoldenberg yes we did, not sure what exactly helped us exactly. This is content of next.config.js
This is content of babelrc:
And here's postcss.config.js
And we import files like so:
or sometimes
|
|
@Yuripetusko were you able to get |
Hello, guys! @Yuripetusko @tgoldenberg noticed that you came up with a solution how to make work |
@dvakatsiienko |
Hi,
It doesn't seems to work with latest code in styled-jsx master branch which allows for external files
vercel/styled-jsx@02e203f
i guess they probably do some kind of babel transpiling of files on the fly of their own? this is kind of string I get when trying to import file with latest styled-jsx:
![screenshot 2017-05-24 01 07 38](https://cloud.githubusercontent.com/assets/666169/26381538/7691fe1c-401d-11e7-9ea5-6c747a04c643.png)
The text was updated successfully, but these errors were encountered: