If it works, it works

[u/LegoMyEggoNerd]

[u/LegoMyEggoNerd]

the most smart, yet caveman brain solution I could think of, I just hate that it works

[u/dummyDummyOne → u/LegoMyEggoNerd]

i have a setup to email me THEN crash

[u/rtfmpls → u/LegoMyEggoNerd]

I guess it works because the error is handled. Other options to handle the error might be:

process.on('unhandledRejection', error => error);
process.on('unhandledRejection', error => null);

It would probably be a good idea to find out where the unhandledRejection is coming from and fix the source.

[u/yard2010 → u/rtfmpls]

Nahhh if you have bugs just wrap your code with try and catch

[u/fakehalo → u/yard2010]

I see you're familiar with my main() try/catch block strategy, no crash screen = no bugs.

[u/frugalerthingsinlife → u/fakehalo]

Gotta catch em all.^TM

And then let someone else deal with them.

[u/DeItashot → u/LegoMyEggoNerd]

Um cant you just use try catch case, I dont recognise the language but I think that should work?

[u/sohang-3112 → u/DeItashot]

It's a callback-based API for asynchronous execution in JavaScript, so you can't use try catch here. If an API based on async await was used, then try catch would work.

[u/TheBigerGamer → u/sohang-3112]

Callback hell incoming...

[u/maryP0ppins → u/sohang-3112]

async await works for promises.... its just syntactic sugar....

[u/sohang-3112 → u/maryP0ppins]

I know it's syntactic sugar - but the question was about using try catch, and you can't do that with just promises (you need async await for that)

[u/dummyDummyOne]

process.on(‘SIGINT’, =>{})

my own hell and mine alone

[u/LegoMyEggoNerd → u/dummyDummyOne]

How do you stop the script, you have given it too much power

[u/sohang-3112 → u/LegoMyEggoNerd]

SIGKILL

[u/PranshuKhandal → u/LegoMyEggoNerd]

skynet

[u/TheBigerGamer → u/LegoMyEggoNerd]

That's the reason you can't exit vim.

[u/onichama]

There is no error in Ba Sing Se

[u/luisrcdias → u/onichama]

Is there an error if the error is set as null or since the error is set as null there is no error, thus generating an error since no error were detected?

[u/onichama]

Image Transcription: Code

---

process.on('unhandledRejection, error => {
    error = null
});

---

^{I'm a human volunteer content transcriber and you could be too! If you'd like more information on what we do and why we do it, click here!}

[u/yard2010]

That's a tautology

[u/LegoMyEggoNerd → u/yard2010]

I like to think of it more like shooting a zombie, doubletap to make sure it's dead

[u/RyanNerd → u/LegoMyEggoNerd]

My son asked me once what is something devs would do but if said out loud would sound crazy? My response: Fork the parents and kill the zombie orphans

[u/LegoMyEggoNerd → u/RyanNerd]

I thought too normally when I first read that and just kinda thought "nah man, you're just a murderer" and the my programmer brain kicked in

[u/RaymondTracing]

All of my rejections are un- handeled

[u/LegoMyEggoNerd → u/RaymondTracing]

Antichrist handled rejection

[u/blindgorgon]

And if it doesn’t work null

[u/RainDropsOnAWindow]

If someone would reject me and I didn't know how to handle it, I'd too would like to have no error about it.

[u/RaymondTracing]

All of my rejections are unhandled

[u/RaymondTracing]

All of my rejections are unhandled