-
Notifications
You must be signed in to change notification settings - Fork 75
Unhandled promise rejection #29
Comments
I already fixed it, it cause by wrong webpack configuration, thanks! |
@Khachatour So it's not on our side? |
@oliviertassinari 100% no, But can you specify in error handling that it is from webpack. It took me a day to resolve that :) . For example to say that it comes from webpack configs ? |
Do you have a reproduction example so I can have a look at? |
I'm running into this as well. @Khachatour could you post the solution? |
@oliviertassinari Now I can't reproduce it, I am sure it came form my side. But I will try to reproduce that as soon as possible. |
No rush, let us know if you find something :). |
@oliviertassinari I've reproduced the error, It comes when in your webpack dev configs you declare the usage of service worker plugin and then in plugins section declare the usage of plugin with this code below: |
The issue I was having was definitely an issue with my entry file not being found. I had a typo. I think this is just an issue of better error handing/reporting. |
@anthonator I definitely agree with you. The error shown is not giving a clue what was wrong :) |
When I am using this plugin, I keep getting
(node:29634) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): undefined
Can someone suggest an answer ?
The text was updated successfully, but these errors were encountered: