-
Notifications
You must be signed in to change notification settings - Fork 121
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
Jetstream routes can be accessed although I'm only using Breeze #59
Comments
Jetstream has been moved to dev dependency in Jetstrap's composer.json, so it shouldn't be included in your installation. |
Apparently it appeared? Let's say it's not included, then why is in vue the |
Ok, thanks for pointing that out, will fix this. |
I think installing Jetstrap without the --dev flag will prevent installing all its dev dependencies. Will try that out and if it fixes the problem then i'll update the docs. I think that would make steps 3 and 4 optional. |
This is causing problems for people who only use Laravel Breeze, and never install jetstream at all.
To Reproduce
I discovered this problem when I want to change the route name. I remove the route in auth.php and create a new one in web.php. Then it turns out that both old and new routes can still be reached. Why are you adding all the jetstream files in vendor\nascent-africa\jetstrap\src\NascentAfrica\Jetstrap\ for people who only use Breeze: "php artisan jetstrap:swap breeze-inertia" ?
SOLUTION
After you use this package to update to bootstrap, you can just remove it:
composer remove vendor/nascent-africa/jetstrap --dev
php artisan route:cache
if you still see the old page with error about missing controller in browser. It should show 404 | Not Found.php artisan route:list
to confirm all the other routes have been removed.div class="form-group" v-if="$page.props.jetstream.hasTermsAndPrivacyPolicyFeature">
The text was updated successfully, but these errors were encountered: