Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/53655/

I found a bug: with the property mutators plugin, this code:

var obj = {
  get [(() => "x")()]() { return 1 },
  set [(() => "x")()](_) {}
};

console.log(obj.x);

logs undefined instead of 1. However, on main babel crashes when compiling it, so it's not a regression introduced by this PR.

https://babeljs.io/repl/build/53642/#?browsers=&build=&builtIns=false&corejs=false&spec=false&loose=false&code_lz=G4QwTgBA9gRgVhAvBA3gKAhA5gUwC4QDaAFMQJRIB8EARAB41nkC65qEY-ArmAHYQBGCAF8ANBggBnfEVIVE1eoxbEA-hRTC0wgNxo0AYyi9JUADY4AdGahZisOJbpkdQA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=true&fileSize=false&timeTravel=false&sourceType=module&lineWrap=false&presets=env&prettier=false&targets=&version=7.20.6%2Bpr.15234&externalPlugins=&assumptions=%7B%7D

Can this be reproduced in the repl? I tried and failed.

It seems that using merge would be more convenient in this case.

I was thinking about this, and I'm not sure anymore that we should fix it. main is already an improvement over #12097: instead of crashing, it just leaves the computed property as-is. If users want to transform computed properties, they have to also enable @babel/plugin-transform-computed-properties.

I forget why I did this, but apparently the original problem has been fixed.