Update Wiki for 6.x

[filipesilva]

We need to update the Wiki to include command options and journey updates.

To track the wiki stories:

• application-environments (pr - docs: update application environments #10537)
• asset-configuration (pr - docs: update assets docs #10538)
• autoprefixer (no changes needed)
• budgets (pr - docs: Update bundle budgets story. #10495)
• code-coverage (pr - docs: Update code coverage story. #10498)
• configure-hmr (pr - docs: Update hmr story. #10500)
• continuous-integration (no changes needed)
• css-preprocessors (pr - docs: Update css preprocessor story. #10501)
• disk-serve (no changes needed)
• github-pages (no changes needed)
• global-lib (pr - docs: update global styles/scripts/lib wiki #10541)
• global-scripts (pr - docs: update global styles/scripts/lib wiki #10541)
• global-styles (pr - docs: update global styles/scripts/lib wiki #10541)
• include-angular-flex (no changes needed)
• include-angular-material (no changes needed)
• include-angularfire (no changes needed)
• include-bootstrap (pr - docs: Update bootstrap story. #10503)
• include-font-awesome (pr - docs: Update font awesome story. #10505)
• internationalization (pr - docs: update intl wiki #10543)
• linked-library (replaced with lib creation pr - docs: add library creation #10545)
• moving-into-the-cli (removed in pr docs: remove moving in/out #10546)
• moving-out-of-the-cli (removed in pr docs: remove moving in/out #10546)
• multiple-apps (replaced by multiple projects in pr docs: add multiple projects #10548)
• proxy (pr - docs: update proxy wiki #10553)
• routing (no changes needed)
• third-party-lib (no changes needed)
• universal-rendering (pr - docs: update universal doc #10554)
• using-corporate-proxy (pr - docs: update proxy wiki #10553)
• replace angular-cli.md with angular.md containing the config file description (pr - docs: add workspace docs #10562)

We also need to update the docs for individual commands.

• auto generate command wiki docs (build: basic command wiki documentation tool #10470)
• update description on top of command pages (pr - Update command description and remove eject command page #10560)
• add arguments for generate commands (pr - Auto doc #10583)

We also need to add a link to the old docs

• add a link to the old docs (pr - Keep 1x wiki #10555)

After a release, we should add schema links to the workspace file docs

• add range links to the CLI schema file in the workspace doc (pr - docs: add schema links for Angular workspace #10578)

[filipesilva]

We'll also need to add the library doc there.

[elvisbegovic]

Currently even after watching presentation angular.json is out of scope to me, i have to generate same app in two app (due to i18n) and I want different architect.build.options (remove some assets from one)

I can run ng build --configuration=myConf it will point architect.build.configurations but what about architect.build.options how have multiple options?
like ng build --options=myOptions

Thanks @filipesilva

[filipesilva]

Heya @istiti, you can override any options you want in configurations. For instance, you can have:

"architect": {
  "build": {
    "builder": "@angular-devkit/build-angular:browser",
    "options": {
      "assets": [
        {
          "glob": "**/*",
          "input": "src/assets",
          "output": "/assets"
        }
      ],
    },
    "configurations": {
      "language-fr": {
        "i18nLocale": "fr",
        "i18nFile": "src/locale/messages.fr.xlf",
        "assets": [],
      },
      "language-de": {
        "i18nLocale": "de",
        "i18nFile": "src/locale/messages.de.xlf",
        "assets": [],
      }
    }
  },

This should give you i18n for two different languages, without assets. Is this what you wanted?

[elvisbegovic]

@filipesilva thanks but have you tried this ?
because on my side if I reset asse to empty array I get:

I copy exactly your config and run ng b -c=fr it seems because assets reset to empty array it stop command without error, if I remove assets:[] it works it compile, might be a bug ?

[MickL]

@filipesilva If i put options like sourceMap into architect.build.options it is also applied to architect.serve.options?

I want to set defaults for build like "sourceMap": false which should not be applied to serve. But right now i have to repeat myself:

"configurations": {
            "testing": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.testing.ts"
                }
              ],
              "sourceMap": false,             
            },
            "staging": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.staging.ts",
                }
              ],
              "sourceMap": false,
            },
            "production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                }
              ],
              "sourceMap": false,
            }
}

[filipesilva]

@istiti that is indeed a bug, I know what's wrong and will fix (angular/devkit#819)

@MickL Yes, what you put in build will be applied to serve since the dev server will use the build options. However, sourceMap is one of the (few) build options that you can override in serve (angular/devkit#734).

[hansl]

Reopening as this was not meant to be closed (yet).

[ghost]

configure-hmr (pr - #10500)

If you follow the docs, you will end up with

Schema validation failed with the following errors:
  Data path "['serve'].configurations['hmr']" should be object.
Error: Schema validation failed with the following errors:
  Data path "['serve'].configurations['hmr']" should be object.

Fixed with PR #10592

[filipesilva]

@robertbaker sorry for that, I have pushed a fix in #10603. The file replacement was also missing.

I'm closing this issue because all the items I had in the original list are addressed.

[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.}