-
Notifications
You must be signed in to change notification settings - Fork 921
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
[BUG] Requested content ".css" but built .sass. #3079
Comments
According to - plugins: ['@snowpack/plugin-react-refresh', '@snowpack/plugin-dotenv'],
+ plugins: ['@snowpack/plugin-react-refresh', '@snowpack/plugin-dotenv', '@snowpack/plugin-sass'], If I do this, I’m able to load Let me know if I missed your issue, or if there’s something else that’s causing problems! |
Edit: ah, sorry—I missed the “only variables” part. You’re right that does result in an error. I’m not sure, though, if this is an error on Snowpack’s fault? In Sass, what is an empty file supposed to produce? I believe the intended effect is to |
There is no scenario where I explicitly want that empty file. And that leads to problems with snowpack. |
Ah this is a bug in our I’ll consider this issue a duplicate of #2967 and we can track resolution there. In the meantime, a temporary workaround is to use |
@nojaf I tried your repo, and on the latest version of Snowpack, I’m no longer seeing the issue if I remove the “blink” hack (I had to fix some broken imports to do so, like |
Yes, I can confirm. The problem seems to be resolved. |
Bug Report Quick Checklist
Describe the bug
My snowpack build is failing, there is a problem with react-refresh and sass plugin interfering.
To Reproduce
We can't fix bugs that we can't see for ourselves. Issues often need to be closed if this section is skipped.
npm init snowpack-app --template @snowpack/app-template-react
Variables.sass looks like
Expected behavior
A clear and concise description of what you expected to happen.
Anything else?
A workaround is to add some sass code that will produce css.
The text was updated successfully, but these errors were encountered: