build: workaround for creating ng_package on windows

Workaround for angular/angular#32603

Author: devversion

WORKSPACE

@@ -44,6 +44,7 @@ yarn_install(
         "//:angular-tsconfig.json",
         "//:tools/bazel/flat_module_factory_resolution.patch",
         "//:tools/bazel/postinstall-patches.js",
+        "//:tools/bazel/rollup_windows_arguments.patch",
         "//:tools/npm/check-npm.js",
     ],
     package_json = "//:package.json",

tools/bazel/postinstall-patches.js

@@ -81,3 +81,9 @@ shelljs.sed('-i',
 shelljs.sed('-i', /("metadata": outs.metadata),/,
   `$1 + [m for dep in ctx.attr.deps if hasattr(dep, "angular") for m in dep.angular.metadata],`,
   'node_modules/@angular/bazel/src/ng_module.bzl');
+
+// Workaround for https://github.com/angular/angular/issues/32603. Note that we don't
+// want to apply the patch if it has been applied already.
+if (!shelljs.test('-f', 'node_modules/@angular/bazel/src/ng_package/rollup_bin.js')) {
+  shelljs.cat(path.join(__dirname, './rollup_windows_arguments.patch')).exec('patch -p0');
+}

tools/bazel/rollup_windows_arguments.patch

@@ -0,0 +1,63 @@
+diff --git node_modules/@angular/bazel/src/ng_package/_BUILD.bazel node_modules/@angular/bazel/src/ng_package/_BUILD.bazel
+index e7cf3d9..1887e95 100644
+--- node_modules/@angular/bazel/src/ng_package/_BUILD.bazel
++++ node_modules/@angular/bazel/src/ng_package/_BUILD.bazel
+@@ -2,6 +2,14 @@ package(default_visibility = ["//visibility:public"])
+
+ load("@build_bazel_rules_nodejs//:defs.bzl", "nodejs_binary")
+
++nodejs_binary(
++    name = "rollup_bin",
++    entry_point = "rollup_bin.js",
++    data = [
++        "rollup_bin.js",
++    ],
++    node_modules = "@build_bazel_rules_nodejs_rollup_deps//:node_modules",
++)
+
+ nodejs_binary(
+     name = "packager",
+diff --git node_modules/@angular/bazel/src/ng_package/ng_package.bzl node_modules/@angular/bazel/src/ng_package/ng_package.bzl
+index f3104f0..bb0c04f 100644
+--- node_modules/@angular/bazel/src/ng_package/ng_package.bzl
++++ node_modules/@angular/bazel/src/ng_package/ng_package.bzl
+@@ -102,6 +102,13 @@ def _rollup(ctx, bundle_name, rollup_config, entry_point, inputs, js_output, for
+     map_output = ctx.actions.declare_file(js_output.basename + ".map", sibling = js_output)
+
+     args = ctx.actions.args()
++
++    # Pass arguments through a parameter file. This is necessary because on Windows there is
++    # an argument limit and we there might be a lot of globals which need to be passed to
++    # rollup. We always enable it because Bazel is not able to properly detect the argument limit.
++    # Read more here: https://docs.bazel.build/versions/master/skylark/lib/Args.html#use_param_file
++    args.use_param_file(param_file_arg = "%s", use_always = True)
++
+     args.add("--config", rollup_config)
+
+     args.add("--input", entry_point)
+@@ -435,7 +442,7 @@ NG_PACKAGE_ATTRS = dict(NPM_PACKAGE_ATTRS, **dict(ROLLUP_ATTRS, **{
+         cfg = "host",
+     ),
+     "_rollup": attr.label(
+-        default = Label("@build_bazel_rules_nodejs//internal/rollup"),
++        default = Label("@npm_angular_bazel//src/ng_package:rollup_bin"),
+         executable = True,
+         cfg = "host",
+     ),
+diff --git node_modules/@angular/bazel/src/ng_package/rollup_bin.js node_modules/@angular/bazel/src/ng_package/rollup_bin.js
+new file mode 100644
+index 0000000..9395677
+--- /dev/null
++++ b/rollup_bin.js
+@@ -0,0 +1,11 @@
++const fs = require('fs');
++
++const args = process.argv.slice(2);
++const rollupArgs = fs.readFileSync(args[0], 'utf8').trim().split('\n');
++
++// Overwrite the process arguments so that the rollup binary uses the
++// proper argument passed from the Bazel action.
++process.argv = [process.argv[0], process.argv[1], ...rollupArgs];
++
++// Run rollup by requiring the binary entry-point.
++require('rollup/bin/rollup');