[12.x] Custom public path resolver for Vite assets #57289
Closed
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.
Current state
Vite::content()
, introduced in 10.x, allows inlining raw contents of Vite assetspublic_path
Proposed change
$vite->createPublicPathsUsing(fn ($path) => $path)
$vite->createAssetPathsUsing()
for a consistent API: one for URLs, one for disk pathsExample use case
file
property:assets/font.356cadeb.woff
assets/font.woff?v=356cadeb
file
key as it is used to construct both the URL and the disk pathBackward compatibility
public_path
Tests