browser-sync@2.18.11 untested ⚠️

[greenkeeperio-bot]

🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

---

Hello lovely humans,

browser-sync just published its new version 2.18.11.

State	No tests ⚠️
Dependency	browser-sync
New version	2.18.11
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.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

FIXED Source map files are now ignored by default. c990ea2

Previously, if you were watching a directory into which source maps were being written (alongside your CSS/JS etc) then Browsersync would instruct all browsers to actually RELOAD as it wouldn't know how to handle the 'map' files.

This was particularly frustrating for gulp users - take this following example (where we compile sass-> css)

gulp.task('styles', function() {
  return gulp.src('app/core.scss')
      .pipe(sourcemaps.init())
      .pipe(sass())
      .pipe(sourcemaps.write('.'))
      .pipe(gulp.dest('dist'))
      .pipe(browserSync.stream())
});

With this, each time a file is saved, there would be 2 output files core.css & core.css.map and Browsersync would be informed of both. With the CSS file, it would update any references to that file in all connected browsers, but for the map file, it would perform a full page reload instead... This is never what a user expects, so I've fixed it.

---

FIXED default ghostMode.location: true 1a0505c

A recent change stopped a module being loaded on the client-side that handled UI events such as 'SYNC ALL' etc.

Issue: #1363

---

FIXED Added pointer-events: none to notification BrowserSync/browser-sync-client#36

---

FIXED Page blinking on styles reload is fixed BrowserSync/browser-sync-client#39

---

The new version differs by 102 commits .

• 510fde4 2.18.11
• c990ea2 fix(sourcemaps): let the client decide how to handle sourcemaps (so it can ignore & update CSS)
• a9e313e 2.18.10
• 1a0505c fix(ghostMode): ensure .location defaults to true - fixes Client doesn't react to SYNC/RESET ALL buttons unless ghostMode.location = true BrowserSync/browser-sync#1363
• b2955fc 2.18.9
• fb0e154 deps: update mocha@3.4.1
• 0452c8d ci: attempt to pass on windows
• d640213 ci: attempt to pass on windows
• 2946065 Remove < 4 on appveyor
• d573cfe deps: browser-sync-client@2.4.7, chokidar@1.7.0, fs-extra@3.0.1, serve-static@1.12.2
• cbe2ccb server: stronger certs
• 8d1b6f0 Merge pull request #975 from martindsouza/master
• 68dcfe1 docs: fix formatting of open option - closes Added missed <code> tag BrowserSync/browsersync.github.io#50
• 81adf91 Merge pull request #1320 from lucalanca/master
• d5196ce Bumps request to 2.79.0

There are 102 commits in total. See the full diff.