Replies: 3 comments
-
|
Same for me, with 2 different libs: |
Beta Was this translation helpful? Give feedback.
-
|
It's not a bug, turbopack does not support https://nextjs.org/docs/architecture/turbopack#unsupported-features
|
Beta Was this translation helpful? Give feedback.
-
|
Ran into this issue myself after upgrading to nextjs 16.0.1, which defaults to using turbopack. I understand the reason it no longer works, but is there a new recommended approach to pull scss variables into the javascript, or is it just no longer possible? Current sass documentation only shows the method that no longer works. |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Link to the code that reproduces this issue
https://github.com/szaleq/next-js-15-sass-issue-repro
To Reproduce
yarn create next-app@latestyarn add sassCurrent vs. Expected behavior
Expected behavior: Sass variables defined using
:export {}are correctly imported in JS using the following code:Current behavior: fails with the following error:
Everything works as expected with Next.js 13 and 14 (just following the steps described above but adding version to
create-next-app, likeyarn create next-app@^13) but fails with next@15.Provide environment information
Which area(s) are affected? (Select all that apply)
Not sure, Module Resolution
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions