Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug? Unhandled Promise Rejection
See original GitHub issueStarted getting this error a couple of days ago. Latest versions of Brackets & CSS Comb, running High Sierra & Node v8.9.1. Reinstalled CSS Comb but didn’t fix the error.
(node:67582) [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.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:13 (2 by maintainers)
Top Results From Across the Web
What is an unhandled promise rejection? - Stack Overflow
A rejected promise is like an exception that bubbles up towards the application entry point and causes the root error handler to produce...
Read more >Tracking Unhandled Promise Rejections - TrackJS
When a promise is rejected, it looks for a rejection handler. If it finds one, like in the example above, it calls the...
Read more >[Bug]: Unhandled promise rejection in case of binded function ...
On node.js 15+ unhandled promise rejections exit the process immediately by default, so this error ends the puppeteer script entirely.
Read more >Safari MacOS – console error 'unhandled promise rejection'…
Hello I'm getting some error in the safari console like: “unhandled promise rejection error: error response received for message…
Read more >[BUG REPORT][iOS] ImagePicker throwing an "Unhandled ...
I was trying to do something last night by saving the value returned from the image picker into a screen variable, and was...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
To the best of my knowledge, this is fixed as of 4.3.0. Can’t actually check because I moved my working directory and generated a fresh prefs JSON file.
I encountered this very problem after i upgraded my sublime editor to version 3.1.1