Skip to content
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

Polyfills for dependencies #4

Open
jamiebuilds opened this issue Oct 2, 2016 · 2 comments
Open

Polyfills for dependencies #4

jamiebuilds opened this issue Oct 2, 2016 · 2 comments

Comments

@jamiebuilds
Copy link

@ljharb brought this up in TC39 the other day...

Ponyfills should absolutely be encouraged, I think there's plenty of benefits to using them. However, there's a valid use case of polyfills that gets ignored:

When you have nested dependencies that have less backwards support than you do they won't use ponyfills/polyfills. Now you can't use that particular dependency without using a full polyfill unless you fork the dependency (which could also be several deps deep).

  1. I think package authors should be encouraged to use ponyfills longer than everyone else
  2. I think polyfills should be limitedly encouraged as the correct solution to that particular problem
@sindresorhus
Copy link
Owner

Agreed

@lacymorrow
Copy link

Yes, I will say that Ponyfills are quite clever for graceful degradation. Support everything. It's our job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants