◆ JavaScript

Catch async errors

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to make sure uncaught promise rejections in the signup flow surface to Sentry and don’t…+
I need to make sure uncaught promise rejections in the signup flow surface to Sentry and don’t leave the UI stuck. Wrap the async functions that run when the user clicks Create Account so the submit button is re-enabled and an error banner appears, then forward the error to Sentry, and do this before the end of today.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I ship, make it obvious to a reviewer how an async failure behaves: show the user-facing…+
Before I ship, make it obvious to a reviewer how an async failure behaves: show the user-facing error message first, then the retry button, and below that the telemetry call to Sentry. Highlight any places where the UI might remain blocked or state left inconsistent.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe Create Account button was clicked, the spinner started, and an uncaught rejection hit in…+
A promise rejection happened during form submit and the spinner never stopped
The Create Account button was clicked, the spinner started, and an uncaught rejection hit in the network code; now the spinner never stops and I can’t find the error in Sentry. I’m worried the button state and local store are inconsistent and I’m missing where the rejection is thrown. What’s the likely root cause and the least risky next fix to restore user experience and capture the error?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several releases we keep getting one-off crashes tied to different async handlers:…+
Occasional production crashes from uncaught async errors
Across several releases we keep getting one-off crashes tied to different async handlers: WebSocket reconnects, file uploads, and form submits. I spend time reproducing, patching, and then another slips through. What habit and guardrail should I adopt to stop these leaks, and how do I add a simple checklist so every async entry point has consistent error capture and state rollback?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.