https://github.com/tc39/proposal-explicit-resource-management

Alternative to#16190, with the distinction thatusing declarations at the top level of a component are only disposed when the component unmounts.

I think I prefer this — it's more useful and more intuitive.Demo here.

On the server it doesn't transform anything, meaning resources are correctly disposed of once rendering is complete. Obviously all this is of limited use until support is sufficiently widespread, but I don't see any reason to hold it back until then. (The demo above actually works in all browsers, because top-levelusing gets compiled away for client code, but that doesn't apply to server code or non-top-levelusing.)

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC:https://github.com/sveltejs/rfcs
• Prefix your PR title withfeat:,fix:,chore:, ordocs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.
• If this PR changes code withinpackages/svelte/src, add a changeset (npx changeset).

Tests and linting

• Run the tests withpnpm test and lint the project withpnpm lint