-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update dependency browser-sync to v3 - abandoned #65
base: master
Are you sure you want to change the base?
Conversation
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 34.4%, saving 3.62 MB.
71 images did not require optimisation. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
This PR contains the following updates:
^2.27.10
->^3.0.2
Release Notes
BrowserSync/browser-sync (browser-sync)
v3.0.2
Compare Source
What's Changed
New Contributors
Full Changelog: BrowserSync/browser-sync@v3.0.1...v3.0.2
v3.0.1
Compare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.29.3...v3.0.1
v3.0.0
Compare Source
v2.29.3
: The one that fixes snippetOptionsCompare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.29.2...v2.29.3
v2.29.2
Compare Source
v2.29.1
Compare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.29.0...v2.29.1
v2.29.0
: The one that restores IE11 support 💪Compare Source
What's Changed
esbuild 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 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)
### IE11 works, again npm install browser-sync@latest
Full Changelog: BrowserSync/browser-sync@v2.28.3...v2.29.0
v2.28.3
Compare Source
v2.28.2
Compare Source
v2.28.1
Compare Source
v2.28.0
: the one that finally removesdocument.write
Compare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.27.12...v2.28.0
v2.27.12
Compare Source
v2.27.11
Compare Source
Configuration
📅 Schedule: Branch creation - "after 6am and before 10am on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.