Support TypeScript and preprocessor file extensions in asset autoloading #150
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.
Problem
The current asset autoloading implementation only supports
.jsand.cssfile extensions when reading from the Vite manifest. This causes issues when using:.ts,.tsx).scss,.sass,.less)For example, when
vite.config.jshas an entry like:The manifest.json contains:
But the current code checks
Str::endsWith($src, '.js')which returns false for.tsfiles, so these assets are not loaded.Solution
Updated the
BlastServiceProviderto support additional file extensions:.js,.ts,.jsx,.tsx.css,.scss,.sass,.lessTesting
Tested with a Laravel project using:
vite.config.jsinputvite.config.jsinputphp artisan blast:publishsuccessfully loads all assetsBackward Compatibility
This change is backward compatible as it only adds support for additional extensions without changing existing behavior.