[Bug]: Pure annotations are incorrectly modified to wrong scope

[hyrious]

💻

• Would you like to work on a fix?

How are you using Babel?

Programmatic API (babel.transform, babel.parse)

Input code

(/* @__PURE__ */ f()).g()

REPL Link

Configuration file name

No response

Configuration

None

Current and expected behavior

Currently babel strips the parentheses of (/* @__PURE__ */ f()), causing the whole expression f().g() be marked as pure.

/* @__PURE__ */
f().g();

// expect: same as input

Environment

System:
  OS: macOS 12.5
Binaries:
  Node: 18.6.0 - /usr/local/bin/node
  Yarn: 1.22.19 - /usr/local/bin/yarn
  npm: 8.15.0 - /usr/local/bin/npm
npmPackages:
  @babel/core: ^7.7.4 => 7.18.9
  @babel/plugin-proposal-class-properties: ^7.7.4 => 7.18.6
  @babel/plugin-proposal-object-rest-spread: ^7.7.4 => 7.18.9
  @babel/plugin-transform-modules-commonjs: ^7.15.0 => 7.18.6
  @babel/preset-env: ^7.7.4 => 7.18.9
  @babel/preset-react: ^7.7.4 => 7.18.6
  @babel/preset-typescript: ^7.7.4 => 7.18.6
  babel-loader: ^8.0.6 => 8.2.5
  webpack: ^5.74.0 => 5.74.0

Possible solution

No response

Additional context

No response

[babel-bot]

Hey @hyrious! 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]

As a workaround, you can enable the createParenthesizedExpressions parser option:

{
  // babel config
  plugins: [...],
  parserOpts: { createParenthesizedExpressions: true }
}

It will generate the ParenthesizedExpressions AST node where the pure annotation comment can be attached.