UnhandledPromiseRejectionWarning
Opened this issue · 3 comments
Hi there,
When running my trusty gulp-livingcss implementation today, I received an error:
(node:16855) UnhandledPromiseRejectionWarning
(node:16855) 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:16855) [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.
When googling the error, it seems other repos have experienced this as well. I haven't been able to figure out how to resolve it though, unfortunately.
Interesting. I'll check all my promises and see where I might be letting an error go unhandled. Thanks for letting me know.
@straker This may actually be user error.
As I was trying to debug, I changed this in index.js
Although the UnhandledProiseRejectionWarning persisted, I also got an error message about a section already existing. Once I cleaned that up it ran successfully.
If you comment out that line 133 return Promise.reject(e) does the UnhandledPromiseRejectionWarning go away?