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

[1.x] Fix CORS policy errors with inertia stack #82

Merged
merged 1 commit into from
Jun 1, 2021
Merged

[1.x] Fix CORS policy errors with inertia stack #82

merged 1 commit into from
Jun 1, 2021

Conversation

ArielMejiaDev
Copy link
Contributor

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 with browserSync you must work with localhost 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 a localhost 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.

@driesvints driesvints changed the title fix cors policy errors with inertia stack [1.x] Fix CORS policy errors with inertia stack May 31, 2021
@taylorotwell taylorotwell merged commit 0769fce into laravel:1.x Jun 1, 2021
@heychazza
Copy link

Hi guys, adding this I get that the url isn't found? Should we really be hard coding to port 3000? Or rather using the .env url?

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.

3 participants