Open wujekbogdan opened 7 years ago
Hello! I've never tested it with Scss. It should at least find scss errors and give them a 0 priority.
Do you have the "XX errors" header when enabling the plugin?
The best you can do in this situation is providing a test-case (think of it as a minimal repro) in the integration-test file.
It would help a great deal moving forward with your issue :smile:
Do you have the "XX errors" header when enabling the plugin?
Nope. There's no difference in the output at all.
The best you can do in this situation is providing a test-case
I'll try to prepare something. I'm not sure If I'm able to create an integration test... because I'm not sure what output am I expecting to see, but I'll create at least a repo that will help you to reproduce the issue (to make you see the same what I can see in my console). Does it work for you?
A minimal repro would be great (ie, the minimal set of plugins, does it happen without the extract-text-plugin, etc.)
Might be related to #38
Any updates on supporting a cleaner scss
error?
@weilinzung Not that I am aware of, but I would be happy to review a PR :)
@christophehurpeau
@christophehurpeau #90 when could we have the new release?
I know that the title of this report sounds very generic, but this is exactly what happens - I can see no difference in the console output when the
friendly-errors-webpack-plugin
is enabled.This is the output when the plugin is disabled:
And this is the output when the plugin is enabled:
So, as you can see, they look the same. Is it a bug, or is it my misunderstanding of what the plugin is supposed to do? Is it supposed to work with css/scss or just with JS?
Here's my webpack config:
And this is my
package.json
Is there anything else I can provide you with?