-
-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Since sass-loader 12.0.0 the @debug
doesn't work with Sass >= 1.43.4
#1065
Comments
That is breaking change in https://github.com/webpack-contrib/sass-loader/releases/tag/v13.0.0, looks like we miss it in changelog, now we use webpack API to emit logs, if you need debug please set https://webpack.js.org/configuration/other-options/#level https://github.com/webpack-contrib/sass-loader/blob/master/src/utils.js#L171 |
Thank you for Tip. The webpack level option has no effect: infrastructureLogging: {
level: 'log',
debug: ['sass-loader'],
}, 💡 I found how to enable stats: {
loggingDebug: ['sass-loader'],
}
The output of Webpack is too "informative":
Expected pure Debug output w/o a path to file at each line, so is the output with
|
@webdiscus I think wen can remove unnecessary lines |
It would be clean to only show the Debug output. My suggestion:
For example:
The |
Yes, can you send a PR, we have |
Bug report
The
@debug
output in SCSS/SASS works only with:Sass <= 1.52.3
+JS API
Sass <= 1.52.3
+sass-loader <= 11.1.1
Sass 1.43.3
+sass-loader 13.0.0
(lastest)Used
sass
: 1.43.3 - 1.52.3sass-loader
: 11.1.1 - 13.0.0How Do We Reproduce?
Create 3 files in a directory:
package.json
style.scss
webpack.config.js
Install npm modules:
Show result in console output:
Expected
the output in console:Debug: *** Color: red
Received
- nothing.How to view the
@debug
outputChange the version of sass-loader from
^12.0.0
(or^13.0.0
) to11.1.1
in package.json and update npm module:Show result in console output:
Now you should see the output in console:
Debug: *** Color: red
.Who broke compatibility:
Sass
since1.43.4
orsass-loader
since12.0.0
?The text was updated successfully, but these errors were encountered: