-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
fix: remove string.repeat for ie11 #1772
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/markedjs/markedjs/kouc9ky5a |
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.
Seems fine.
When do we want to drop support for IE 11?
Not sure, but I don't think we need to yet. |
We should settle on a date to drop support for IE since we are not testing it and even Microsoft products are dropping support. How about November 30? |
Sure. I'm good with it whenever but it will be a breaking change. Should we be removing the es5 version as well since we will only be supporting es6+ browsers? |
Sounds good to me. Grouping a few breaking changes is preferable to me 👍 |
I'm going to merge this to see if semantic release will pick up the correct version |
## [1.2.2](v1.2.1...v1.2.2) (2020-10-21) ### Bug Fixes * remove string.repeat for ie11 ([#1772](#1772)) ([2707070](2707070))
🎉 This PR is included in version 1.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Marked version: 1.2.0
Description
string.repeat
is not a function in IE11. If we are still supporting IE11 then we need to create our own repeat helper function. I searched for the fastest function and found https://stackoverflow.com/a/5450113/806777.I'm not exactly sure how we can write a test to make sure
string.repeat
isn't used in the future since even node v4 supportsstring.repeat
.Contributor
Committer
In most cases, this should be a different person than the contributor.