An unhandled rejection
The error is reported, but the user sees nothing. Add .catch((err) => console.log("Could not save:", err.message)) and the red line disappears.
Every then, catch and finally returns a new promise, so you can chain steps: what a callback returns becomes the next step's value (and a returned promise is waited for), a throw skips ahead to the nearest catch, and a rejection nobody handles is reported as an unhandled rejection.
Change the code and press Run (Ctrl+Enter). Predict what will happen first, then break it on purpose and read what changes. Your edits are saved and match the lesson page.
Ready for more? This phase has 5 hands-on exercises with automatic checks.
Practice questions
Write the code in the editor, run it, then open the model answer to compare.
Rewrite the callback-hell example from Topic 10.4 as a flat chain, using later(value) that returns a promise fulfilled after 50 ms.
Write a chain that starts from Promise.reject(new Error("offline")), recovers with the value "cached copy" in a catch, and logs Showing: cached copy.
Explain it without notes
What does then return, and how is its value decided?
How do errors travel through a promise chain, and how do you recover from one?
What's the difference between p.then(ok, fail) and p.then(ok).catch(fail)?
What is an unhandled rejection, how is it reported, and how do you avoid it?
Preview
Console
Nothing logged yet.Expected console output
Saving the draft…
The rest of the page keeps working
Uncaught (in promise) Error: Server said 500