Force browser-sync version less than 2.23.2 having issue in npm start #196
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
thank you! |
|
FYI - this was fixed in https://github.com/BrowserSync/browser-sync/releases/tag/v2.23.3 Sorry for any inconvenience caused :) |
|
I"m still getting the error in 2.23.3 |
EmmDguez
pushed a commit
to EmmDguez/JavaScript30
that referenced
this pull request
Jun 10, 2018
Force browser-sync version less than 2.23.2 having issue in npm start
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
browser-sync version 2.23.2 does not work in project 19, 20 or 21. In the browser just return "Cannot GET /index.html"
Version 2.23.1 of browser-sync works as expected.
Related issue BrowserSync/browser-sync#1477
Simplest change seemed to be to limit the browser-sync version for now.