Keep multiple browsers & devices in sync when building websites. https://browsersync.io
APACHE-2.0 License
Bot releases are hidden (Show)
Published by shakyShane 23 days ago
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v3.0.2...v3.0.3
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v3.0.1...v3.0.2
Published by shakyShane 10 months ago
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.29.3...v3.0.1
Published by shakyShane over 1 year ago
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.29.0...v2.29.1
Published by shakyShane over 1 year ago
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.29.2...v2.29.3
Published by shakyShane over 1 year ago
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: https://github.com/BrowserSync/browser-sync/compare/v2.28.3...v2.29.0
Published by shakyShane over 1 year ago
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.12...v2.28.0
Published by shakyShane over 2 years ago
A bug prevented the help output from displaying - it was introduced when the CLI parser yargs
was updated, and is now fixed :)
Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.8...v2.27.9
Published by shakyShane over 2 years ago
This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)
PR:
Resolved Issues:
Thanks to @lachieh for the original PR, which helped me land this fix
Published by shakyShane over 3 years ago
This release adds a feature to address https://github.com/BrowserSync/browser-sync/issues/1882
Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet
option :)
browser-sync . --no-snippet
or in any Browsersync configuration
const config = {
snippet: false,
};
the original request was related to Eleventy usage, so here's how that would look
eleventyConfig.setBrowserSyncConfig({
snippet: false,
});
Published by shakyShane over 3 years ago
This is a maintenance release to address 2 security related issues (socket.io & axios)
Happy Browsersync'in :)
Published by shakyShane about 6 years ago
fixes
these notes describe the change from 2.24.6 -> 2.26.0
fixes
domain
key in proxy responses dacfc8bcedbd1f8e27a3ad4944aee44ff7f73533chore
lerna
feature
docs
deps
Published by shakyShane about 6 years ago
Browsersync can now be used in more restrictive areas, ones where you cannot simply bind to all addresses on the host (such as schools or universities) - this is enabled via the listen
option.
For backwards compatibility reasons, we actually cannot use the host
option to acheive this (even though that would make the most sense), as it would break some people's existing setups.
This is mainly because in the past, host
was not used to determine an address to bind to, but rather just as a way of changing the urls Browsersync displays to the user. :( :( :(
It was a big mistake, but now with the sheer size of the user base we have, every tiny change to any existing option causes some kind of breakage. I'm not prepared to do that again with host
.
So, instead we're back to the old method of instead adding a new option, that I've called listen
. It's the only way we can acheive the goal without breaking existing users who are using host
for other reasons.
The idea is that you'd only ever use the listen
option if you want to restrict the address being bound to. For example, the following will serve files from the current directory, but behind the scenes Browsersync will only bind to localhost
(this does mean that other features such as external urls
will not work any more, but if you need this listen
option in the first place, that will not be a concern for you)
npm i -g [email protected]
browser-sync . --listen localhost
Published by shakyShane about 6 years ago
fix
deps
Published by shakyShane over 6 years ago
fix
Published by shakyShane over 6 years ago
2.24.0 was a very large release - and with that, a handful of patch releases inevitably follow. Please move straight to 2.24.3 :)
fixes
Published by shakyShane over 6 years ago
Features
injectNotification
option & defaulted to false 06608fbe8d7e01fba19987f7de745af62535b57bFixes
watch
boolean when false b41f602bdae17db9ed4f5418719c4003646c0335Dependencies
Tests
misc
teh
to the
4ce533cec469c8ca45c9c6bca3bcfa8e52041369Published by shakyShane over 6 years ago