feat(builtin): rename @nodejs//:npm and @nodejs//:yarn to @nodejs//:[…

…yarn/npm]_node_repositories

Also,

* create @nodejs//:npm_bin, @nodejs//:npx_bin & @nodejs//:yarn_bin targets
* create @nodejs//:node_files, @nodejs//:npm_files & @nodejs//:yarn_files filegroups
* cleanup & simplify node_repositories.bzl code
* cleanup & simplify @nodejs//:BUILD.bazel file

BREAKING CHANGES:

bazel run @nodejs//:npm is replaced with bazel run @nodejs//:npm_node_repositories and bazel run @nodejs//:yarn is replaced with bazel run @nodejs//:yarn_node_repositories. @nodejs//:yarn and @nodejs//:npm now run yarn & npm in the current working directory instead of on all of the package.json files in node_repositories().

@nodejs//:bin/node & @nodejs//:bin/node.cmd (on Windows) are no longer valid targets. Use @nodejs//:node instead on all platforms. You can still call the old targets in their platform specific node repositories such as @nodejs_darwin_amd64//:bin/node.

@nodejs//:bin/yarn & @nodejs//:bin/yarn.cmd (on Windows) are no longer valid targets. Use @nodejs//:yarn instead on all platforms. You can still call the old targets in their platform specific node repositories such as @nodejs_darwin_amd64//:bin/yarn.

@nodejs//:bin/npm & @nodejs//:bin/npm.cmd (on Windows) are no longer valid targets. Use @nodejs//:npm instead on all platforms. You can still call the old targets in their platform specific node repositories such as @nodejs_darwin_amd64//:bin/npm.
[dc57136] feat(builtin): create @nodejs//:npm_bin, @nodejs//:npx_bin & @nodejs//:yarn_bin targets

.bazelci/presubmit.yml

@@ -4,7 +4,7 @@ tasks:
     name: ubuntu1604
     platform: ubuntu1604
     run_targets:
-    - "@nodejs//:yarn"
+    - "@nodejs//:yarn_node_repositories"
     - "//internal/node/test:no_deps"
     - "//internal/node/test:has_deps_legacy"
     - "//internal/node/test:has_deps"
@@ -79,7 +79,7 @@ tasks:
     name: ubuntu1804
     platform: ubuntu1804
     run_targets:
-    - "@nodejs//:yarn"
+    - "@nodejs//:yarn_node_repositories"
     - "//internal/node/test:no_deps"
     - "//internal/node/test:has_deps_legacy"
     - "//internal/node/test:has_deps"
@@ -194,7 +194,7 @@ tasks:
     name: macos
     platform: macos
     run_targets:
-    - "@nodejs//:yarn"
+    - "@nodejs//:yarn_node_repositories"
     - "//internal/node/test:no_deps"
     - "//internal/node/test:has_deps_legacy"
     - "//internal/node/test:has_deps"
@@ -291,7 +291,7 @@ tasks:
     name: windows
     platform: windows
     run_targets:
-    - "@nodejs//:yarn"
+    - "@nodejs//:yarn_node_repositories"
     - "//internal/node/test:no_deps"
     - "//internal/node/test:has_deps_legacy"
     - "//internal/node/test:has_deps"

.circleci/config.yml

@@ -106,8 +106,8 @@ jobs:
       - *yarn_install
       - *init_bazel
 
-      # Run yarn on all node_repositories
-      - run: bazel run @nodejs//:bin/yarn
+      # Run yarn
+      - run: bazel run @nodejs//:yarn
 
       # Save all node_modules to the cache
       - save_cache:
@@ -236,7 +236,7 @@ jobs:
       # We should also be able to test targets in a different workspace
       # TODO(gmagolan): move these tests into `build` job once
       # https://github.com/bazelbuild/bazel/issues/6481 is resolved
-      - run: 'cd examples/user_managed_deps && bazel run @nodejs//:yarn'
+      - run: 'cd examples/user_managed_deps && bazel run @nodejs//:yarn_node_repositories'
       - run: bazel test @examples_user_managed_deps//...
       - run: bazel test @e2e_packages//...
 

docs/Built-ins.md

@@ -35,8 +35,8 @@ to point to those before calling node_repositories.
 This rule exposes the `@nodejs` workspace containing some rules the user can call later:
 
 - Run node: `bazel run @nodejs//:node path/to/program.js`
-- Install dependencies using npm: `bazel run @nodejs//:npm install`
-- Install dependencies using yarn: `bazel run @nodejs//:yarn`
+- Install dependencies using npm: `bazel run @nodejs//:npm_node_repositories install`
+- Install dependencies using yarn: `bazel run @nodejs//:yarn_node_repositories`
 
 Note that the dependency installation scripts will run in each subpackage indicated by the `package_json` attribute.
 
@@ -50,7 +50,7 @@ load("@build_bazel_rules_nodejs//:index.bzl", "node_repositories")
 node_repositories(package_json = ["//:package.json", "//subpkg:package.json"])
 ```
 
-Running `bazel run @nodejs//:yarn` in this repo would create `/node_modules` and `/subpkg/node_modules`.
+Running `bazel run @nodejs//:yarn_node_repositories` in this repo would create `/node_modules` and `/subpkg/node_modules`.
 
 
 
@@ -114,7 +114,7 @@ and expect that file to have sha256sum `00b7a8426e076e9bf9d12ba2d571312e833fe962
 #### `package_json`
 (*[labels]*): a list of labels, which indicate the package.json files that will be installed
             when you manually run the package manager, e.g. with
-            `bazel run @nodejs//:yarn` or `bazel run @nodejs//:npm install`.
+            `bazel run @nodejs//:yarn_node_repositories` or `bazel run @nodejs//:npm_node_repositories install`.
             If you use bazel-managed dependencies, you can omit this attribute.
 
 
@@ -777,7 +777,7 @@ Actually publish the package with `npm publish` (also builds first):
 
 ```sh
 # Check login credentials
-$ bazel run @nodejs//:npm who
+$ bazel run @nodejs//:npm_node_repositories who
 # Publishes the package
 $ bazel run :my_package.publish
 ```

docs/TypeScript.md

@@ -107,7 +107,7 @@ node_repositories(package_json = ["//:package.json"])
 You can then run `yarn` in your workspace with:
 
 ```sh
-$ bazel run @nodejs//:yarn
+$ bazel run @nodejs//:yarn_node_repositories
 ```
 
 To use your workspace `node_modules` folder as a dependency in `ts_library` and

docs/install.md

@@ -385,16 +385,16 @@ To use the Yarn package manager, which we recommend for its built-in
 verification command, you can run:
 
 ```sh
-$ bazel run @nodejs//:yarn
+$ bazel run @nodejs//:yarn_node_repositories
 ```
 
 If you use npm instead, run:
 
 ```sh
-$ bazel run @nodejs//:npm install
+$ bazel run @nodejs//:npm_node_repositories install
 ```
 
-The `@nodejs//:yarn` and `@nodejs//:npm` targets will run yarn/npm on all of the
+The `@nodejs//:yarn_node_repositories` and `@nodejs//:npm_node_repositories` targets will run yarn/npm on all of the
 package.json contexts listed `package_json` attribute of the `node_repositories`
 repository rule in your WORKSPACE file (`node_repositories(package_json = [...])`).
 
@@ -403,22 +403,20 @@ run the bazel managed yarn or npm on a single context this can be done
 using the following targets:
 
 ```sh
-$ bazel run @nodejs//:bin/yarn -- <arguments passed to yarn>
+$ bazel run @nodejs//:yarn -- <arguments passed to yarn>
 ```
 
 If you use npm instead, run:
 
 ```sh
-$ bazel run @nodejs//:bin/npm -- <arguments passed to npm>
+$ bazel run @nodejs//:npm -- <arguments passed to npm>
 ```
 
-Note: on **Windows** the targets are `@nodejs//:bin/yarn.cmd` and `@nodejs//:bin/npm.cmd`.
-
 This will run yarn/npm in the current working directory. To add a package with the `yarn add` command,
 for example, you would use:
 
 ```sh
-$ bazel run @nodejs//:bin/yarn -- add <package>
+$ bazel run @nodejs//:yarn -- add <package>
 ```
 
 Note: the arguments passed to `bazel run` after `--` are forwarded to the executable being run.

e2e/BUILD.bazel

@@ -121,8 +121,8 @@ e2e_integration_test(
 e2e_integration_test(
     name = "e2e_ts_auto_deps",
     bazel_commands = [
-        "run @nodejs//:yarn",
-        "run @nodejs//:bin/yarn -- generate_build_file",
+        "run @nodejs//:yarn_node_repositories",
+        "run @nodejs//:yarn -- generate_build_file",
         "build //simple:simple",
     ],
     npm_packages = {

e2e/ts_auto_deps/package.json

@@ -4,7 +4,7 @@
     "typescript": "2.9.2"
   },
   "scripts": {
-    "pretest": "bazel run @nodejs//:yarn",
+    "pretest": "bazel run @nodejs//:yarn_node_repositories",
     "generate_build_file": "cd simple && ts_auto_deps",
     "test": "yarn generate_build_file && bazel build simple"
   }

examples/BUILD.bazel

@@ -191,9 +191,9 @@ example_integration_test(
 
 example_integration_test(
     name = "examples_user_managed_deps",
-    # This test requires calling `bazel run @nodejs//:yarn` before `bazel test ...`
+    # This test requires calling `bazel run @nodejs//:yarn_node_repositories` before `bazel test ...`
     bazel_commands = [
-        "run @nodejs//:yarn",
+        "run @nodejs//:yarn_node_repositories",
         "test ...",
     ],
     # replace the following repositories with the generated archives

examples/user_managed_deps/WORKSPACE

@@ -19,14 +19,14 @@ load("@build_bazel_rules_nodejs//:index.bzl", "node_repositories")
 # - NodeJS:
 #   @nodejs//:node
 # - NPM:
-#   @nodejs//:npm
+#   @nodejs//:npm_node_repositories
 # - The yarn package manager:
-#   @nodejs//:yarn
+#   @nodejs//:yarn_node_repositories
 #
 # To install the node_modules of all the listed package_json files run:
-#   bazel run @nodejs//:yarn
+#   bazel run @nodejs//:yarn_node_repositories
 # or
-#   bazel run @nodejs//:npm
+#   bazel run @nodejs//:npm_node_repositories
 node_repositories(
     package_json = ["//:package.json"],
 )

examples/user_managed_deps/package.json

@@ -5,7 +5,7 @@
     "v8-coverage": "1.0.9"
   },
   "scripts": {
-    "pretest": "bazel run @nodejs//:yarn",
+    "pretest": "bazel run @nodejs//:yarn_node_repositories",
     "test": "bazel test ..."
   }
 }

internal/node/BUILD.bazel

@@ -31,7 +31,6 @@ exports_files([
     "node_repositories.bzl",  # Exported to be consumed for generating skydoc.
     "node_launcher.sh",
     "node_loader.js",
-    "BUILD.nodejs_host_os_alias.tpl",
 ])
 
 filegroup(
@@ -42,7 +41,6 @@ filegroup(
         "*.sh",
     ]) + [
         "BUILD.bazel",
-        "BUILD.nodejs_host_os_alias.tpl",
     ],
     visibility = ["//:__pkg__"],
 )