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

mix.browserSync(); doesn't work #1205

Closed
delmicio opened this issue Oct 23, 2017 · 3 comments
Closed

mix.browserSync(); doesn't work #1205

delmicio opened this issue Oct 23, 2017 · 3 comments
Labels

Comments

@delmicio
Copy link

Info:

  • Docker version: 17.09.0-ce-win33 (13620)
  • System info (Mac, PC, Linux): PC Win 10

Issue:

mix.browserSync(); doesn't work and there is no instructions on how to use.


Expected behavior:

Adding mix.browserSync(); should work on localhost:3000


Reproduce:

add mix.browserSync(); to you webpack.mix.js
run npm run watch inside workspace container

[Browsersync] Proxying: http://app.dev
[Browsersync] Access URLs:
 -----------------------------------
       Local: http://localhost:3000
    External: http://172.19.0.2:3000
 -----------------------------------
          UI: http://localhost:3001
 UI External: http://172.19.0.2:3001
 -----------------------------------
[Browsersync] Watching files...
[Browsersync] Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false)

goto http://localhost:3000 and nothing

@Harti
Copy link

Harti commented Oct 26, 2017

Someone already found a solution in #640, but never posted the exact steps to reproduce it.

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants