Woah, that issue template is a pain to work with.

Would you like to add more details to this doc? That string is extracted from json files in this repo, and should be the 3 results for "Target to serve" if you search across the code.

I'd love to, but I have no idea what it does nor how to use it. That's why I was referring to the docs.

The browserTarget property says what build target is going to be served. The serve command doesn't completely know how to build it, it just knows how to serve it.

Usually there's only one build, but since a target can have multiple configurations, you can specify that you want to serve that particular configuration of the build. There's some more information about it in this AIO page.

In practical terms what this means is that ng serve will serve the development build and ng serve --prod will serve the production build.

The way this is specified is through browserTarget. In a default angular.json you'll have this:

{
  "projects": {
    "next-app": {
      ...
      "architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
          "options": { ... }
          "configurations": {
            "production": { ... }
        },
        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "next-app:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "next-app:build:production"
            }
          }
        },

Where "browserTarget": "next-app:build" means "I want to serve projects->next-app with the default options" and "browserTarget": "next-app:build:production" means "I want to serve projects->next-app with the default options merged with the production config".

Does this description help?