-
Notifications
You must be signed in to change notification settings - Fork 150
Sapper - (node-)SASS - prependData doesn't seem to work #200
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
Comments
Maybe "use" isn't working because, |
I tried that "use" stuff on a svelte project, same result. |
To sum up :
|
Okay, made it work (for the "use" stuff) by removing 'F:' at the start of the file. |
Actually, I don't need to use "process.cwd()" at all because it is run from the project root folder |
Okay... ¯_(ツ)_/¯ |
(prependData was getting "undefined" because I used sass instead of scss as key of "autoPreprocess") |
I spent hours trying to get my setup to work when all I needed to do was to change Why isn't it mentioned anywhere that |
|
@kaisermann hmm, that's weird, because for me it did all the difference 🤔 I am using the |
@NickKaramoff Just to see if I understood it correctly: you were using |
That's exactly what I was doing 😅
Thank you 🙌 |
Describe the bug
When I use prependData for the sass preprocessor in a Sapper project, my sass variables are not recognized. If I import them myself if the <style> tag, it works.
Logs

To Reproduce
https://github.com/Nokorbis/sapper-preprocess-sass-issue
Expected behavior
My sass variables being prepended to my style tags
Stacktraces
Information about your project:
Your browser and the version:
/
Your operating system:
Windows 10
svelte-preprocess
version4.0.6
https://github.com/Nokorbis/sapper-preprocess-sass-issue/blob/master/package.json
Whether your project uses Webpack or Rollup
Rollup
Additional context
I had a similar issue on Svelte, but which was caused by the path format (\ instead of /), here my path is correct :D
Node version: v12.10.0
The text was updated successfully, but these errors were encountered: