-
Notifications
You must be signed in to change notification settings - Fork 754
Release history
Shane Osbourne edited this page Mar 18, 2014
·
23 revisions
Release notes for BrowserSync
##0.7.2
- Re-introduced the
--config
option that allows custom paths to config files to be given on the command line. Fixes #100 - Added plugin interface for the upcoming control panel, (preview it now
by visiting
http://<browser-sync-ip>:3001
after BrowserSync has started. - Increased
z-index
value of notify Element. Fixes #2. Thanks to @hugomrdias
##0.7.0 - includes breaking changes
-
debugInfo: false
will now completely mute all console output. fixes #97 - You can now specify multiple base directories to serve files from when using the server. fixes #83
- Custom middleware can now be added to the server option. fixes grunt-browser-sync #11
- Added support for services such as http://xip.io/ through the new
hostnameSuffix
option. -
/client/browser-sync-client.js
now always resolves to the latest installed version of the client script. This help people who save the snippet to file. fixes #82 - File watching accuracy for people using ruby + sass is greatly improved (fouc eliminated now :) ).
- Scroll position now saved as a cookie instead of URL (thanks to @faergeek)
- Added plugin interface for some of the internals - making it easier to extend/consume BrowserSync.
-
BREAKING CHANGE -
proxy
option simplified. It's now as simple asproxy: "localhost:8000"
-
BREAKING CHANGE - Command line usage now requires commands to be prefixed with
start
. -
BREAKING CHANGE -
.init()
no longer returns the event emitter directly. See the API Docs. -
.init()
now accepts a callback with full access the BrowserSync Object. See the API Docs.
##0.6.2
-
Critical - Fixed a bug that was introduced in
0.6.1
where modifying response data with both Proxy & Server options would quit after first chunk. fixes: #36 & #87 - Merged PR #88 to check if the notify option was disabled before trying to displaying it. Thanks to @falzhobel
- Merged PR #85 to ensure the notify elem can be re-created if an app wipes it out. Thanks to @hugomrdias
##0.6.1
- Page reloads no longer jump back to the top (scroll position saved in query string) fixes #80.
- Now uses a version of connect-livereload middleware to make script-injecting more robust.
- Added in-browser notification when a browser is 'connected'.
- Fixed a bug that stopped scripts being injected into pages with query strings. fixes #35
- Added IE 7 & 8 specific middleware to deal with them not sending
html
in theiraccept
header - All sync actions now only check the URL path. fixes #78
##0.6.0
- Upgraded cl-strings to deal with #73 (now uses chalk) - thanks to @jas
- added
.map
to auto-excluded files (deals with chrome automatically requesting .map fils when devtools are open)
##0.5.8
- Upgraded http-proxy to > 1.0 (internal breaking changes).
- Added
startPath
option to allow the auto-opened browser to point to a sub-dir. - Added
scrollProportionally
option to allow scrollTop position to be synced instead. (thanks to @hugoBessaa) - Removed the minified client script (removes a build step & easier to work with/hack on)
- Added versioning to client script to elimate any cache issues on upgrades