-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnhandledPromiseRejectionWarning, when no files match /**/*.s?(c|a)ss #82
Comments
This might be an upstream issue with stylelint itself, because I don't think there should be an unhandled rejection when a files are not found in the lint function. All this plugin does is call |
That being said if you can reproduce it with a failing test in this repo, that would be awesome :) |
@JaKXz, it's actually quite easy to reproduce. Same problem here. The plugin fails with an error if the context folder contains no stylesheets at all. Admittedly, this may not be relevant for production builds, but it is quite annoying in other scenarios. For example, I've been running running tests cases on some of my application components with the same webpack configuration as for the actual application. After integrating stylelint-webpack-plugin, these test cases are now failing for all components that don't have stylesheets in their folders/subfolders. |
any news on this? having no stylesheet breaks compilation |
+1 It's pretty important in scenarios with reusable |
Closing as stale due to age and inactivity. If there is still interest in this issue, please do submit a pull request. |
The plugin fail when not found stylesheets for lint and break webpack build, this is a problem in some cases when you're starting a project without styles or embed styles in HTML
stylelint-webpack-plugin v0.7.0
webpack v2.5.1
gulp v3.9.1
node v7.7.3
npm v4.5.0
Manjaro GNU/Linux 17.0.1
You can clone my repository and view the error
The text was updated successfully, but these errors were encountered: