ng run with --configuration option

[Manduro]

Versions

Angular CLI: 6.0.0-rc.7
Node: 8.10.0
OS: darwin x64
Angular: 6.0.0-rc.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.11
@angular-devkit/build-angular     0.5.11
@angular-devkit/build-optimizer   0.5.11
@angular-devkit/core              0.5.11
@angular-devkit/schematics        0.5.10
@angular/cdk                      6.0.0-rc.14
@angular/cli                      6.0.0-rc.7
@angular/flex-layout              6.0.0-beta.15
@angular/material                 6.0.0-rc.14
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.9
@schematics/angular               0.5.10
@schematics/update                0.5.10
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

> ng run site:app-shell --configuration=accp

Observed behavior

Unknown option: '--configuration'

Desired behavior

I expect to be able to use --configuration in the same way as it works for ng build, ng serve, etc.
The documentation also suggests this should be possible: https://github.com/angular/angular-cli/blob/master/docs/documentation/run.md

Mention any other details that might be useful (optional)

I know this can be done using ng run site:app-shell:accp, but why not make it consistent with other commands? Argument are easier to pass around in npm scripts as well.

My use case:

{
  "scripts": {
    "build.app-shell": "ng run site:app-shell"
  }
}

Then use npm run build.app-shell -- --configuration=accp.
This does not seem to be possible with a command like ng run site:app-shell:${configuration}

[Xoadra]

I got this to work simply by appending a typical ng run command with the :configuration-name-here at the end of a project's architect name. For example, you could have ng run angular:build:production, with angular as the project name and build as the architect configuration, followed by that architect's configuration.

You shouldn't need to write any scripts to make this work, but you can always add this to your package.json's scripts if you want. It'll work there too. :D

Hope this helps!

[Manduro]

I know it works that way, but there are use cases where arguments make it a lot more flexible. And the docs mention it should be possible to do so. It's all in the issue really ;)

[attilacsanyi]

@Manduro do you have an open source example where I can check how you use app-shell architect? I wanted to use with PWA, but was not working as expected, thx in advance.

[Manduro]

@attilacsanyi Basically it's this:

angular.json

{
  ...
  "projects": {
    "site": {
      "architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
          "options": {...},
          "configurations": {
            "accp": {...},
            "prod": {...}
        },
        "serve": {...},
        "test": {...},
        "lint": {...},
        "server": {
          "builder": "@angular-devkit/build-angular:server",
          "options": {
            "outputPath": "dist-server",
            "main": "src/main.server.ts",
            "tsConfig": "src/tsconfig.server.json"
          }
        },
        "app-shell": {
          "builder": "@angular-devkit/build-angular:app-shell",
          "options": {
            "browserTarget": "site:build",
            "serverTarget": "site:server",
            "route": "/shell"
          },
          "configurations": {
            "accp": {
              "browserTarget": "site:build:accp"
            },
            "prod": {
              "browserTarget": "site:build:prod"
            }
          }
        }
      }
    }
  }
}

package.json

{
  "scripts": {
    "build.app-shell.accp": "ng run site:app-shell:accp",
    "build.app-shell.prod": "ng run site:app-shell:prod",
    ...
  }
  ...
}

With CLI 6.1.0 (beta) where this issue is solved, you can now do this:

package.json

{
  "scripts": {
    "build.app-shell": "ng run site:app-shell"
    ...
  }
  ...
}

npm run build.app-shell -- --configuration=accp

[attilacsanyi]

Thanks @Manduro it is straightforward I have the same.

But when I call npm run build.app-shell with prod and I have already service-worker setup with @angular/pwa and SwUpdate service with popup, then no SwUpdate popup coming, just if I run ng build --prod. This is another issue, not related here just wrote it down

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}