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 v2.29.3 #52
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/browser-sync-2.x
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
December 21, 2017 22:35
bc6bb0c
to
9947ce5
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.19.0
chore(deps): update dependency browser-sync to v2.20.0
Dec 21, 2017
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
December 22, 2017 07:33
9947ce5
to
f5f72d8
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.20.0
chore(deps): update dependency browser-sync to v2.20.1
Dec 22, 2017
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
December 22, 2017 10:17
f5f72d8
to
cd253b0
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.20.1
chore(deps): update dependency browser-sync to v2.21.0
Dec 22, 2017
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.21.0
chore(deps): update dependency browser-sync to v2.22.0
Dec 28, 2017
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
2 times, most recently
from
December 29, 2017 14:32
f645b38
to
c85f332
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.22.0
chore(deps): update dependency browser-sync to v2.23.0
Dec 29, 2017
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
December 29, 2017 16:40
c85f332
to
b1986ab
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.0
chore(deps): update dependency browser-sync to v2.23.1
Dec 29, 2017
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
January 1, 2018 22:02
b1986ab
to
c565b80
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.1
chore(deps): update dependency browser-sync to v2.23.2
Jan 1, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
January 5, 2018 18:17
c565b80
to
1857285
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.2
chore(deps): update dependency browser-sync to v2.23.3
Jan 5, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
January 10, 2018 09:21
1857285
to
690f94e
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.3
chore(deps): update dependency browser-sync to v2.23.5
Jan 10, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
January 24, 2018 17:14
690f94e
to
f56df38
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.5
chore(deps): update dependency browser-sync to v2.23.6
Jan 24, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
April 20, 2018 06:27
f56df38
to
284aa06
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.6
chore(deps): update dependency browser-sync to v2.23.7
Apr 20, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
April 29, 2018 20:58
284aa06
to
67e7b5e
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.23.7
chore(deps): update dependency browser-sync to v2.24.0
Apr 29, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
April 30, 2018 05:24
67e7b5e
to
42b3c7d
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.24.0
chore(deps): update dependency browser-sync to v2.24.1
Apr 30, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
May 2, 2018 14:26
42b3c7d
to
b1375e1
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.24.1
chore(deps): update dependency browser-sync to v2.24.2
May 2, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
May 3, 2018 11:54
b1375e1
to
782d9d1
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.24.2
chore(deps): update dependency browser-sync to v2.24.3
May 3, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
October 13, 2018 11:52
b6aee44
to
eff5558
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.2
chore(deps): update dependency browser-sync to v2.26.3
Oct 13, 2018
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
October 13, 2018 12:49
eff5558
to
66abe4c
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.3
chore(deps): update dependency browser-sync to v2.26.4
Apr 22, 2019
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
April 22, 2019 19:25
66abe4c
to
afedfc1
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.4
chore(deps): update dependency browser-sync to v2.26.5
Apr 24, 2019
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
April 24, 2019 20:29
afedfc1
to
384b096
Compare
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
June 19, 2019 11:40
384b096
to
b00fbde
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.5
chore(deps): update dependency browser-sync to v2.26.7
Jun 19, 2019
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
August 27, 2020 09:56
b00fbde
to
cf3f808
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.7
chore(deps): update dependency browser-sync to v2.26.12
Aug 27, 2020
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
October 26, 2020 06:59
cf3f808
to
6744bf5
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.12
chore(deps): update dependency browser-sync to v2.26.13
Oct 26, 2020
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
January 30, 2021 11:47
6744bf5
to
8d7a0c9
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.13
chore(deps): update dependency browser-sync to v2.26.14
Jan 30, 2021
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
October 20, 2021 07:03
8d7a0c9
to
3acd162
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.26.14
chore(deps): update dependency browser-sync to v2.27.5
Oct 20, 2021
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
March 7, 2022 08:08
3acd162
to
d8b4647
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.27.5
chore(deps): update dependency browser-sync to v2.27.7
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
March 26, 2022 15:53
d8b4647
to
07dad19
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.27.7
chore(deps): update dependency browser-sync to v2.27.9
Mar 26, 2022
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
June 18, 2022 23:51
07dad19
to
3ded31c
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.27.9
chore(deps): update dependency browser-sync to v2.27.10
Jun 18, 2022
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.27.10
chore(deps): update dependency browser-sync to v2.28.3
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
March 16, 2023 15:40
3ded31c
to
c7705ac
Compare
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
March 24, 2023 19:53
c7705ac
to
f399b17
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.28.3
chore(deps): update dependency browser-sync to v2.29.1
Mar 24, 2023
renovate
bot
force-pushed
the
renovate/browser-sync-2.x
branch
from
May 28, 2023 12:12
f399b17
to
e2dd69b
Compare
renovate
bot
changed the title
chore(deps): update dependency browser-sync to v2.29.1
chore(deps): update dependency browser-sync to v2.29.3
May 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.18.13
->2.29.3
Release Notes
BrowserSync/browser-sync (browser-sync)
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
v2.27.10
Compare Source
v2.27.9
: 2.27.9Compare Source
What's Changed
A bug prevented the help output from displaying - it was introduced when the CLI parser
yargs
was updated, and is now fixed :)Full Changelog: BrowserSync/browser-sync@v2.27.8...v2.27.9
v2.27.8
: 2.27.8Compare Source
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
v2.27.7
Compare Source
v2.27.6
Compare Source
v2.27.5
Compare Source
v2.27.4
Compare Source
v2.27.3
Compare Source
v2.27.1
: addedsnippet: boolean
optionCompare Source
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
the original request was related to Eleventy usage, so here's how that would look
v2.26.14
: upgraded dependenciesCompare Source
This is a maintenance release to address 2 security related issues (socket.io & axios)
Happy Browsersync'in :)
v2.26.13
Compare Source
v2.26.12
Compare Source
v2.26.10
Compare Source
v2.26.9
Compare Source
v2.26.7
Compare Source
v2.26.6
Compare Source
v2.26.5
Compare Source
v2.26.4
Compare Source
v2.26.3
: 2.26.0 -> 2.26.3Compare Source
fixes
d60cd91
0a2ff5a
9f3fea4
v2.26.2
Compare Source
v2.26.1
Compare Source
v2.26.0
Compare Source
these notes describe the change from 2.24.6 -> 2.26.0
fixes
257fba6
domain
key in proxy responsesdacfc8b
11729cc
06ee1b7
9e96603
48286e0
chore
0d4ab81
900e23e
ef12e9a
lerna
7c0ad4e
c108af8
4ac3a49
d6198f9
325c775
feature
d641916
docs
cf0febd
16487ad
deps
27f2173
a6578a3
v2.25.0
: thelisten
option releaseCompare Source
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 usinghost
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 tolocalhost
(this does mean that other features such asexternal urls
will not work any more, but if you need thislisten
option in the first place, that will not be a concern for you)npm i -g browser-sync@2.25.0 browser-sync . --listen localhost
v2.24.7
: Bug fixesCompare Source
fix
b6ba0dd
9e96603
48286e0
deps
a6578a3
v2.24.6
Compare Source
v2.24.5
Compare Source
fix
dd70eba
90e7306
v2.24.4
: Bug fixCompare Source
fix
a6d39e6
v2.24.3
: bug fixesCompare Source
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
cc5118c
1153845
9cef9c1
568e64e
b37e11c
v2.24.2
Compare Source
v2.24.1
Compare Source
v2.24.0
: 2.24.0Compare Source
Features
99a69ce
9d9dfb1
injectNotification
option & defaulted to false06608fb
4803786
e4754c9
Fixes
b8685bc
watch
boolean when falseb41f602
Dependencies
0ad5f3a
f6ac69f
0e1dd37
679fbbc
Tests
31bace2
misc
1c9ae43
8a957e9
31956ab
78c3854
teh
tothe
4ce533c
v2.23.7
: Bug fixCompare Source
66dd19c
v2.23.6
: Bug fixesCompare Source
v2.23.5
Compare Source
v2.23.4
Compare Source
v2.23.3
Compare Source
misc
type: array
in server field of startOpts" - fixes #1483 (This reverts commitb24514b
)31150d6
620e9ae
v2.23.2
Compare Source
CLI
type: array
in server field of startOptsb24514b
v2.23.1
Compare Source
2.23.1 (2018-01-01)
v2.23.0
: - DX releaseCompare Source
e6be4e9
notify
command over HTTP protocolac86665
(closes #1467)3b7e8cb
91b7e89
watch
option - (see below)@imports
- thanks to Live Reloadfb26e82
(closes #10)b5cc56e
single
option - adds a middleware to help with SPAs (serves index.html for all non-matching routes)91480aa
ignore
option - shortcut for adding towatchOptions.ignored
- added because of the newwatch
optiongit checkout
without any configurationfd3d074
dbb1267
cb5b44c
Highlights
Easier CLI commands
In an attempt to streamline the common use-cases, Browsersync will now attempt to 'do the right thing' when no command is provided, for example:
To run a static server, serving from the current directory
To run a static server, serving from 2 directories:
If the directory contains a 'index.html' file, you can omit any input and just run:
### after browser-sync
You can run the proxy in this manner too
### after browser-sync https://example.com
To run a proxy, whilst also serving static files
### after browser-sync https://example.com htdocs/themes/example
New
watch
optionBecause we now have the shorthand ways of launching servers/proxies, eg:
browser-sync .
- it also made sense to automatically watch files too. So, ifwatch: true
- then Browsersync will make a best-guess at which files to automatically watch.Here's a comparison to the old way (which will still work, of course)
Behind the scenes, Browsersync is just looking at served directories (in this case,
app
) andadding it to the regular
files
option as normal.It means the following the 2 configurations are identical, but the latter is better since there's no
repetition.
New
ignore
optionAdded as a convenience since we have simpler watching via the
watch
flag. Use it to ignore any patterns that should not cause Browsersync reloads/injectionsExample:
- Serve files from the 'app' directory
- Watch all files
- But, exclude
**/*.js
(if using Webpack, etc)CLI:
browser-sync app -w --ignore '**/*.js'
Config:
New
single
option, easy SPA developmentThis option will add the
connect-history-api-fallback
middleware automatically for you, meaning that developing with client-side routers can be done without configuring this middleware manuallyExample:
- Serve files from the
app
directory- Watch all files
- Serve
index.html
for all none matching routesFall back to a directory listing if a request gives a 404
No more
Cannot Get /' messages
. If you run Browsersync in a directory where there's noindex.html
, a directory listing will be shown instead.v2.22.0
Compare Source
v2.21.0
Compare Source
v2.20.1
Compare Source
v2.20.0
Compare Source
v2.19.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.