feat(esbuild): add option to disable metafile generation #3066
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
mgred
force-pushed
the
feat-eslint-optional-metafile
branch
from
3c2ccf6
to
d2504f2
Compare
mgred
changed the title
mgred
force-pushed
the
feat-eslint-optional-metafile
branch
from
d2504f2
to
107b4aa
Compare
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
esbuildalways generates*._metadata.jsonfile.What is the new behavior?
The new option
metafilecan turn of generation of the metafile.This might be useful if one would like to inject the output into html as possible with
@bazel/rollup.Does this PR introduce a breaking change?