Fix: file name generation in build dir#22
Merged
stackmystack merged 2 commits intomasterfrom Apr 8, 2025
Merged
Conversation
Then copy that file to its destination. PR: #22
Since we're generating the exact file as `prefix + name + ext` in the build dir, we rely on that name to copy to output dir. If that name is not present, because the user defined a user script like make mostly (like in typescript), then take the first match and work with that. PR: #22
080a234 to
6552949
Compare
stackmystack
added a commit
that referenced
this pull request
Apr 8, 2025
Then copy that file to its destination. PR: #22
This file contains hidden or 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.
prefix + name + extfile directly in the build dirdllin the target dir, and copy it if it's the only file there. This is mostly useful for parsers with custom scripts like make (e.g. typescript).