[Bug]: Babel throws on computed property access using[x]

[JLHwung]

💻

• Would you like to work on a fix?

How are you using Babel?

Programmatic API (babel.transform, babel.parse)

Input code

var using = [];
using[0];

REPL

Configuration file name

No response

Configuration

REPL

Current and expected behavior

Current: Babel throws "Support for the experimental syntax 'explicitResourceManagement' isn't currently enabled (2:1)"

Expected: Babel parses it successfully.

Environment

REPL

Possible solution

No response

Additional context

This is a regression introduced in #14968.

The bug is already covered in the test case

babel/packages/babel-parser/test/fixtures/experimental/explicit-resource-management/invalid-using-binding-pattern/input.js

Line 3 in e7405b9

using [ bar ] = g();

but the behaviour is not correct since it is already valid JS.

[babel-bot]

Hey @JLHwung! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.

[JLHwung]

Note that

babel/packages/babel-parser/test/fixtures/experimental/explicit-resource-management/invalid-using-binding-pattern/input.js

Line 2 in e7405b9

using { foo } = f();

will be valid under the Extractors proposal. I tend to remove the recoverable errors for the using-binding-pattern scenario.