This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
Remove --incompatible_depset_is_not_iterable #471
Closed
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.
Remove this flag from the .bazelrc.
Bazel no longer supports this flag, see bazelbuild/bazel#5816
Attention Googlers: This repo has its Source of Truth in Piper. After sending a PR, you can follow http://g3doc/third_party/bazel_rules/rules_typescript/README.google.md#merging-changes to get your change merged.
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?
Using Bazel built from bazelbuild/bazel@8f075d2,
bazel-head info
breaks. Culprit is Bazel no longer supports--incompatible_depset_is_not_iterable
, added here:rules_typescript/.bazelrc
Line 15 in 62bbdc8
Issue Number: N/A
Did not open any issue, because the bug template asks to open issues with rules_nodejs, but the bug is specific to this repo.
What is the new behavior?
bazel-head info
works.Does this PR introduce a breaking change?
Other information