build: convert release package build scripts to typescript (angular#46456)

Follow-up to: cce395a.

PR Close angular#46456

Author: devversion

.bazelrc

@@ -53,8 +53,8 @@ build:release --workspace_status_command="yarn -s ng-dev release build-env-stamp
 build:release --stamp
 
 # Snapshots should also be stamped with version control information.
-build:snapshot --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=snapshot"
-build:snapshot --stamp
+build:snapshot-build --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=snapshot"
+build:snapshot-build --stamp
 
 ###############################
 # Output                      #

.circleci/config.yml

@@ -442,7 +442,7 @@ jobs:
     steps:
       - custom_attach_workspace
       - init_environment
-      - run: node scripts/build/build-packages-dist.js
+      - run: yarn build
 
       # Save the npm packages from //packages/... for other workflow jobs to read
       - persist_to_workspace:

.ng-dev/release.mts

@@ -1,5 +1,4 @@
 import {ReleaseConfig} from '@angular/dev-infra-private/ng-dev';
-import {join} from 'path';
 
 /** Configuration for the `ng-dev release` command. */
 export const release: ReleaseConfig = {
@@ -24,12 +23,10 @@ export const release: ReleaseConfig = {
     {name: '@angular/upgrade'},
   ],
   buildPackages: async () => {
-    // The buildTargetPackages function is loaded at runtime as the loading the script causes an
-    // invocation of bazel.
-    const packageBuilder = await import('../scripts/build/package-builder.js');
-
-    return packageBuilder.default.buildTargetPackages(
-      'dist/release-output', 'Release', /* isRelease */ true);
+    // The buildTargetPackages function is loaded at runtime as the loading the script
+    // causes an invocation of Bazel.
+    const {performNpmReleaseBuild} = await import('../scripts/build/package-builder.mjs');
+    return performNpmReleaseBuild();
   },
   releaseNotes: {
     hiddenScopes: ['aio', 'bazel', 'dev-infra', 'docs-infra', 'zone.js', 'devtools'],

aio/tools/ng-packages-installer/index.js

@@ -16,8 +16,7 @@ const ANGULAR_ROOT_DIR = path.resolve(__dirname, '../../..');
 const ANGULAR_DIST_PACKAGES_DIR = path.join(ANGULAR_ROOT_DIR, 'dist/packages-dist');
 const AIMWA_DIST_PACKAGES_DIR = path.join(ANGULAR_ROOT_DIR, 'dist/angular-in-memory-web-api-dist');
 const ZONEJS_DIST_PACKAGES_DIR = path.join(ANGULAR_ROOT_DIR, 'dist/zone.js-dist');
-const DIST_PACKAGES_BUILD_SCRIPT = path.join(ANGULAR_ROOT_DIR, 'scripts/build/build-packages-dist.js');
-const DIST_PACKAGES_BUILD_CMD = `"${process.execPath}" "${DIST_PACKAGES_BUILD_SCRIPT}"`;
+const DIST_PACKAGES_BUILD_CMD = 'yarn -s build';
 
 /**
  * A tool that can install Angular/Zone.js dependencies for a project from NPM or from the
@@ -181,14 +180,14 @@ class NgPackagesInstaller {
     const canBuild = process.platform !== 'win32';
 
     if (canBuild) {
-      this._log(`Building the local packages with: ${DIST_PACKAGES_BUILD_SCRIPT}`);
-      shelljs.exec(DIST_PACKAGES_BUILD_CMD);
+      this._log(`Building the local packages with: ${DIST_PACKAGES_BUILD_CMD} in ${ANGULAR_ROOT_DIR}`);
+      shelljs.exec(DIST_PACKAGES_BUILD_CMD, {cwd: ANGULAR_ROOT_DIR});
     } else {
       this._warn([
         'Automatically building the local Angular/angular-in-memory-web-api/zone.js packages is currently not ' +
           'supported on Windows.',
         `Please, ensure '${ANGULAR_DIST_PACKAGES_DIR}', '${AIMWA_DIST_PACKAGES_DIR}' and ` +
-          `'${ZONEJS_DIST_PACKAGES_DIR}' exist and are up-to-date (e.g. by running '${DIST_PACKAGES_BUILD_SCRIPT}' ` +
+          `'${ZONEJS_DIST_PACKAGES_DIR}' exist and are up-to-date (e.g. by running "${DIST_PACKAGES_BUILD_CMD}" ` +
           'in Git Bash for Windows, Windows Subsystem for Linux or a Linux docker container or VM).',
         '',
         'Proceeding anyway...',

aio/tools/ng-packages-installer/index.spec.js

@@ -305,25 +305,20 @@ describe('NgPackagesInstaller', () => {
     };
 
     it('should build the local packages, when not on Windows', () => {
-      const buildScript = path.join(ngRootDir, 'scripts/build/build-packages-dist.js');
-      const buildCmd = `"${process.execPath}" "${buildScript}"`;
+      const buildCmd = 'yarn -s build';
 
       buildDistPackagesOnPlatform('linux');
-      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd);
+      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd, {cwd: ngRootDir});
 
       shelljs.exec.calls.reset();
 
       buildDistPackagesOnPlatform('darwin');
-      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd);
+      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd, {cwd: ngRootDir});
 
       shelljs.exec.calls.reset();
 
       buildDistPackagesOnPlatform('anythingButWindows :(');
-      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd);
-
-      // Ensure that the script does actually exist (e.g. it was not renamed/moved).
-      fs.existsSync.and.callThrough();
-      expect(fs.existsSync(buildScript)).toBe(true);
+      expect(shelljs.exec).toHaveBeenCalledWith(buildCmd, {cwd: ngRootDir});
     });
 
     it('should print a warning, when on Windows', () => {

devtools/src/BUILD.bazel

@@ -283,7 +283,7 @@ pkg_web(
         "@npm//:node_modules/tslib/tslib.js",
     ],
     # Currently, ibazel doesn't allow passing in flags to bazel run.
-    # This means we are not able to use --config snapshot
+    # This means we are not able to use --config snapshot-build
     # to access the current commit SHA.
     # Since we still want to be able to use ibazel to speed up
     # local development, we supply an empty string for the SHA substitution.

docs/BAZEL.md

@@ -297,7 +297,7 @@ The `msys64` library and associated tools (like `mkdir`) are required to build A
 
 Make sure you have `C:\msys64\usr\bin` in the "system" `PATH` rather than the "user" `PATH`.
 
-After that, a `git clean -xfd`, `yarn`, and `node scripts\build\build-packages-dist.js` should resolve this issue.
+After that, a `git clean -xfd`, `yarn`, and `yarn build` should resolve this issue.
 
 ### Xcode
 

docs/DEBUG_COMPONENTS_REPO_IVY.md

@@ -4,8 +4,7 @@ Currently all changes to Ivy are validated against the test suite of the
 `angular/components` repository. In order to debug the `components-repo-unit-tests` CI
 job, the following steps can be used:
 
-1\) Build the Ivy package output by running `node ./scripts/build/build-packages-dist.js` in
-the `angular/angular` repo.
+1\) Build the Ivy package output by running `yarn build` in the `angular/angular` repo.
 
 2\) Clone the `angular/components` repository if not done yet ([quick link to repo](https://github.com/angular/components)).
 

docs/DEVELOPER.md

@@ -67,7 +67,7 @@ yarn install
 To build Angular run:
 
 ```shell
-node ./scripts/build/build-packages-dist.js
+yarn build
 ```
 
 * Results are put in the `dist/packages-dist` folder.
@@ -197,7 +197,7 @@ c. Some package managers (such as `pnpm` or `yarn pnp`) might not work correctly
 ### Publishing to GitHub Repos
 You can also manually publish `*-builds` snapshots just like our CircleCI build does for upstream
 builds. Before being able to publish the packages, you need to build them locally by running the
-`./scripts/build/build-packages-dist.js` script.
+`yarn build` command.
 
 First time, you need to create the GitHub repositories:
 

integration/README.md

@@ -4,7 +4,7 @@ This directory contains end-to-end tests for Angular. Each directory is a self-c
 that exactly mimics how a user might expect Angular to work, so they allow high-fidelity
 reproductions of real-world issues.
 
-For this to work, we first build the Angular distribution via `./scripts/build/build-packages-dist.js`, then
+For this to work, we first build the Angular distribution via `yarn build`, then
 install the distribution into each app.
 
 To test Angular CLI applications, we use the `cli-hello-world-*` integration tests.