proposal-cancellation VS proposal-source-phase-imports

To cancel a task, you'll have to do that plumbing yourself, and it depends on what you're wanting to cancel. Most libraries provide some sort of mechanism to do the cancelation. The fetch API allows you to pass in an abort controller, which provides a way for you to signal to the running fetch request to abort. setTimeout() has clearTimeout(). In Node, if you read a file as a stream instead of a simple fs.promises.readFile(), you'll have the power to just stop trying to grab more data from the stream. Each async API has its own way to enable aborting (or, sometimes it doesn't provide any way to abort at all). There's unfortunately no standard way to handle aborting (though there is this stalled JavaScript proposal that attempted to standardize an abort system).

Finally, one other related and important concept is the token-based cancelation of asynchronous subscriptions (the current TC39 proposal), which I plan to cover later. If you find these topics interesting, consider following me on Twitter for any updates.

We will soon support WASM imports (`import source foo from "./foo.wasm"`). [1]

[1]: https://github.com/tc39/proposal-source-phase-imports

Source Phase Imports: Proposal to enable importing modules at the source phase.

Import Reflection: Syntax to import ES modules with import reflection attributes.

Alternative module reflections (wasm imports): https://github.com/tc39/proposal-import-reflection

Evaluator Attributes: Enables the module import syntax to provide extra attributes along with a given import as evaluator attributes with the primary use case in mind of permitting these module type imports for Wasm slides.