Auto enable SSR based on existence of SSR bundle #487
Merged
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.
This PR removes the
inertia.ssr.enabled
config value in favor of automatically enabling SSR based on the existence of an SSR JavaScript bundle file.By default it looks for the SSR bundle in a few common places, so quite often you won't even need to publish an Inertia config as long as you're using a pretty standard setup, such as
bootstrap/ssr/ssr.mjs
— the default location used by the Laravel Vite plugin.You can, of course, still set a custom SSR bundle path using the
inertia.ssr.bundle
config option:This PR also updates the
inertia:start-ssr
command to automatically terminate the node process should the PHP process die, as well as when the command is run, just in case there is a lingering node process hanging around still.