More descriptive errors about sasslint-webpack-plugin

[ianks]

I have the same issue. Sometimes there is no output given about the errors which makes the plugin basically useless...

[mikeerickson]

@ianks would you mind sharing some example(s) where you are seeing silent errors? Will see what can be done to provide more details.

Thx in advance :)

[mikeerickson]

@bharley as requested from @ianks, if you could please supply some example(s) it would help track down what you are experiencing.

Perhaps a sample .sass file which contains errors which are skipped

[bharley]

@mikeerickson: In my case, the errors aren't skipped. They just output to the browser without any description. If I switch to the command-line window running the node application, I can scroll up and see the exact error details (line number, which rule broke, etc), but this isn't a pleasant workflow.

[mikeerickson]

@bharley thanks for the input. Would you mind sharing what you expect to see different?

Just trying to understand what you are asking to make it a better workflow fo you? Seeing as the plugin is designed for CLI output, not sure what you want to see differently.

Surely trying to help, just not quite sure what you are looking for.

Thanks

• me

[bharley]

@mikeerickson: I'm not entirely sure of the technical details, so excuse me as I try to make sense of this:

webpack-hot-middleware has an overlay that it uses to display errors on top of the application in the browser (mildly documented on their README). When I make a code change that will throw an eslint error, the overlay will show this after the build is finished and sent to the browser (as illustrated in the above screen shot of my application).

This plugin will also show up in the overlay (as seen in the screenshot in my original post), but it includes much less details than the eslint error above it—only showing the file where the error occurred instead of including line numbers or rule issues.

[mikeerickson]

@bharley Ah, ok. I was not making the connection you were talking about regarding webpack-hot-middleware My apologies for the confusion, now I understand what you are saying.

I will have a look at this :-)

[bharley]

@mikeerickson: I probably should have opened with that, so my bad. Thanks!

[mikeerickson]

@bharley No worries, sometimes hard to get in sync with what someone is thinking, especially via text communication :-) I make this same mistake all the time. It's all good!!

[jackmarketon]

We do not use webpack-hot-middleware internally so I will not be able to implementing a fix for this @bharley. We use it entirely as a CLI tool, you are welcome to submit a PR for improvements for integrating with webpack-hot-middleware.