Fix blog opening: SPA component unmount instead of full navigation

[taras]

Motivation

A r/javascript commenter correctly pointed out that the blog opening — "Or you navigate away in the browser, and a request you no longer care about keeps running anyway" — is not true for full page navigation. Modern browsers kill all running JS, pending requests, etc. on navigation.

The actual problem is in SPAs, where route changes and component unmounts happen while async work is still in flight. That's where you get unscoped async work unless you explicitly wire cancellation.

Approach

One-line change in the opening of www/blog/2026-02-06-structured-concurrency-for-javascript/index.md:

"Or a component unmounts in your SPA, and the requests it started keep running anyway — burning battery, holding sockets, and calling callbacks into code that has already moved on."

This is technically accurate and preempts the nitpick.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/thefrontside/effection@1105

commit: c1f08fe