Spread operator mismatches native behavior when getter is used

[Buslowicz]

Bug Report

Current Behavior
When using object spread on an object with a getter, the function is triggered only once, and the result is copied to the output object.

Input Code

let counter = 0;

const x = { a: 1 };
const y = { ...x, get b() { counter++; return 2; } };
y.b;
y.b;

console.assert(counter === 2);

Expected behavior/code
Getter should be created in the output object so it can be triggered on each property access, as it happens with native browser implementation.

Babel Configuration (.babelrc, package.json, cli command)
Anything that compiles to ES5.

Environment
Any

Possible Solution
Use Object.getOwnPropertyDescriptors(input) to get a configuration of each input object and in case of getters/setters define them in the output object.

Additional context/Screenshots
This bug happens in both Babel and TypeScript, looks to be pretty common.

[babel-bot]

Hey @Draccoz! 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.

[mathieutu]

The same here:

{
  ...attributes,
  get fullName() {
    return `${this.firstName} ${this.lastName}`.trim()
  },
}

Will transpile to (pseudo code):

Object.assign({}, attributes, {
   get fullName() {
    return `${this.firstName} ${this.lastName}`.trim()
  }
})

so all this.* parameters will be undefined.

Works well in browser with direct spread operators.

[mathieutu]

Actually I found:
#7524
#7034
#9322
and https://babeljs.io/docs/en/next/babel-plugin-proposal-object-rest-spread.html

About this topic.
This should be handled by now, so I don't understand why it isn't working on our own.

I'm using a brand new create-react-app... 🤔

EDIT:

It was reverted in: #9379, and then a new PR was merged 7 days ago (so unreleased for now): #9384.

It should be fixed with the next released.

[nicolo-ribaudo]

This has been fixed: https://babeljs.io/repl#?browsers=node%205.0.0&build=&builtIns=false&spec=false&loose=false&code_lz=DYUwLgBAxg9grgOzCAThAvBADAbgFB6wIDOkAHhhAN4QCGAXBAIwQC--RpEAnpTQHSCyAGggBzcBABGACgCU1aPCSoA1KpwQU4OCgQQATJtZt83flLMX8hGCRih-tYsVRgZsRMjTpfhuThAA&debug=false&forceAllTransforms=false&shippedProposals=true&circleciRepo=&evaluate=false&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=env&prettier=false&targets=&version=7.12.12&externalPlugins=