Fix: Remove bootstrap.js import for Laravel 13+ in Inertia stack#1602
Merged
taylorotwell merged 2 commits intoMay 19, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When installing the Jetstream Inertia stack on a fresh Laravel 13 application, the installation currently fails when running
npm run build.Because Laravel 13 no longer includes the
resources/js/bootstrap.jsfile by default, the Jetstream installer stubbing outimport './bootstrap';inresources/js/app.jscauses Vite to throw an[UNRESOLVED_IMPORT]error.This PR adds a version check during the Inertia installation process. If the application is running Laravel 13 or higher, the import line is dynamically removed from the copied
app.jsfile, allowing Vite to build successfully.Note regarding the Livewire stack: I only applied this change to the Inertia installation logic. The Livewire stack does not copy a custom
app.jsstub (it relies on the default framework skeleton), so it does not suffer from this bug and did not need to be updated.