+
+Check out [angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpages), a full featured package that does all this for you and has extra functionality.
+
+
+
++ +{@a server-configuration} + +## Server configuration + +This section covers changes you may have to make to the server or to files deployed on the server. + +{@a fallback} + +### Routed apps must fallback to `index.html` + +Angular apps are perfect candidates for serving with a simple static HTML server. +You don't need a server-side engine to dynamically compose application pages because +Angular does that on the client-side. + +If the app uses the Angular router, you must configure the server +to return the application's host page (`index.html`) when asked for a file that it does not have. + +{@a deep-link} + +A routed application should support "deep links". +A _deep link_ is a URL that specifies a path to a component inside the app. +For example, `http://www.mysite.com/heroes/42` is a _deep link_ to the hero detail page +that displays the hero with `id: 42`. + +There is no issue when the user navigates to that URL from within a running client. +The Angular router interprets the URL and routes to that page and hero. + +But clicking a link in an email, entering it in the browser address bar, +or merely refreshing the browser while on the hero detail page — +all of these actions are handled by the browser itself, _outside_ the running application. +The browser makes a direct request to the server for that URL, bypassing the router. + +A static server routinely returns `index.html` when it receives a request for `http://www.mysite.com/`. +But it rejects `http://www.mysite.com/heroes/42` and returns a `404 - Not Found` error *unless* it is +configured to return `index.html` instead. + +#### Fallback configuration examples + +There is no single configuration that works for every server. +The following sections describe configurations for some of the most popular servers. +The list is by no means exhaustive, but should provide you with a good starting point. + +* [Apache](https://httpd.apache.org/): add a +[rewrite rule](http://httpd.apache.org/docs/current/mod/mod_rewrite.html) to the `.htaccess` file as shown + (https://ngmilk.rocks/2015/03/09/angularjs-html5-mode-or-pretty-urls-on-apache-using-htaccess/): + +
+ # If the requested resource doesn't exist, use index.html + RewriteRule ^ /index.html +
+ +{@a optimize} + +## Production optimizations + +The `--prod` _meta-flag_ engages the following build optimization features. + +* [Ahead-of-Time (AOT) Compilation](guide/aot-compiler): pre-compiles Angular component templates. +* [Production mode](#enable-prod-mode): deploys the production environment which enables _production mode_. +* Bundling: concatenates your many application and library files into a few bundles. +* Minification: removes excess whitespace, comments, and optional tokens. +* Uglification: rewrites code to use short, cryptic variable and function names. +* Dead code elimination: removes unreferenced modules and much unused code. + +See [`ng build`](cli/build) for more about CLI build options and what they do. + + +{@a enable-prod-mode} + +### Enable runtime production mode + +In addition to build optimizations, Angular also has a runtime production mode. Angular apps run in development mode by default, as you can see by the following message on the browser console: + +
+
+Don't eagerly import something from a lazy-loaded module
+
+If you mean to lazy-load a module, be careful not to import it
+in a file that's eagerly loaded when the app starts (such as the root `AppModule`).
+If you do that, the module will be loaded immediately.
+
+The bundling configuration must take lazy loading into consideration.
+Because lazy-loaded modules aren't imported in JavaScript, bundlers exclude them by default.
+Bundlers don't know about the router configuration and can't create separate bundles for lazy-loaded modules.
+You would have to create these bundles manually.
+
+The CLI runs the
+[Angular Ahead-of-Time Webpack Plugin](https://github.com/angular/angular-cli/tree/master/packages/ngtools/webpack)
+which automatically recognizes lazy-loaded `NgModules` and creates separate bundles for them.
+
+
+
+{@a measure}
+
+### Measure performance
+
+You can make better decisions about what to optimize and how when you have a clear and accurate understanding of
+what's making the application slow.
+The cause may not be what you think it is.
+You can waste a lot of time and money optimizing something that has no tangible benefit or even makes the app slower.
+You should measure the app's actual behavior when running in the environments that are important to you.
+
+The
+
+Chrome DevTools Network Performance page is a good place to start learning about measuring performance.
+
+The [WebPageTest](https://www.webpagetest.org/) tool is another good choice
+that can also help verify that your deployment was successful.
+
+{@a inspect-bundle}
+
+### Inspect the bundles
+
+The source-map-explorer
+tool is a great way to inspect the generated JavaScript bundles after a production build.
+
+Install `source-map-explorer`:
+
+
+ 
+
+
+{@a base-tag}
+
+## The `base` tag
+
+The HTML [_<base href="..."/>_](/guide/router)
+specifies a base path for resolving relative URLs to assets such as images, scripts, and style sheets.
+For example, given the `
+
+
+See also the [*APP_BASE_HREF*](api/common/APP_BASE_HREF "API: APP_BASE_HREF") alternative.
+
+
+
+In development, you typically start the server in the folder that holds `index.html`.
+That's the root folder and you'd add `
+
+ Differential loading is currently only supported when using `es2015` as a compilation target. When used with targets higher than `es2015`, the build process emits a warning.
+
+
+
+For a development build, the output produced by `ng build` is simpler and easier to debug, allowing you to rely less on sourcemaps of compiled code.
+
+For a production build, your configuration determines which bundles are created for deployment of your application.
+When needed, the `index.html` file is also modified during the build process to include script tags that enable differential loading, as shown in the following example.
+
+
+
+ Some legacy browsers still download both bundles, but only execute the appropriate scripts based on the attributes mentioned above. You can read more on the issue [here](https://github.com/philipwalton/webpack-esnext-boilerplate/issues/1).
+
+
+
+### Configuring differential loading
+
+To include differential loading in your application builds, you must configure the Browserslist and TypeScript configuration files in your application project.
+
+The following examples show a `browserlistrc` and `tsconfig.json` file for a newly created Angular application. In this configuration, legacy browsers such as IE 9-11 are ignored, and the compilation target is ES2015.
+
+
+
+ To see which browsers are supported and determine which settings meet to your browser support requirements, see the [Browserslist compatibility page](https://browserl.ist/?q=%3E+0.5%25%2C+last+2+versions%2C+Firefox+ESR%2C+not+dead%2C+not+IE+9-11).
+
+
+
+The Browserslist configuration allows you to ignore browsers without ES2015 support. In this case, a single build is produced.
+
+If your Browserslist configuration includes support for any legacy browsers, the build target in the TypeScript configuration determines whether the build will support differential loading.
+
+{@a configuration-table }
+
+| Browserslist | ES target | Build result |
+| -------- | -------- | -------- |
+| ES5 support disabled | es2015 | Single build, ES5 not required |
+| ES5 support enabled | es5 | Single build w/conditional polyfills for ES5 only |
+| ES5 support enabled | es2015 | Differential loading (two builds w/conditional polyfills) |
+
+{@a test-and-serve}
+
+## Local development in older browsers
+
+In Angular CLI version 8 and higher, differential loading is enabled by default for the `ng build` command.
+The `ng serve`, `ng test`, and `ng e2e` commands, however, generate a single ES2015 build which cannot run in older browsers that don't support the modules, such as IE 11.
+
+If you want to run ES5 code during development, you could disable differential loading completely.
+To maintain the benefits of differential loading, however, a better option is to define multiple configurations for `ng serve`, `ng e2e`, and `ng test`.
+
+{@a differential-serve}
+
+### Configuring serve for ES5
+
+To do this for `ng serve`, create a new file, `tsconfig-es5.app.json` next to `tsconfig.app.json` with the following content.
+
+
-The output folder is `dist/project-name/` by default.
-To output to a different folder, change the `outputPath` in `angular.json`.
+El folder de salida es `dist/project-name/` por defecto.
+Para obtener la salida en un folder diferente, cambia el `outputPath` en `angular.json`.
-As you near the end of the development process, serving the contents of your output folder from a local web server can give you a better idea of how your application will behave when it is deployed to a remote server.
-You will need two terminals to get the live-reload experience.
+Conforme se termina el proceso de desarrollo, servir el contenido que se encuentra en la carpeta de salida hacia un servidor web local, le dará una mejor idea de como se comportara su aplicación cuando se despliegue en un servidor remoto.
+
+Necesitara dos terminales para tener la experiencia de recarga automática.
-* On the first terminal, run the [`ng build` command](cli/build) in *watch* mode to compile the application to the `dist` folder.
+* En la primera terminal, ejecuta el comando [`ng build` command](cli/build) en modo *observador* para compilar la aplicación que se encuentra en la carpeta `dist`.
-This method is for development and testing only, and is not a supported or secure way of deploying an application.
+Este método es solamente para desarrollo y ambiente de pruebas, y no es soportado o seguro para desplegar la aplicación a producción.
-### Automatic deployment with the CLI
+### Despliegue automático con la CLI
-The Angular CLI command `ng deploy` (introduced in version 8.3.0) executes the `deploy` [CLI builder](guide/cli-builder) associated with your project. A number of third-party builders implement deployment capabilities to different platforms. You can add any of them to your project by running `ng add [package name]`.
+El comando de Angular CLI `ng deploy` (lanzado en la version 8.3.0) ejecuta `deploy` [CLI builder](guide/cli-builder) asociado con su proyecto. Varios constructores de terceros tienen la capacidad de desplegar en diferentes plataformas. Puede agregar cualquiera de ellos para ejecutar su proyecto como `ng add [nombre del paquete]`.
-When you add a package with deployment capability, it'll automatically update your workspace configuration (`angular.json` file) with a `deploy` section for the selected project. You can then use the `ng deploy` command to deploy that project.
+Cuando agrega un paquete con capacidad de despliegue, Se ejecutara automáticamente la actualización en su entorno de configuración (archivo `angular.json`) con una sección `deploy` para el proyecto seleccionado. Puede usar el comando `ng deploy` para desplegar su proyecto.
-For example, the following command automatically deploys a project to Firebase.
+Por ejemplo, el siguiente comando automáticamente desplegara su proyecto en Firebase.
-Check out [angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpages), a full featured package that does all this for you and has extra functionality.
+Verifique [angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpages), un paquete con todas las funciones que hace todo esto por usted y tiene una funcionalidad adicional.
@@ -139,48 +139,49 @@ Check out [angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpa
{@a server-configuration}
-## Server configuration
-This section covers changes you may have to make to the server or to files deployed on the server.
+## Configuración del servidor
+
+Esta sección cubre los cambios que debe hacer en el servidor o los archivos que se desplegaron en el servidor.
{@a fallback}
-### Routed apps must fallback to `index.html`
+### Las aplicaciónes con rutas deben redirigirse a `index.html`
-Angular apps are perfect candidates for serving with a simple static HTML server.
-You don't need a server-side engine to dynamically compose application pages because
-Angular does that on the client-side.
+Las aplicaciónes de Angular son los candidatos perfectos para desplegar con un servidor HTML estático.
+No se necesita un server-side engine para crear su aplicación dinámica porque
+Angular hace eso desde el lado del cliente.
-If the app uses the Angular router, you must configure the server
-to return the application's host page (`index.html`) when asked for a file that it does not have.
+Si la aplicación usar rutas de Angular, debe configurar el servidor
+para que regresen a la pagina principal (`index.html`) cuando se pida una ruta que no existe.
{@a deep-link}
-A routed application should support "deep links".
-A _deep link_ is a URL that specifies a path to a component inside the app.
-For example, `http://www.mysite.com/heroes/42` is a _deep link_ to the hero detail page
-that displays the hero with `id: 42`.
+Una aplicación con rutas debe soportar "enlaces profundos".
+Un _deep link_ es una URL que especifica la ruta a un componente dentro de la aplicación.
+Por ejemplo, `http://www.mysite.com/heroes/42` es un _deep link_ para la pagina que contiene el detalle del héroe,
+la cual despliega el héroe con el `id: 42`.
-There is no issue when the user navigates to that URL from within a running client.
-The Angular router interprets the URL and routes to that page and hero.
+No hay problema cuando el usuario navega hacia la URL dentro de un cliente en ejecución.
+Las rutas de Angular interpreta la URL y las rutas de esa pagina.
-But clicking a link in an email, entering it in the browser address bar,
-or merely refreshing the browser while on the hero detail page —
-all of these actions are handled by the browser itself, _outside_ the running application.
-The browser makes a direct request to the server for that URL, bypassing the router.
+Pero al hacer clic en un correo electrónico, se debe ingresar en la barra de direcciones,
+o simplemente refresque el navegador mientras se encuentra en la pagina del detalle del héroe —
+todas estas acciones son manejadas por el navegador, _outside_ fuera de la aplicación.
+El navegador hace la redirección con un pedido hacia la URL del servidor, pasando por alto el router.
-A static server routinely returns `index.html` when it receives a request for `http://www.mysite.com/`.
-But it rejects `http://www.mysite.com/heroes/42` and returns a `404 - Not Found` error *unless* it is
-configured to return `index.html` instead.
+Un servidor estático retorna rutinariamente index.html cuando recibe un pedido para `http://www.misitio.com/`.
+Pero es rechazada para `http://www.mysite.com/heroes/42` y retorna un error `404 - Not Found` *a menos*
+que este este configurado para devolver `index.html`.
-#### Fallback configuration examples
+#### Ejemplos de configuración de reserva
-There is no single configuration that works for every server.
-The following sections describe configurations for some of the most popular servers.
-The list is by no means exhaustive, but should provide you with a good starting point.
+No hay una sola manera para trabajar con cada servidor.
+Las siguientes secciones se describe la configuración para algunos de los servidores mas populares.
+La lista de ninguna manera es exhaustivo, pero debería proporcionarle un buen punto de partida.
-* [Apache](https://httpd.apache.org/): add a
-[rewrite rule](http://httpd.apache.org/docs/current/mod/mod_rewrite.html) to the `.htaccess` file as shown
+* [Apache](https://httpd.apache.org/): agregar a
+[regla de sobre escritura](http://httpd.apache.org/docs/current/mod/mod_rewrite.html) a el archivo `.htaccess` como muestra
(https://ngmilk.rocks/2015/03/09/angularjs-html5-mode-or-pretty-urls-on-apache-using-htaccess/):
{@a optimize} -## Production optimizations +## Optimizacion en producción -The `--prod` _meta-flag_ engages the following build optimization features. +La bandera `--prod` _meta-flag_ compromete las siguientes características para la optimización. -* [Ahead-of-Time (AOT) Compilation](guide/aot-compiler): pre-compiles Angular component templates. -* [Production mode](#enable-prod-mode): deploys the production environment which enables _production mode_. -* Bundling: concatenates your many application and library files into a few bundles. -* Minification: removes excess whitespace, comments, and optional tokens. -* Uglification: rewrites code to use short, cryptic variable and function names. -* Dead code elimination: removes unreferenced modules and much unused code. +* [Ahead-of-Time (AOT) Compilation](guide/aot-compiler): pre compila las plantillas de los componentes de Angular +* [Modo de producción](#enable-prod-mode): despliega un ambiente de producción que habilita el _production mode_. +* Empaquetado: concatena tus aplicación y los archivos de las librerías dentro de algunos empaquetados. +* Minificación: remueve los espacios en blanco excedentes, comentarios y token adicionales. +* Uglificación: reescribe el código para hacerlo mas corto, encripta las variables y los nombres de las funciones. +* Eliminación de código muerto: remueve módulos sin referencia y el código que no es usado en la aplicación. -See [`ng build`](cli/build) for more about CLI build options and what they do. +Ver [`ng build`](cli/build) para mas información acerca de las opciones de construcción y que hacen en el CLI. {@a enable-prod-mode} -### Enable runtime production mode +### Habilitar el tiempo de ejecución en modo de producción -In addition to build optimizations, Angular also has a runtime production mode. Angular apps run in development mode by default, as you can see by the following message on the browser console: +Adicionalmente para optimizar la creación de aplicaciónes, Angular también posee tiempo de ejecución en el modo de producción. Las aplicaciónes de Angular se ejecutan en modo de desarrollo por defecto, tal como se puede ver en los siguientes mensajes de la consola:
+No importe algo de un modulo cargándolo de forma diferida
-Don't eagerly import something from a lazy-loaded module
+Si piensa hacer una carga lenta de un modulo de forma diferida, sea cuidadoso
+de no importarlo dentro de un archivo que se inicia con la aplicación (como la raíz en `AppModule`)
+si lo hace, el modulo se cargara inmediatamente.
-If you mean to lazy-load a module, be careful not to import it
-in a file that's eagerly loaded when the app starts (such as the root `AppModule`).
-If you do that, the module will be loaded immediately.
+La configuración de agrupación debe tener en cuenta la carga diferida.
+Debido a que los módulos de carga diferida no se importan en JavaScript, los paquetes los excluyen de forma predeterminada.
+Los empaquetadores no conocen la configuración del enrutador y no pueden crear paquetes separados para módulos de carga diferida.
+Tendría que crear estos paquetes manualmente.
-The bundling configuration must take lazy loading into consideration.
-Because lazy-loaded modules aren't imported in JavaScript, bundlers exclude them by default.
-Bundlers don't know about the router configuration and can't create separate bundles for lazy-loaded modules.
-You would have to create these bundles manually.
-
-The CLI runs the
+El CLI ejecuta el
[Angular Ahead-of-Time Webpack Plugin](https://github.com/angular/angular-cli/tree/master/packages/ngtools/webpack)
-which automatically recognizes lazy-loaded `NgModules` and creates separate bundles for them.
+que reconoce automáticamente los `NgModules` cargados de forma diferida y crea paquetes separados para ellos.
{@a measure}
-### Measure performance
+### Medición del rendimiento
-You can make better decisions about what to optimize and how when you have a clear and accurate understanding of
-what's making the application slow.
-The cause may not be what you think it is.
-You can waste a lot of time and money optimizing something that has no tangible benefit or even makes the app slower.
-You should measure the app's actual behavior when running in the environments that are important to you.
+Puede tomar una mejor decision acerca de la optimizacion cuando conoce y tiene un claro entendimiento de
+porque su aplicación es lenta.
+La causa es posible no sea lo que piense.
+Puede llegar a gastar mucho tiempo y dinero optimizando algo que no le dará un beneficio tangible o a veces la aplicación sera mas lenta.
+Puede medir el comportamiento de su aplicación cuando ejecuta los ambientes correctos y de importancia para usted.
-The
+La
-Chrome DevTools Network Performance page is a good place to start learning about measuring performance.
+herramienta de la pagina en Chrome DevTools Network Performance es un buen lugar para comenzar a aprender como medir el rendimiento de su aplicación.
-The [WebPageTest](https://www.webpagetest.org/) tool is another good choice
-that can also help verify that your deployment was successful.
+La herramienta [WebPageTest](https://www.webpagetest.org/) es otra buena opción
+que también le ayuda a verificar si su despliegue ha sido exitoso.
{@a inspect-bundle}
-### Inspect the bundles
+### Inspeccionado de paquetes
-The source-map-explorer
-tool is a great way to inspect the generated JavaScript bundles after a production build.
+La herramienta source-map-explorer
+es otro buen camino para inspeccionar los paquetes generados de JavaScript después de la creación de producción.
-Install `source-map-explorer`:
+Instala `source-map-explorer`:
@@ -411,77 +411,76 @@ Here's the output for the _main_ bundle of an example app called `cli-quickstart
{@a base-tag}
-## The `base` tag
+## La etiqueta `base`
-The HTML [_<base href="..."/>_](/guide/router)
-specifies a base path for resolving relative URLs to assets such as images, scripts, and style sheets.
-For example, given the `
-See also the [*APP_BASE_HREF*](api/common/APP_BASE_HREF "API: APP_BASE_HREF") alternative.
+Puede ver también [*APP_BASE_HREF*](api/common/APP_BASE_HREF "API: APP_BASE_HREF") como alternativa.
-In development, you typically start the server in the folder that holds `index.html`.
-That's the root folder and you'd add `
-
- Differential loading is currently only supported when using `es2015` as a compilation target. When used with targets higher than `es2015`, the build process emits a warning.
+
+ Actualmente, la carga diferencial solo se admite cuando se usa "es2015" como destino de compilación. Cuando se usa con objetivos superiores a "es2015", el proceso de compilación emite una advertencia.
-For a development build, the output produced by `ng build` is simpler and easier to debug, allowing you to rely less on sourcemaps of compiled code.
+Para una compilación de desarrollo, la salida producida por `ng build` es más simple y más fácil de depurar, lo que le permite depender menos de los mapas fuente del código compilado.
-For a production build, your configuration determines which bundles are created for deployment of your application.
-When needed, the `index.html` file is also modified during the build process to include script tags that enable differential loading, as shown in the following example.
+Para una compilación de producción, su configuración determina qué paquetes se crean para la implementación de su aplicación.
+Cuando es necesario, el archivo `index.html` también se modifica durante el proceso de compilación para incluir etiquetas de secuencia de comandos que permiten la carga diferencial, como se muestra en el siguiente ejemplo.
- Some legacy browsers still download both bundles, but only execute the appropriate scripts based on the attributes mentioned above. You can read more on the issue [here](https://github.com/philipwalton/webpack-esnext-boilerplate/issues/1).
+ Algunos navegadores heredados aún descargan ambos paquetes, pero solo ejecutan los scripts apropiados según los atributos mencionados anteriormente. Puedes leer más sobre el tema [aqui](https://github.com/philipwalton/webpack-esnext-boilerplate/issues/1).
-### Configuring differential loading
+### Configuración de carga diferencial
-To include differential loading in your application builds, you must configure the Browserslist and TypeScript configuration files in your application project.
+Para incluir la carga diferencial en la compilación de su aplicación, debe configurar el Browserslist y la configuración de TypeScript en los archivos de su aplicación.
-The following examples show a `browserlistrc` and `tsconfig.json` file for a newly created Angular application. In this configuration, legacy browsers such as IE 9-11 are ignored, and the compilation target is ES2015.
+Los siguientes ejemplos muestran un archivo `browserlistrc` y` tsconfig.json` para una aplicación Angular recién creada. En esta configuración, los navegadores heredados como IE 9-11 se ignoran y el objetivo de compilación es ES2015.
- To see which browsers are supported and determine which settings meet to your browser support requirements, see the [Browserslist compatibility page](https://browserl.ist/?q=%3E+0.5%25%2C+last+2+versions%2C+Firefox+ESR%2C+not+dead%2C+not+IE+9-11).
+ Para ver que navegador es soportado y determinar que configuración se asemeja a los requerimientos de su navegador, vea la [pagina de compatibilidad de Browserslist](https://browserl.ist/?q=%3E+0.5%25%2C+last+2+versions%2C+Firefox+ESR%2C+not+dead%2C+not+IE+9-11).
-The Browserslist configuration allows you to ignore browsers without ES2015 support. In this case, a single build is produced.
+La configuración de la lista de navegadores le permite ignorar los navegadores que no son compatibles con ES2015. En este caso, se produce una sola construcción.
-If your Browserslist configuration includes support for any legacy browsers, the build target in the TypeScript configuration determines whether the build will support differential loading.
+Si su configuración de Browserslist incluye soporte para navegadores heredados, el destino de compilación en la configuración de TypeScript determina si la compilación admitirá la carga diferencial.
{@a configuration-table }
| Browserslist | ES target | Build result |
| -------- | -------- | -------- |
-| ES5 support disabled | es2015 | Single build, ES5 not required |
-| ES5 support enabled | es5 | Single build w/conditional polyfills for ES5 only |
-| ES5 support enabled | es2015 | Differential loading (two builds w/conditional polyfills) |
+| ES5 soporte deshabilitado | es2015 | Empaquetado simple, ES5 no requerido |
+| ES5 soporte habilitado | es5 | Empaquetado simple con condiciones polyfills solo es para ES5 |
+| ES5 soporte habilitado | es2015 | Carga diferencial (dos o mas condiciones polyfills) |
{@a test-and-serve}
-## Local development in older browsers
+## Desarrollo local en navegadores viejos
-In Angular CLI version 8 and higher, differential loading is enabled by default for the `ng build` command.
-The `ng serve`, `ng test`, and `ng e2e` commands, however, generate a single ES2015 build which cannot run in older browsers that don't support the modules, such as IE 11.
+En Angular CLI versión 8 y superior, la carga diferencial está habilitada de forma predeterminada para el comando `ng build`.
+Sin embargo, los comandos `ng serve`,` ng test` y `ng e2e` generan una única compilación de ES2015 que no se puede ejecutar en navegadores antiguos que no admiten los módulos, como IE 11.
-If you want to run ES5 code during development, you could disable differential loading completely.
-To maintain the benefits of differential loading, however, a better option is to define multiple configurations for `ng serve`, `ng e2e`, and `ng test`.
+Si desea ejecutar el código ES5 durante el desarrollo, puede deshabilitar la carga diferencial por completo.
+Sin embargo, para mantener los beneficios de la carga diferencial, una mejor opción es definir múltiples configuraciónes para "ng serve", "ng e2e" y "ng test".
{@a differential-serve}
+{@a configuring-serve-for-es5}
+### Configurar el servicio para ES5
-### Configuring serve for ES5
-
-To do this for `ng serve`, create a new file, `tsconfig-es5.app.json` next to `tsconfig.app.json` with the following content.
+Para hacer esto para `ng serve`, cree un nuevo archivo,` tsconfig-es5.app.json` junto a `tsconfig.app.json` con el siguiente contenido.