angular-start | Angular起步项目，目前更新到Angular5.x | Command Line Interface library

I'm sure you've already found this but there is Microsoft's starter template here: https://github.com/Microsoft/TypeScript-Node-Starter

Whilst you are still on Node 8.x, keep your module set to commonjs, target can be es6.

compilerOptions.lib only defines what declarations the compiler uses for compile time checks, it does not affect the output of tsc. In other words, you can use whatever lib you want and not worry that your transpiled code will be any different (this is controlled entirely by compilerOptions.target).

Using es7 as a lib in your case will be fine and will give you type declarations for ES7 and under.

Array.includes is ES7 (ES2016) and therefore as you've discovered is not part of ES6. You could define your lib as; lib: ["es6", "ES2016.Array.Include"] to get around your issue.

In angular, the view is encapsulated with each unique attribute.

add encapsulation: ViewEncapsulation.None in main component, hence the css will be shared by all components

Before I go into any detail, let me give you the Github link of my Angular Universal seed project with Dockerfile and Sass. I use it as a starting point for my projects. Since I am a fan of Vagrant, you will find the Vagranfile in the repository and use it to create the exact same environment for development as well as testing the Docker container. The Readme file provides all the details as to how to work with the project.

Here is the link.

Angular Universal Project Creation

The Angular Universal setup steps are detailed here in the official documentation.

However, I had a few wasted hours to find out the following point

• Webpack 3 is not compatible with ts-loader versions higher than 3.5.0. At the time of developing this, the latest version of Angular CLI is 1.7.2 which uses Webpack 3.*. Hence, while setting up Angular Universal, install ts-config@3.5.0

Dockerfile

My Dockerfile looks like below. So, as you can see, I am using the docker feature multi stage build to first build the project in a container, copying the distribution to a new container and discarding the old container used for build. This allows Google Cloud build trigger to build the source code and create the Docker image from the distribution.

In your app.module.ts, did you import ListModule ?

I faced same issue, and was able to fix it by removing lazy loaded modules from imports in app.module.ts

It's possible if you add [style.display]="isCollapsed?'inherit':'none'" into

:

first npm i --save async, then restart your app

• Open your angular.json file, set "outputPath" to ../../../dist

• In your package.json, you should have a build script, example:

Although not optimal, I solved this by moving completely to Angular CLI and ditching the manual webpack config. I hoped I could then do ng eject and get the resulting webpack config, but it appears as if the Angular devs have disabled it :/

As mentioned in the above comment the solution was to remove the tilders...

"If you use lower that ^5.x.x, npm version (means you don't have package-lock.json), you can try to remove all ~ and ^ from package.json".