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

Revert "fix cors policy errors with inertia stack (#797)" #883

Closed

Conversation

DSpeichert
Copy link

Attempting to load browser-sync-client.js without it being used in
Jetstream by default results in blocked JS execution until timeout.

Fixes #850

Attempting to load browser-sync-client.js without it being used in
Jetstream by default results in blocked JS execution until timeout.
@taylorotwell
Copy link
Member

It is to support Mix's npm run hot out of the box for browser reloading.

@DSpeichert
Copy link
Author

DSpeichert commented Sep 17, 2021

@taylorotwell But npm run hot does not actually start the browsersync server component (nothing is listening on port 3000).
browser-sync is not in package.json or package-lock.json for a fresh project bootstrapped from jetstream at this point.

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.

BrowserSync Error on fresh installation
2 participants