Según devops, el comando ng build --prod está llevando a un alto uso de la CPU, por lo que el costo de nuestro servidor aumenta. No sé cómo optimizo este proceso de compilación, pero tengo dudas cuando ejecuto mi comando ng build localmente y en el servidor, la salida de la consola es diferente.
consola de producción.:
⠋ Generating browser application bundles (phase: setup)... [2K [1G⠙ Generating browser application bundles (phase: building)... [2K [1G⠹ Generating browser application bundles (phase: building)... [2K [1G⠸ Generating browser application bundles (phase: building)... [2K [1G⠼ Generating browser application bundles (phase: building)... [2K [1G⠴ Generating browser application bundles (phase: building)... [2K [1G⠦ Generating browser application bundles (phase: building)... [2K [1G⠧ Generating browser application bundles (phase: building)... [2K [1G⠇ Generating browser application bundles (phase: building)... [2K [1G⠏ Generating browser application bundles (phase: building)... [2K [1G⠋ Generating browser application bundles (phase: building)... [2K [1G⠙ Generating browser application bundles (phase: building)... [2K [1G⠹ Generating browser application bundles (phase: building)... [2K [1G⠸ Generating browser application bundles (phase: building)... [2K [1G⠼ Generating browser application bundles (phase: building)... [2K [1G⠴ Generating browser application bundles (phase: building)... [2K [1G⠦ Generating browser application bundles (phase: building)... [2K [1G⠧ Generating browser application bundles (phase: building)... [2K [1G⠇ Generating browser application bundles (phase: building)... [2K [1G⠏ Generating browser application bundles (phase: building)... [2K [1G⠋ Generating browser application bundles (phase: building)... [2K [1G⠙ Generating browser application bundles (phase: building)... [2K [1G⠹ Generating browser application bundles (phase: building)... [2K [1G⠸ Generating browser application bundles (phase: building)... [2K [1G⠼ Generating browser application bundles (phase: building)... [2K [1G⠴ Generating browser application bundles (phase: building)... [2K [1G⠦ Generating browser application bundles (phase: building)... [2K [1G⠧ Generating browser application bundles (phase: building)... [2K [1G⠇ Generating browser application bundles (phase: building)... [2K [1G⠏ Generating browser application bundles (phase: building)... [2K [1G⠋ Generating browser application bundles (phase: building)... [2K [1G⠙ Generating browser application bundles (phase: building)... [2K [1G⠹ Generating browser application bundles (phase: building)... [2K [1G⠸ Generating browser application bundles (phase: building)...Consola local:
Generating browser application bundles (phase: setup)...Compiling @angular/core : es2015 as esm2015En ambas consolas, la diferencia es que, en producción, la aplicación de navegador que genera... esta línea llama muchas veces, pero en local, esta es una llamada solo una vez y luego se inicia el proceso del paquete.
¿Dónde está la brecha en el comando ng build en el entorno local y el entorno del servidor?
Las múltiples líneas en la salida del servidor se deben simplemente al hecho de que el registro del servidor no sabe cómo manejar el carácter de progreso animado que se muestra en la consola.
Para la compilación del servidor, simplemente deshabilite los informes de progreso:
ng build --no-progress --prod