build: set symlink_node_modules = False for yarn_install in main WORK…

…SPACE and bazel schematics

This is needed to work-around issue: yarn_install & npm_install with managed directories can't handle deleted or manually regenerated node_modules folder [bazel-contrib/rules_nodejs#802]
Underlying issue has been fixed in Bazel bazelbuild/bazel#8487 but hasn't landed in a release yet

WORKSPACE

@@ -65,7 +65,19 @@ node_repositories(
 
 yarn_install(
     name = "npm",
+    data = [
+        "//:tools/npm/@angular_bazel/index.js",
+        "//:tools/npm/@angular_bazel/package.json",
+        "//:tools/postinstall-patches.js",
+        "//:tools/yarn/check-yarn.js",
+    ],
     package_json = "//:package.json",
+    # Don't install devDependencies, they are large and not used under Bazel
+    prod_only = True,
+    # Temporarily disable node_modules symlinking until the fix for
+    # https://github.com/bazelbuild/bazel/issues/8487 makes it into a
+    # future Bazel release
+    symlink_node_modules = False,
     yarn_lock = "//:yarn.lock",
 )
 

packages/bazel/src/builders/files/WORKSPACE.template

@@ -52,7 +52,12 @@ Try running `yarn bazel` instead.
 )
 yarn_install(
     name = "npm",
+    data = ["//:angular-metadata.tsconfig.json"],
     package_json = "//:package.json",
+    # Temporarily disable node_modules symlinking until the fix for
+    # https://github.com/bazelbuild/bazel/issues/8487 makes it into a
+    # future Bazel release
+    symlink_node_modules = False,
     yarn_lock = "//:yarn.lock",
 )