rebuild time depends on assets

[montella1507]

Versions:

"@angular/animations": "^11.0.4",
   "@angular/cdk": "^11.0.2",
   "@angular/common": "^11.0.4",
   "@angular/compiler": "^11.0.4",
   "@angular/core": "^11.0.4",
   "@angular/forms": "^11.0.4",
   "@angular/localize": "^11.0.4",
   "@angular/platform-browser": "^11.0.4",
   "@angular/platform-browser-dynamic": "^11.0.4",
   "@angular/router": "^11.0.4"
  "@angular-devkit/build-angular": "^0.1100.4",
   "@angular-eslint/eslint-plugin": "0.8.0-beta.5",
   "@angular-eslint/eslint-plugin-template": "0.8.0-beta.5",
   "@angular-eslint/template-parser": "0.8.0-beta.5",
   "@angular/cli": "^11.0.4",
   "@angular/compiler-cli": "^11.0.4",
   "@angular/language-service": "^11.0.4",

Rebuild time is somehow affected by assets in angular.json - here are table with times with and without assets:

   "assets": [
              "apps/edhance/src/favicon.ico",
              "apps/edhance/src/assets",
              "apps/edhance/src/config.json",
              {
                "glob": "**/*",
                "input": "apps/edhance/configs",
                "output": "./configs/"
              }
            ],

Difference in first build is comprehensible (to copy static - immutable assets to serve folder), however, why is so big difference in rebuild time when i change typescript file?

(another project)

[alan-agius4]

This is unfortunately how https://webpack.js.org/plugins/copy-webpack-plugin works with Webpack 4. With every re-build the assets patterns are re-processed and copied over and over again.

With Webpack 5 & caching enabled this should get better eventually as this plugin use caching to reduce IO calls https://github.com/webpack-contrib/copy-webpack-plugin/blob/01fa91b09d3b4fdc4552b520bb90918fc7f34e54/src/index.js#L604

[montella1507]

:-( So it may be possible to try performance boost with:

"resolutions": {
    "webpack": "^5.0.0"
}

right?

[alan-agius4]

yes

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