[Bug]: Wrong transpilling @babel/[email protected] when destructuring to a new object about babel HOT 3 OPEN

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

from babel.

Why do you want to transpile es2015 features, sich as computed keys, but no newer features, such as object spread?

I don't think this case matters much, because all browser that supports ... in objects has full support for es2015.

from babel.

I dont, maybe Im doing something wrong?
Makes me think to ways, is there a way of setting a prest for no-commonjs but without es2015? (if there is, my fault)
But, if this pereset exists (the one i´m using now), shouldnt it work ok? I mean, this error in transpilling could be weeeery difficult to debug because, it changes the way the result is affected but no error thrown and no alert of the situation, if one dont imagine something like this could happen in a more complex scenario... could be much of a problem to detect.
Sorry for my english thoug.

from babel.