This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
Add support for patterns when specifying emitFiles #17
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
|
v2.1.0 published on npm |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It would be very useful to be able to
emitFilesbased on pattern, similar to Rollup's ownoutput.entryFileNames, etc.This PR adds basic support for templating. For consistency, I've followed similar naming convention to Rollup's options:
[hash]- The existing hash of the file contents[name]- The filename of the source file[extname]- The extension of the source file[dirname]- The directory of the file. Useful if using[name]and there are multiple files in different directoriesThe default value is
"[hash][extname]", which will ensure backwards compatibility with previous versions.