feat: add package_visibility attribute to npm_translate_lock and npm_import #1302
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.
Request from a consulting client.
Since link targets are generated by
npm_translate_lock
andnpm_import
repository rules, customizable visibility for link targets must be annpm_translate_lock
andnpm_import
attributes. There is no way to set a visibility on annpm_package
target that could be propagated to the visibility of a link target that uses thatnpm_package
target via the virtual store link.Type of change
Test plan