I found all of those in their respective release notes:

• Chrome: https://developer.chrome.com/release-notes/134#explicit_resource_management_async
• Deno: https://deno.com/blog/v2.3
• Edge: https://learn.microsoft.com/en-us/microsoft-edge/web-platform/release-notes/134
• Node: https://nodejs.org/en/blog/release/v24.0.0

You're editing an automatically-generated file :)

Don't worry about figuring out the right way to do this. It's easy for me to do, so I can take it from here. This data is typically automatically derived from various sources. However, it looks like esbuild's sources are indicating that the correct support matrix looks more like this:

• Chrome: 143+
• Edge: 143+
• Firefox: 147+
• Node: 25+

There are several implementation bugs known in earlier versions of these platforms, so esbuild should still apply the transform to avoid them. This is one example that doesn't work correctly in Node 24. The data esbuild pulls from can be visualized here (sort of): https://compat-table.github.io/compat-table/esnext/

You're editing an automatically-generated file :)

Oops 😅 i have not noticed that