Skip to content

Remove es6 promise#7677

Closed
IgorMinar wants to merge 3 commits into
angular:masterfrom
IgorMinar:remove-es6-promise
Closed

Remove es6 promise#7677
IgorMinar wants to merge 3 commits into
angular:masterfrom
IgorMinar:remove-es6-promise

Conversation

@IgorMinar
Copy link
Copy Markdown
Contributor

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit-message-format
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
    drop obsolete es6-promise dependency

* What is the current behavior? (You can also link to an open issue here)

* What is the new behavior (if this is a feature change)?

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
    not really. projects that already require es6-promise polyfill will now contain unnecessary dependency which should be removed if only everygreen browsers are targeted by the app.
  • Other information:

As of zone.js@0.6* we no longer require an es6-promise polyfill. The polyfill is only needed on browsers that don't
have native Promise support.
@IgorMinar IgorMinar added the action: review The PR is still awaiting reviews from at least one requested reviewer label Mar 19, 2016
@IgorMinar
Copy link
Copy Markdown
Contributor Author

// @wardbell - fyi

@wardbell
Copy link
Copy Markdown
Contributor

To be clear, is the shim still required for older supported browsers e.g. IE10 and IE11? I'm not sure which browsers you're including in "evergreen browsers"

@IgorMinar
Copy link
Copy Markdown
Contributor Author

My understanding is that edge is the only evergreen browser from MS.

MDN concurs
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
On Sat, Mar 19, 2016 at 4:15 PM Ward Bell notifications@github.com wrote:

To be clear, is the shim still required for older supported browsers e.g.
IE10 and IE11? I'm not sure which browsers you're including in "evergreen
browsers"


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#7677 (comment)

@e-oz
Copy link
Copy Markdown

e-oz commented Mar 20, 2016

@wardbell I share your opinion that majority of apps will have to support IE1, but it will be easy and more fair (and explicit) for them to add es6-shim to app dependencies, without having it as default dependency. And small subset of apps, which don't have to support IE11 (mobile apps, for example), will have benefit of it. "Pay for what you use" :)

@IgorMinar
Copy link
Copy Markdown
Contributor Author

CI is green.

@filipesilva
Copy link
Copy Markdown
Contributor

It comes down to what is said here:

LEGACY BROWSER SUPPORT

In addition to fully supporting latest versions of Chrome, Edge, Firefox, IE, and Safari, Angular 2 is also tested for older browsers including IE9+ and Android 4.1+.

If we put a warning about it somewhere, that this shim is only needed on those platforms, I think it's reasonable enough to remove it from the angular peer deps.

But it would be expected that in any best practices document the shim is listed, for without it apps would not work on one browser and one mobile platform.

It's also worth noting that component libraries should care nothing for this shim. Maybe not even for other shims.

@mhevery
Copy link
Copy Markdown
Contributor

mhevery commented Mar 21, 2016

New zones will polyfill Promises regardless if they are in the browser, so removing the polyfill here is the right thing, and it will have no impact on any legacy browsers.

@mhevery mhevery added pr_state: LGTM action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Mar 21, 2016
@mary-poppins
Copy link
Copy Markdown

Merging PR #7677 on behalf of @jelbourn to branch presubmit-jelbourn-pr-7677.

@mary-poppins
Copy link
Copy Markdown

Merging PR #7677 on behalf of @jelbourn to branch presubmit-jelbourn-pr-7677.

@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants