feat: gather config dependencies when config is a js_library #247
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.


Allows esbuild config attribute to accept a js_library target, automatically including its dependencies (e.g., esbuild plugins) in the build without manually adding them to srcs.
This fixes the issue where config files with dependencies required users to manually specify those dependencies in the esbuild rule's srcs attribute.
Changes are visible to end-users: yes
config files have their transitive dependencies propagated to esbuild
Test plan