-
Notifications
You must be signed in to change notification settings - Fork 0
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
An in-range update of browser-sync is breaking the build 🚨 #89
Comments
Version 2.18.10 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 2 commits0.
false See the full diff |
Version 2.18.11 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes2.18.11FIXED 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.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 FIXED default 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 |
Version 2.18.12 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.18.13 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits.
See the full diff |
Version 2.19.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.20.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Version 2.20.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.21.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.22.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 38 commits.
There are 38 commits in total. See the full diff |
Version 2.23.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.23.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.23.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.23.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.23.3misc |
Version 2.23.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Version 2.23.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.23.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits.
See the full diff |
Version 2.23.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesBug fix |
Version 2.24.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes2.24.0Features
Fixes
Dependencies
Tests
misc
CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Version 2.24.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.24.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.24.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesbug fixes2.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
CommitsThe new version differs by 5 commits.
See the full diff |
Version 2.24.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.24.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.24.5fix CommitsThe new version differs by 6 commits.
See the full diff |
Version 2.24.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.24.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesBug fixesfix
deps CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 12 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Version 2.18.9 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 💪
Status Details
Commits
The new version differs by 12 commits0.
b2955fc
2.18.9
fb0e154
deps: update [email protected]
0452c8d
ci: attempt to pass on windows
d640213
ci: attempt to pass on windows
2946065
Remove < 4 on appveyor
d573cfe
deps: [email protected], [email protected], [email protected], [email protected]
cbe2ccb
server: stronger certs
8d1b6f0
Merge pull request #975 from martindsouza/master
68dcfe1
docs: fix formatting of
open
option - closes BrowserSync/browsersync.github.io#5081adf91
Merge pull request #1320 from lucalanca/master
d5196ce
Bumps request to 2.79.0
475588b
#970 Fix: Change SHA-1 to SHA-256 cert
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: