[1.x] Fix CORS policy errors with inertia stack #82
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.
Description
Quick note
this pull request reflects the same change that has jetstream on inertia stack that is already merged fix cors policy errors with inertia stack #797
on inertia stack a when you run
npm install && npm run watch
if you work with.test
domains like Laravel Valet add, the watcher does not add live reload withbrowserSync
you must work withlocalhost
ip to work with vue components.to avoid this by adding this tag on
app.blade.php
file on inertia stack it would reload.test
domains as it is alocalhost
domain.How it help the end user
it avoid confusion on why vue components does not reload using browserSync by default, and make easier the workflow with inertia and of course with jetstream.