Document ECMAScript explicit resource management

[captainbrosset]

Proposal

Chromium 134 comes with a new JS keyword: using , which allows explicit resource management.
See https://github.com/tc39/proposal-explicit-resource-management
And https://chromestatus.com/feature/5087324181102592 and https://chromestatus.com/feature/5071680358842368 which are both marked as shipping with 134.

Browser support

Chrome and Edge 134 should have this feature now.

Tasks

• [ ]

Dependencies

• [ ]: Add BCD data for this feature: ECMAScript explicit resource management - New using keyword should be added to BCD browser-compat-data#25873

Additional information

No response

Are you willing to support this work?

No response

[Josh-Cena]

#38027

@captainbrosset @caugner If they aren't, could other APIs documented in this PR, notably await using, AsyncDisposableStack, DisposableStack, SuppressedError, Symbol.disposable, Symbol.asyncDisposable, Iterator.prototype[Symbol.disposable], AsyncIterator.prototype[Symbol.asyncDisposable] be collected by BCD too?

[Elchi3]

Thanks for the list, @Josh-Cena. I can try to add these to the collector. openwebdocs/mdn-bcd-collector#893 is the issue in which we want to take into account proposals automatically somehow ideally but manually adding these will work for now, too.

[dipikabh]

Thanks @captainbrosset for reporting this, and @Josh-Cena for already putting together a PR to add the relevant pages.

Since content work is already underway, I'm moving this to mdn/content for further tracking.