FUCKING PROMISE WONT FUCKING RESOLVE SO MY FUCKING CODE KEEPS FUCKING RETURNING A FUCKING NULL VALUE FOR FUCKING FUCKS SAKE IT REALLY SHOULDNT BE THIS FUCKING HARD TO RESOLVE A FUCKING PROMISE WITHOUT FUCKING CRASHING MY GODDAMN SERVER

98% sure you did it wrong.

If it's not ever timing out, use an abort controller to collect it

https://developer.mozilla.org/en-US...

If it's returning a null value, that's on your service.

Good good, let the hate flow

@bagfox there are better websites for pretending your better than everyone else

@phat-lasagna he's right though. We all been there, where we didn't know why the code behaves im a stupid way, were sure we did everything right and spent hours trying to debug it only to find out we just did some really stupid mistake that we never did before.

I think both the rant and that comment are correct to be here

@phat-lasagna Did I say I am better than “everyone else”?

For example, @SortOfTested is way better than me, especially at having good information quick at hand.

Also what @Hazarth said.

@RememberMe Don't you have a massacre to be overseeing or something?

@bagfox you just always seem to exhibit troll-like behavior on every rant you comment on. Like ofc he did it wrong, that's why he's ranting. There's no point in you saying that lol. Are you trying to be funny or something?

Without knowing what HTTP lib you are using, most libs handle it better if empty responses from the server has HTTP 204 status.