You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is an error during a custom transform, the stream stops and prints an error properly but the exit code is wrong. The exit code is 0 but I expect it to be 1.
For example, if using require('gulp-bundle-assets').transformHelper.less() and there is a compile error inside a .less file, the stream will stop and print the error, but the node process will simply exit with the wrong code.
One possible solution is to simply process.exit(1) inside the stream-files.handleTransformError, however the ideal solution is to bubble up the error to gulp that the stream failed.
The text was updated successfully, but these errors were encountered:
When there is an error during a custom transform, the stream stops and prints an error properly but the exit code is wrong. The exit code is
0
but I expect it to be1
.For example, if using
require('gulp-bundle-assets').transformHelper.less()
and there is a compile error inside a.less
file, the stream will stop and print the error, but the node process will simply exit with the wrong code.One possible solution is to simply
process.exit(1)
inside thestream-files.handleTransformError
, however the ideal solution is to bubble up the error togulp
that the stream failed.The text was updated successfully, but these errors were encountered: