fix(@angular/cli): handle project being passed as a flag

Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project.

Closes angular#23291

Author: alan-agius4

packages/angular/cli/src/command-builder/architect-command-module.ts

@@ -94,16 +94,18 @@ export abstract class ArchitectCommandModule
   }
 
   private getArchitectProject(): string | undefined {
-    const workspace = this.context.workspace;
-    if (!workspace) {
-      return undefined;
-    }
-
-    const [, projectName] = this.context.args.positional;
+    const { options, positional } = this.context.args;
+    const [, projectName] = positional;
 
     if (projectName) {
-      return workspace.projects.has(projectName) ? projectName : undefined;
+      return projectName;
     }
+
+    // Yargs allows positional args to be used as flags.
+    if (typeof options['project'] === 'string') {
+      return options['project'];
+    }
+
     const target = this.getArchitectTarget();
     const projectFromTarget = this.getProjectNamesByTarget(target);
 

tests/legacy-cli/e2e/tests/commands/builder-project-by-cwd.ts

@@ -8,6 +8,8 @@ export default async function () {
   const startCwd = process.cwd();
 
   try {
+    await ng('build', '--project=second-app', '--configuration=development');
+
     // When no project is provided it should favor the project that is located in the current working directory.
     process.chdir(join(startCwd, 'projects/second-app'));
     await ng('build', '--configuration=development');