Skip to content
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

browser-sync@2.18.8 breaks build ⚠️ #270

Merged
merged 1 commit into from
Mar 2, 2017

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

browser-sync just published its new version 2.18.8.

State Failing tests ⚠️
Dependency browser-sync
New version 2.18.8
Type devDependency

This version is covered by your current version range and after updating it in your project the build kept failing.

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

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: re-implemented reloadDebounce to better suit the Browsersync use-case. Now we debounce and buffer events to allow multiple files to be injected following the specified window of event silence.


FIXED: de2e2fa added watchEvents option to solve #1291 - now you can override which file-watching events Browsersync will respond to.

For example, if you wanted to respond to the add event, along with the default change event, you could provide the following

   browser-sync start --server --files "app/src" --watchEvents change add

or

const bs = require('browser-sync').create();

bs.init({
server: 'app',
files: ['app/src'],
watchEvents: ['add', 'change']
});


FIXED: c6d7d16 always send override: true on public notify method to fix #538

This means you can now silence the default notify messages, whilst still using your own.

const bs = require('browser-sync').create();

bs.init({
server: 'app',
notify: false
});

setInterval(function() {
bs.notify('5 seconds have passed!')
}, 5000);


The new version differs by 14 commits .

See the full diff.


✨ Try the all new Greenkeeper GitHub Integration
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.

Screencast

Try it today. Free for private repositories during beta.

@Scrum Scrum merged commit c95accb into master Mar 2, 2017
@Scrum Scrum deleted the greenkeeper-browser-sync-2.18.8 branch March 2, 2017 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants