Include TS declarations from generated sources in node_modules_package
#17
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.
In our main repo, we have a
ts_librarytarget that includes.js,.js.map, and.d.tsfiles generated from X12 fixtures. When we updated from using rules_javascript of August 2022 to March 2025, those.d.tsfiles stopped getting included in ournode_modules_packagetarget that locally installs VSCode type hints. (Otherts_libraryandjs_import_tstargets were fine).This restores desired behavior of including type declarations from generated sources in
node_modules_packageoutput.