Closed greenkeeper[bot] closed 7 years ago
Your tests are still failing with this version. Compare the changes 🚨
FIXED Source map files are now ignored by default. c990ea2 BrowserSync/browser-sync-client@24de0ec
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
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 8 commits.
f015a29
2.18.13
d3d871d
chore(tests): cleanup to remove flaky tests
bf53394
Merge pull request #1378 from joemaller/master
c64c120
Merge pull request #1359 from docwhat/patch-1
470ab02
Merge pull request #1403 from swashcap/upgrade/localtunnel
4ff95ec
Upgrade localtunnel to 1.8.3.
08f4da0
Set default logPrefix to "Browsersync". Closes #1377
0aa00a7
Improve documentation for steam
See the full diff
Version 2.18.10 of browser-sync just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As browser-sync is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/benkalsky/reactabbble/22?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)Commits
The new version differs by 2 commits0.
a9e313e
2.18.10
1a0505c
fix(ghostMode): ensure
.location
defaults to true - fixes BrowserSync/browser-sync#1363false
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: