fix ie11 #2024
Merged
fix ie11 #2024
+6,339 −470
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
shakyShane force-pushed the browser-sync-1845 branch from 94d7856 to 1facd55 Compare shakyShane force-pushed the browser-sync-1845 branch from 1facd55 to bcd16cb Compare renovate bot referenced this pull request in openedx/edx-ui-toolkit Mar 20, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [browser-sync](https://browsersync.io/) ([source](https://togithub.com/BrowserSync/browser-sync)) | [`2.28.3` -> `2.29.0`](https://renovatebot.com/diffs/npm/browser-sync/2.28.3/2.29.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>BrowserSync/browser-sync</summary> ### [`v2.29.0`](https://togithub.com/BrowserSync/browser-sync/releases/tag/v2.29.0): The one that restores IE11 support 💪 [Compare Source](https://togithub.com/BrowserSync/browser-sync/compare/v2.28.3...v2.29.0) #### What's Changed - fix ie11 by [@​shakyShane](https://togithub.com/shakyShane) in [https://github.com/BrowserSync/browser-sync/pull/2024](https://togithub.com/BrowserSync/browser-sync/pull/2024) [esbuild](https://esbuild.github.io/) does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally broke `IE11` support 😢 This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers. So, IE11 will work once again 🎉. Please use the [issues](https://togithub.com/BrowserSync/browser-sync/issues) thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved) ```shell ### IE11 works, again npm install browser-sync@latest ``` **Full Changelog**: BrowserSync/browser-sync@v2.28.3...v2.29.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 3am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/openedx/edx-ui-toolkit). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNC4wIiwidXBkYXRlZEluVmVyIjoiMzUuMTQuMCJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
| Type: Opinion 💬 In my opinion, for developers should be preferable to support users who use new browsers than users who use older browsers. I don’t think spending time supporting Internet Explorer, which is used by 0.42% of users, while there are 535 issues and 25 pull requests open is the best idea. Moreover, when Internet Explorer was actively developed, it was the worst browser for web developers, its support took a lot of time. Now, in 2024, forcing people to use Internet Explorer seems like bosses sadism or reluctance to update very outdated services/applications. Thanks. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
No description provided.