docs: document exclude_types_from_npm_packages as deprecated #2014
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.
With
js_library
always being recommended I thinknpm_package
should be used almost exclusively for creating packages ready to be published and not for use as a runtime/type-checking dependency within the workspace.The only remaining use case I can see for using
npm_package
instead ofjs_library
would be to properly test a package in the same state it would be published. In that case this flag may still be useful, but is it worth maintaining for that use case?Changes are visible to end-users: yes
Deprecate
--@aspect_rules_js//npm:exclude_types_from_npm_packages
.Test plan