-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Migrate from @babel/polyfill to core-js@3 #19872
Conversation
FYI the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh. Is it because with corejs only the bundled files are polyfilled and anything external isn't? 😢 |
Probably, I just checked the login page and it was an Object.assign in backbone.js that caused that. |
Okay. Then we can either
|
Not sure if that fixes it but maybe we could also make sure that the affected node modules are transpiled as well? https://github.com/nextcloud/server/blob/master/webpack.common.js#L86 |
It will help with the packages where we know that transpilation is requried. But anything else might break. I think the safe path is to still ship a polyfill. On that note. We might want to document that apps shouldn't rely on it, so we can phase that out? |
You also need other stuff to replace polyfill: import "core-js/stable";
import "regenerator-runtime/runtime"; |
Now we're at 1356kB :rocket_crashing: |
Signed-off-by: Christoph Wurst <[email protected]>
f987fb7
to
fa9c206
Compare
Tested again with IE11, Object.assign was there :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I am a bit worried about this but it looks like other people have write access so it should still be supported.
EDIT: TLDR, the author and primary maintainer of the project has been sentenced to 1.5 years in prison.
Ouch. Didn't know about that. As the polyfill is deprecated this is our best choice right now. If alternatives evolve, we should be able to migrate to them. |
Ref 🔖 https://babeljs.io/blog/2019/03/19/7.4.0
Supersedes #19842