[1.x] Hot file monitoring #323
Draft
Conversation
This file contains 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
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 allows 3rd party tools, such as Expose, to control the URL in the hot file. The URL in the hot file is used by both Laravel and Vite when rendering URLs to the Vite server.
When the URL in the hot file is updated, the plugin will use the new URL when rendering URLs in JS and CSS assets. It will also perform a full page reload when the hot file is updated which should be a nice DX, e.g., when Expose starts it can write a new URL to the hot file, handle proxying that URL back to the Vite server, and the page will refresh to start using the new dev server URL all automatically.
An example log, which matches how Vite formats their log messages for similar events: