-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
prependData does import to other partials #58837
Comments
Have you tried appending E.g
|
@EliHood yeah it still has the same error/behaviour. I feel like this is something to do with the |
Currently on Next 14.1.0. I faced the same issue, seems to be related to the --turbo flag on the next dev. When I remove it, my variables.scss file is correctly set so it might just be that prependData isn't working with turbo dev for the moment. |
Had a look at this but it seems there's a misconception about what More info here: https://webpack.js.org/loaders/sass-loader/#additionaldata @KenTay198 your case is different, I just opened a PR for the issue you ran into: #62397 |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/PaulSinghDev/prepend-data-nextjs-issue
To Reproduce
sassOptions
_colors.scss
@use
the new partial in the main SCSS module for the componentCurrent vs. Expected behavior
Expected: The app will compile and the SCSS will render as normal with the color variable added in
Actual: Get an undefined variable error
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
Not sure
Additional context
No response
The text was updated successfully, but these errors were encountered: