browser-sync just published its new version 2.16.0.
State
No tests :warning:
Dependency
browser-sync
New version
2.16.0
Type
devDependency
This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.
I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.
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.
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:
it should've never been part of the the path in the first place as it caused problems for people upgrading
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.
Hello lovely humans,
browser-sync just published its new version 2.16.0.
This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.
I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.
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
2 fixes & a really useful new option.
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:
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 7 commits .
f147b932.16.0fb77d82chore: ci62d83b8feat(cors): Add new option 'cors' for adding HTTP access control (CORS) to assets served by Browsersyncf5c3910deps: Bump browser-sync-ui6fc76d4use query string instead of path for versioning client JS05dc70dUpdate .travis.yml9a5f339Update appveyor.ymlSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade