Unhandled Promise Rejections

[elboletaire]

Your promised code does not have a catch, this generates a warning, but it also hides the real errors. In my case, I've been trying to build a set of less files where one file could not be found.

The error shown is this:

(node:732) UnhandledPromiseRejectionWarning
(node:732) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:732) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Here are two issues:

• you should grab the catch in order to show any possible error (like in my case, where I've ended up removing gulp-less-sourcemap and just using gulp-less instead because it shows the errors, thanks to the implemented catch).
• as said in the warning, unhandled promise rejections are being deprecated. So in the future, this will terminate with a non-sero exit (which would be better, because right now this error passes throughout my build process successfully, when it should not).

[radist2s]

Thank you for report. What is interesting, Promise is has catch. And I can't handle with this error. Anyway, the module is abandoned, and I marked it as deprecated. Now I see no reason to not use gulp-less.

[elboletaire]

Thanks @radist2s, I didn't even know that gulp-less added sourcemaps. So I'll go that way.

Thanks again!