Update browser-sync to version 2.16.0 🚀

[greenkeeperio-bot]

Hello lovely humans,

browser-sync just published its new version 2.16.0.

State	Update :rocket:
Dependency	browser-sync
New version	2.16.0
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of browser-sync. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

---

GitHub Release

A small release with 2 little fixes & a really useful new option

---

• FIXED - current connections will show once again in the UI - BrowserSync/UI@00af3da

---

• FIXED - the version number of the Browsersync client script is now added as a query param instead of within the file path. This is a massive help for users that have the snippet saved in a file.

  Fun fact: other than a sanity check to show which release of Browsersync you're using, the version number actually serves no purpose, and that's why:

1. it should've never been part of the the path in the first place as it caused problems for people upgrading
2. you've always been able to access the JS file without the version number at the end, but this wasn't the default... so no one did it... so I've fixed it now instead 👍

---

• ADDED - new option cors: true - setting this will ensure that all assets served by Browsersync (including the script file itself) in all modes will have HTTP access control headers added.

  This allows any domain to access your files, which can lead to some creative workflows - for example, you could create a chrome extension that added some files you have locally into a live site & have Browsersync auto-update them when they change.

---

enjoy :)

---

The new version differs by 840 commits .

• f147b93 2.16.0
• fb77d82 chore: ci
• 62d83b8 feat(cors): Add new option 'cors' for adding HTTP access control (CORS) to assets served by Browsersync
• f5c3910 deps: Bump browser-sync-ui
• 6fc76d4 use query string instead of path for versioning client JS
• 05dc70d Update .travis.yml
• 9a5f339 Update appveyor.yml
• 24d7275 2.15.0
• 80c091d feat(proxy): Allow https with non-https target - fixes #1175
• 5fcd12f 2.14.3
• e26750d chore: code style
• 48d588b Merge pull request #1186 from justgook/master
• 8ac0703 2.14.2
• 42059df fix(rewrites): also rewrite protocol-relative URLs - fixes #991
• 54ae01b 2.14.1

There are 250 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? :zap: greenkeeper upgrade}

[coveralls]

Coverage remained the same at 85.271% when pulling 56cc0a02084c8cc0d46bc5da5183068a55bcbbbb on greenkeeper-browser-sync-2.16.0 into 466d5b4eb12edde46576ad72008921644cbd72a9 on 1.x.x.