-
Notifications
You must be signed in to change notification settings - Fork 28
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
Error not catched in css-parse #1
Comments
@tkjaergaard Hi. I do not know well how to receive the error css-parse can throw. https://github.com/reworkcss/css-parse#errors I do think I think we can deal with such a situation to add code similar to the following, but do you intent not match the thing you are you said?
|
That could be a valid solution to overcome this issue? |
Since try if the problem can be solved, why not tell me the CSS code that has a problem css-parse such that an error? |
Sorry mate, but what you just wrote doesn't make any sense to me? :) |
Hi, i just encountered a similar issue. but the error message in the terminal give me the line where it crash. In fact the parser crash in my case, with a missing ';' at the end of the class declaration.this can be considered as correct in a css validation normaly.
|
When css-parse encounters an error it throws a new Error object which is not caught in index,js:125
This causes the watch workflow in Gulp to crash due to an unhandled error and is also resulting the .on('error') event not to be triggered.
Please look at some options to catch the error and throw a PluginError instead?
The text was updated successfully, but these errors were encountered: