Promise chain possibly missing .catch()
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A .then() chain with no trailing .catch() on the same statement means rejected promises may fail silently.
Why it matters
A .then() chain with no .catch() turns every rejection into an unhandled promise rejection: the user's action silently does nothing, and in Node an unhandled rejection can take down the process. The failure only appears when the network or API actually misbehaves, which is exactly when the error path matters.
How to fix it
This check flags statements ending in .then() with no .catch() on the same statement, so first confirm each site is not already covered by a .catch() chained on the next line or an enclosing try/catch. For the genuinely unhandled ones, append a .catch() that surfaces the failure, or convert the chain to async/await inside try/catch, which usually reads better. The eslint-plugin-promise rule catch-or-return enforces this going forward.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo