Skip to content

Conversation

@eriwen
Copy link
Member

@eriwen eriwen commented Oct 8, 2014

Add ES5 polyfills inline instead of depending on a shim library.

@eriwen eriwen added the RFC label Oct 8, 2014
@eriwen eriwen added this to the v1.0.0 milestone Oct 8, 2014
@pkozlowski-opensource
Copy link

Imo it would be better to not include polyfils as part of this library. Doing so woul penalise users of modern browsers and the ones that are including one already. Maybe it would be enough to point people to a polyfil or keep a minimal polyfil as a separate file.

@eriwen
Copy link
Member Author

eriwen commented Oct 9, 2014

@pkozlowski-opensource Given this PR there is very, very little cost for modern browsers or others who're using shims because we don't redefine necessary functions if they're defined.

I strongly believe we should polyfill because I want stacktrace.js to "just work" in legacy envs.

I think mostly I hope to decide whether we should require() es5-shim or something.

@eriwen eriwen merged commit 97c26eb into master Oct 10, 2014
@eriwen eriwen deleted the es5-polyfills branch January 26, 2015 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants