Feature request: warnings rather than errors #65
Comments
Vinnl
added a commit
to Vinnl/stylelint-webpack-plugin
that referenced
this issue
Jan 30, 2017
This option allows you to log errors as warnings, preventing Webpack dev server from aborting compilation.
|
I went ahead and created a PR for this: #66. Let me know if that looks OK :) |
|
👍 |
Vinnl
added a commit
to Vinnl/stylelint-webpack-plugin
that referenced
this issue
Feb 1, 2017
This option allows you to log errors as warnings, preventing Webpack dev server from aborting compilation.
|
Hi, very nice feature, I am looking forward to it! 👍 |
Vinnl
added a commit
to Vinnl/stylelint-webpack-plugin
that referenced
this issue
Feb 13, 2017
This option allows you to log errors as warnings, preventing Webpack dev server from aborting compilation.
|
Thanks @Vinnl for getting the work in on this :) @mhlavacka @Zephir77167 and others, if you could try installing |
|
For those who also never installed an NPM package directly from a repo before, you can simply run It appears to work fine for me. I did encounter a strange thing that I reported in the PR #66, but I suppose that's probably a new issue? |
joshwiens
pushed a commit
that referenced
this issue
Mar 31, 2018
Resolves #65. This option allows you to log errors as warnings, preventing webpack-dev-server from aborting compilation. * tests: fix typo in lint-dirty-modules test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when using Webpack Dev Server with hot reloading, not adhering to my stylelist rules results in an error. The dev server then thinks compilation has failed and will not serve the updated styles.
I want to adhere to my linting rules, but perhaps not as strictly when I'm just messing about locally :) Thus, an option like ts-loader's
emitErrorswould be nice, that can set stylelint errors to be emitted as warnings.The text was updated successfully, but these errors were encountered: