Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(deps): update dependency browser-sync to v2.29.0 (#312)
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](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) | [![age](https://badges.renovateapi.com/packages/npm/browser-sync/2.29.0/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/browser-sync/2.29.0/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/browser-sync/2.29.0/compatibility-slim/2.28.3)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/browser-sync/2.29.0/confidence-slim/2.28.3)](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>
- Loading branch information