fix(deps): update dependency browser-sync to v2.27.9 by renovate[bot] · Pull Request #248 · redhataccess/spandx

renovate · 2021-10-26T14:23:29Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
browser-sync (source)	`2.18.13` -> `2.27.9`

Release Notes

BrowserSync/browser-sync

`v2.27.9`

Compare Source

What's Changed

fix(cli): Where's the command help? fixes #1929 by @shakyShane in fix(cli): Where's the command help? fixes #1929 BrowserSync/browser-sync#1945

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`

Compare Source

This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

PR:

BrowserSync/browser-sync@58ab4ab

Resolved Issues:

Thanks to @lachieh for the original PR, which helped me land this fix

This release adds a feature to address BrowserSync/browser-sync#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,
});

`v2.26.14`

Compare 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`

Compare Source

fixes

application/wasm support - fixes #1598 d60cd91
deps - ensure previous users of browser-sync-client are not affected by new structure - fixes #1615 0a2ff5a
npm audit fixes across all packages - fixes #1618 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

Removing default logger prefix [BS] - fixes #1607 257fba6
case-insensitive matching on domain key in proxy responses dacfc8b
bump chokidar fixing fsevents build - closes #1613 11729cc
Unexpected Page Reload after Pausing in Debugger - fixes #1591 06ee1b7
scroll - add missing init method for window.name method of scroll restoring - fixes #1586 #1457 #1457 9e96603
proxy Port gets unnecesarily rewritten in Proxy - fixes #1577 48286e0

chore

move cypress to top-level dep 0d4ab81
package-lock files 900e23e
change API of option transforms ef12e9a

lerna

initial version 7c0ad4e
more path updates c108af8
updated more stuff since the move to lerna 4ac3a49
bring in server/client/ui d6198f9
add browser-sync-ui 325c775

feature

adding 'listen' option to restrict binding of interfaces d641916

docs

emphasize a couple of points - fixes #1461 cf0febd
added additional note about httpModule option - fixes #1485 16487ad

deps

npm audit for localtunnel - fixes #1587 27f2173
easy-extender@2.3.4 cypress@3.1.0 supertest@3.1.0 a6578a3

`v2.25.0`

Compare 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 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 browser-sync@2.25.0
browser-sync . --listen localhost

`v2.24.7`

Compare Source

fix

Update opn to latest release b6ba0dd
scroll - add missing init method for window.name method of scroll restoring - fixes #1586 #1457 #1457 9e96603
proxy Port gets unnecesarily rewritten in Proxy - fixes #1577 48286e0

deps

easy-extender@2.3.4 cypress@3.1.0 supertest@3.1.0 a6578a3

`v2.24.6`

Compare Source

`v2.24.5`

Compare Source

fix

update following npm audit - fixes #1559 dd70eba
TypeError when watchOptions.ignored is not an array - fixes #1563 90e7306

`v2.24.4`

Compare Source

fix

Remote Debug tools do not work - fixes #1556 a6d39e6

`v2.24.3`

Compare 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

Don’t always add "defaultIgnorePatterns" - fixes #1543 cc5118c
handle windows-style paths on the client - fixes #1553 1153845
remove source-maps from client - fixes #1551 9cef9c1
support bs.reload('*.css') - fixes #1550 568e64e
(client) use correct npm lifecycle hook for prepublish - fixes #1549 b37e11c

`v2.24.2`

Compare Source

`v2.24.1`

Compare Source

`v2.24.0`

Compare Source

Features

(client) rewrite to Typescript + RxJS 99a69ce
(client) make initial options available in initial payload 9d9dfb1
(client) added injectNotification option & defaulted to false 06608fb
(client-js) allow functions in client:js hook 4803786
(http-protocol) support POST requests over HTTP Protocol e4754c9

Fixes

(client, rxjs) fix imports to avoid the entire library being bundled b8685bc
(cli) remove watch boolean when false b41f602

Dependencies

upgrade ua-parser-js@0.7.17 0ad5f3a
upgrade serve-static@1.13.2 f6ac69f
upgrade qs@6.2.3 - fixes #1512 0e1dd37
typescript@2.8 679fbbc

Tests

add cypress for integration tests 31bace2

misc

Resolved warning in tsconfig. 1c9ae43
Merge pull request #1547 from jgravois/patchbump localtunnel to resolve security vuln nag 8a957e9
bump localtunnel to resolve security vuln nag 31956ab
Merge pull request #1544 from SergiuNegara/fix/steam-docs-spellingFix stream docs spelling 78c3854
Fix stream docs spellingChange teh to the 4ce533c

`v2.23.7`

Compare Source

fix(client): CSS injection broken in older browsers due to use of Array.from - fixes #1539 66dd19c

`v2.23.6`

Compare Source

fix(client): remove sourcemaps - fixes #1498, Uncaught SyntaxError: Unexpected token } BrowserSync/browser-sync-client#45
fix(watcher): remove greedy regexes - fixes #1490
fix(css-injection): enable smoother CSS file for none-css files - re: #1488

`v2.23.5`

Compare Source

`v2.23.4`

Compare Source

`v2.23.3`

Compare Source

misc

Revert "Fix the missing type: array in server field of startOpts" - fixes #1483 (This reverts commit b24514b) 31150d6
fix(server-middleware): allow res.end -> next() in middeware flow when no serveStatic exists - fixes #1481 620e9ae

`v2.23.2`

Compare Source

CLI

Fix the missing type: array in server field of startOpts b24514b

`v2.23.1`

Compare Source

2.23.1 (2018-01-01)

`v2.23.0`

Compare Source

Fixed: removed weinre from the UI - it was using deprecated packages, and is un-maintained. e6be4e9
Fixed: Updated socket.io to the latest version (security advisory)
Fixed: Allow notify command over HTTP protocol ac86665 (closes #1467)
New: CI: build on node 8 (latest lts) 3b7e8cb
New: Easier CLI commands for common flows. (see below) 91b7e89
New: watch option - (see below)
New: Supports CSS @imports - thanks to Live Reload fb26e82 (closes #10)
New: Fall back to a directory listing if a request gives a 404 b5cc56e
New: single option - adds a middleware to help with SPAs (serves index.html for all non-matching routes) 91480aa
New: ignore option - shortcut for adding to watchOptions.ignored - added because of the new watch option
Improved: Perf: Always group file-changes into flexible 500ms buffers - this will help things such as git checkout without any configuration fd3d074
Improved: Perf: Adding adding cwd + ignore defaults to all watcher options dbb1267
Changed: Log CSS file injections into the console (rather than the overlay, which always gets in the way) 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

### before
browser-sync start --server
### after
browser-sync .

To run a static server, serving from 2 directories:

### before
browser-sync start --server app/src app/tmp
### after
browser-sync app/src app/tmp

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` option

Because we now have the shorthand ways of launching servers/proxies, eg: browser-sync . - it also made sense to automatically watch files too. So, if watch: 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)

### before
browser-sync start --server ./app --files ./app
### after
browser-sync ./app -w

Behind the scenes, Browsersync is just looking at served directories (in this case, app) and
adding 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.

{
  "server": {"baseDir": ["app"]},
  "files": ["app"]
}

{
  "server": {"baseDir": ["app"]},
  "watch": "true"
}

New `ignore` option

Added as a convenience since we have simpler watching via the watch flag. Use it to ignore any patterns that should not cause Browsersync reloads/injections

Example:
- Serve files from the 'app' directory
- Watch all files
- But, exclude **/*.js (if using Webpack, etc)

CLI:

browser-sync app -w --ignore '**/*.js'

Config:

{
    "server": "app",
    "watch": true,
    "ignore": "**/*.js"
}

New `single` option, easy SPA development

This 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 manually

Example:
- Serve files from the app directory
- Watch all files
- Serve index.html for all none matching routes

browser-sync app -w --single

Fall 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 no index.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: 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.

If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate bot force-pushed the renovate/browser-sync-2.x branch from 37a5eb9 to 0ba59b7 Compare October 27, 2021 21:26

renovate bot changed the title ~~fix(deps): update dependency browser-sync to v2.27.6~~ fix(deps): update dependency browser-sync to v2.27.7 Oct 27, 2021

renovate bot force-pushed the renovate/browser-sync-2.x branch from 0ba59b7 to 4b0843f Compare December 14, 2021 05:37

renovate bot force-pushed the renovate/browser-sync-2.x branch 2 times, most recently from 99ff315 to 049d79b Compare March 13, 2022 23:02

renovate bot changed the title ~~fix(deps): update dependency browser-sync to v2.27.7~~ fix(deps): update dependency browser-sync to v2.27.8 Mar 13, 2022

renovate bot force-pushed the renovate/browser-sync-2.x branch from 049d79b to cd8592a Compare March 15, 2022 10:10

renovate bot changed the title ~~fix(deps): update dependency browser-sync to v2.27.8~~ fix(deps): update dependency browser-sync to v2.27.9 Mar 15, 2022

fix(deps): update dependency browser-sync to v2.27.9

d63ff08

renovate bot force-pushed the renovate/browser-sync-2.x branch from cd8592a to d63ff08 Compare March 23, 2022 16:15

mwcz merged commit f7dfa3a into master Mar 25, 2022

renovate bot deleted the renovate/browser-sync-2.x branch March 25, 2022 19:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency browser-sync to v2.27.9#248

fix(deps): update dependency browser-sync to v2.27.9#248
mwcz merged 1 commit intomasterfrom
renovate/browser-sync-2.x

renovate bot commented Oct 26, 2021 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

renovate bot commented Oct 26, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

2.23.1 (2018-01-01)

Highlights

Easier CLI commands

New watch option

New ignore option

New single option, easy SPA development

Fall back to a directory listing if a request gives a 404

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

renovate bot commented Oct 26, 2021 •

edited

Loading

New `watch` option

New `ignore` option

New `single` option, easy SPA development