New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing es7.promise.finally polyfill when using useBuiltIns: usage #8500
Conversation
Usage of a `finally` instance method should trigger import of the `es7.promise.finally` polyfill, but it doesn't. This PR adds the missing definition and a test.
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/8865/ |
This way of adding |
You will have this problem even with the order of import from fixtures from this PR. |
@zloirock thanks, I was concerned about this too =/ |
Hello @zloirock and @existentialism , is there any way how this bug can be fixed? I tried to add the instanceMethods: {
finally: ["es6.object.to-string", "es6.promise", "es7.promise.finally"],
} but it didn't change the behavior of the I also don't understand why the test output has the reversed order of imports: import "core-js/modules/es7.promise.finally";
import "core-js/modules/es6.promise"; In the transpiled source, the |
I'm having an issue with this. Drilled it down to this:
If I comment out @zloirock this is perhaps a concrete example of what you said? |
@oles nope. |
@jsnajdr IIRC |
Hi, is this solved in anyway? i was testing and .finally was only working in Chrome and Safari. with the inclusion of "useBuiltIns: 'usage'," the error disappeared on Edge, but it failed silently and caused script execution problems. I had to remove finally from my code.
wepack.dist.config.js:
package.json:
|
Was it released? |
Yeah, since 7.0.0 |
Usage of a
finally
instance method should trigger import of thees7.promise.finally
polyfill, but it doesn't. This PR adds the missing definition and a test.