Flag --incompatible_config_setting_private_default_visibility will break rules_nodejs in Bazel 7.0

[keertk]

Incompatible flag --incompatible_config_setting_private_default_visibility will be enabled by default in the next major release (Bazel 7.0), thus breaking rules_nodejs. Please migrate to fix this and unblock the flip of this flag.

The flag is documented here: bazelbuild/bazel#12933.

Please check the following CI builds for build and test results:

• MacOS, OpenJDK 11
• MacOS, OpenJDK 11
• MacOS, OpenJDK 11
• RBE (Ubuntu 16.04, OpenJDK 8)
• Ubuntu 18.04, OpenJDK 11
• Ubuntu 18.04, OpenJDK 11
• Ubuntu 18.04, OpenJDK 11
• Ubuntu 18.04, OpenJDK 11
• Windows, OpenJDK 11
• Windows, OpenJDK 11
• Windows, OpenJDK 11

Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 6 months. It will be closed if no further activity occurs in 30 days. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs!

[sgowroji]

We are closing this issue as we can see no errors in the CI https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/1536#0188747c-5ad8-4e0d-a2c9-cc845ff4b058