You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using webpack 4.10.2 with sass-loader 6.0.7. After updating my include for the new version to have /sass, my build now fails with:
ERROR in Module build failed:
License: none (public domain)
^
Invalid CSS after "...blic domain) */": expected 1 selector or at-rule, was "*/ {}"
in (myBuildPath)/node_modules/reset-css/sass/_reset.sass (line 3, column 36)
I didn't inspect the file terribly closely, but I believe the only real difference between version 3 and version 4 is that the extension changed. If I manually switch the extension back to .scss, the build succeeds.
(The comment closing characters being the important difference). Manually altering the .sass file to have this comment style ends up breaking the build further down the file (at time, mark, audio, video {), which leads me to believe the extension switch may have been by mistake.
Was the change from .scss to .sass intentional? And if so, is there anything else I should try here?
The text was updated successfully, but these errors were encountered:
I'm using webpack 4.10.2 with sass-loader 6.0.7. After updating my include for the new version to have
/sass
, my build now fails with:I didn't inspect the file terribly closely, but I believe the only real difference between version 3 and version 4 is that the extension changed. If I manually switch the extension back to
.scss
, the build succeeds.Lastly, plugging the file into https://www.sassmeister.com/ switches the comment to look like this:
but then upon compile, it switches to
(The comment closing characters being the important difference). Manually altering the
.sass
file to have this comment style ends up breaking the build further down the file (attime, mark, audio, video {
), which leads me to believe the extension switch may have been by mistake.Was the change from
.scss
to.sass
intentional? And if so, is there anything else I should try here?The text was updated successfully, but these errors were encountered: