@angular/cli 13.1.0-next.3 → 13.1.0-rc.0

package/README.md

@@ -234,26 +234,26 @@ For more informations about Node.js debugging in VS Code, see the related [VS Co
 
 In order to investigate performance issues, CPU profiling is often useful.
 
-To capture a CPU profiling, you can:
+#### Creating a profile
 
-1. install the v8-profiler-node8 dependency: `npm install v8-profiler-node8 --no-save`
-1. set the NG_CLI_PROFILING Environment variable to the file name you want:
-   - on Unix systems (Linux & Mac OS X): ̀`export NG_CLI_PROFILING=my-profile`
-   - on Windows: ̀̀`setx NG_CLI_PROFILING my-profile`
+Node.js 16+ users can use the Node.js command line argument `--cpu-prof` to create a CPU profile.
 
-Then, just run the ng command on which you want to capture a CPU profile.
-You will then obtain a `my-profile.cpuprofile` file in the folder from which you ran the ng command.
+```bash
+node --cpu-prof node_modules/.bin/ng build
+```
+
+In addition to this one, another, more elaborated way to capture a CPU profile using the Chrome Devtools is detailed in https://github.com/angular/angular-cli/issues/8259#issue-269908550.
+
+#### Opening a profile
 
 You can use the Chrome Devtools to process it. To do so:
 
-1. open `chrome://inspect/#devices` in Chrome
+1. open `chrome://inspect` in Chrome
 1. click on "Open dedicated DevTools for Node"
 1. go to the "profiler" tab
-1. click on the "Load" button and select the generated .cpuprofile file
+1. click on the "Load" button and select the generated `.cpuprofile` file
 1. on the left panel, select the associated file
 
-In addition to this one, another, more elaborated way to capture a CPU profile using the Chrome Devtools is detailed in https://github.com/angular/angular-cli/issues/8259#issue-269908550.
-
 ## Documentation
 
 The documentation for the Angular CLI is located on our [documentation website](https://angular.io/cli).

package/commands/deploy-impl.d.ts

@@ -10,6 +10,6 @@ import { Arguments } from '../models/interface';
 import { Schema as DeployCommandSchema } from './deploy';
 export declare class DeployCommand extends ArchitectCommand<DeployCommandSchema> {
     readonly target = "deploy";
-    readonly missingTargetError = "\nCannot find \"deploy\" target for the specified project.\n\nYou should add a package that implements deployment capabilities for your\nfavorite platform.\n\nFor example:\n  ng add @angular/fire\n  ng add @azure/ng-deploy\n  ng add @zeit/ng-deploy\n\nFind more packages on npm https://www.npmjs.com/search?q=ng%20deploy\n";
+    readonly missingTargetError = "\nCannot find \"deploy\" target for the specified project.\n\nYou should add a package that implements deployment capabilities for your\nfavorite platform.\n\nFor example:\n  ng add @angular/fire\n  ng add @azure/ng-deploy\n\nFind more packages on npm https://www.npmjs.com/search?q=ng%20deploy\n";
     initialize(options: DeployCommandSchema & Arguments): Promise<number | void>;
 }

package/commands/deploy-impl.js

@@ -18,7 +18,6 @@ favorite platform.
 For example:
   ng add @angular/fire
   ng add @azure/ng-deploy
-  ng add @zeit/ng-deploy
 
 Find more packages on npm https://www.npmjs.com/search?q=ng%20deploy
 `;

package/commands/doc-impl.js

@@ -61,15 +61,11 @@ class DocCommand extends command_1.Command {
                 const currentNgVersion = (await Promise.resolve().then(() => __importStar(require('@angular/core')))).VERSION.major;
                 domain = `v${currentNgVersion}.angular.io`;
             }
-            catch (e) { }
+            catch { }
         }
-        let searchUrl = `https://${domain}/api?query=${options.keyword}`;
-        if (options.search) {
-            searchUrl = `https://${domain}/docs?search=${options.keyword}`;
-        }
-        await (0, open_1.default)(searchUrl, {
-            wait: false,
-        });
+        await (0, open_1.default)(options.search
+            ? `https://${domain}/api?query=${options.keyword}`
+            : `https://${domain}/docs?search=${options.keyword}`);
     }
 }
 exports.DocCommand = DocCommand;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angular/cli",
-  "version": "13.1.0-next.3",
+  "version": "13.1.0-rc.0",
   "description": "CLI tool for Angular",
   "main": "lib/cli/index.js",
   "bin": {
@@ -28,10 +28,10 @@
   },
   "homepage": "https://github.com/angular/angular-cli",
   "dependencies": {
-    "@angular-devkit/architect": "0.1301.0-next.3",
-    "@angular-devkit/core": "13.1.0-next.3",
-    "@angular-devkit/schematics": "13.1.0-next.3",
-    "@schematics/angular": "13.1.0-next.3",
+    "@angular-devkit/architect": "0.1301.0-rc.0",
+    "@angular-devkit/core": "13.1.0-rc.0",
+    "@angular-devkit/schematics": "13.1.0-rc.0",
+    "@schematics/angular": "13.1.0-rc.0",
     "@yarnpkg/lockfile": "1.1.0",
     "ansi-colors": "4.1.1",
     "debug": "4.3.3",
@@ -51,12 +51,12 @@
   "ng-update": {
     "migrations": "@schematics/angular/migrations/migration-collection.json",
     "packageGroup": {
-      "@angular/cli": "13.1.0-next.3",
-      "@angular-devkit/architect": "0.1301.0-next.3",
-      "@angular-devkit/build-angular": "13.1.0-next.3",
-      "@angular-devkit/build-webpack": "0.1301.0-next.3",
-      "@angular-devkit/core": "13.1.0-next.3",
-      "@angular-devkit/schematics": "13.1.0-next.3"
+      "@angular/cli": "13.1.0-rc.0",
+      "@angular-devkit/architect": "0.1301.0-rc.0",
+      "@angular-devkit/build-angular": "13.1.0-rc.0",
+      "@angular-devkit/build-webpack": "0.1301.0-rc.0",
+      "@angular-devkit/core": "13.1.0-rc.0",
+      "@angular-devkit/schematics": "13.1.0-rc.0"
     }
   },
   "engines": {