[10.x] Make Vite throw a new ManifestNotFoundException
#47681
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.
What
This pull request introduces a new
ManifestNotFoundException
that simply extends\Exception
.It's used instead of the base
\Exception
that is thrown when the Vite manifest cannot be found.Why
I have specific exception handling in all my projects using Inertia or Hybridly: I don't want to display my custom error page for this error, since it won't be able to be rendered due to Vite not being started.
I currently use the following:
I believe having a specific exception would make this kind of logic more reliable. This is not specific to my projects' exception handling, it could also be used in Ignition as well, for instance.