feat!: support redirect.asset.path
and redirect.asset.extension
#1119
+267
−24
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.
Summary
Small breaking changes about
redirect.asset
.boolean
->{ path?: boolean; extension?: boolean; }
redirect.asset
Controls the redirect of the import paths of output asset files.
redirect.asset.path
Whether to automatically redirect the import paths of asset output files.
boolean
true
When set to
true
, the relevant redirect rules are the same asredirect.js.path
.When set to
false
, the original import path will remain unchanged.redirect.asset.extension
Whether to automatically redirect the file extension to import paths based on the asset output files.
boolean
true
When set to
true
, the paths of imported asset files will be redirected to the corresponding JavaScript output file.When set to
false
, the file extension will remain unchanged from the original import path.Related Links
Checklist