Updated 99. FAQ (Frequently Asked Questions) (markdown)

Eduard Tomàs 2017-08-11 12:13:57 +02:00
parent f5eccb3180
commit 1fd1a23279

@ -35,3 +35,8 @@ You can ignore those warnings. They're not from VS2017 but from docker-compose.
This error is produced because some Docker image can't be built. This is because the project is not published. All projects are published in their `obj/Docker/publish` folder. If there is any compilation error, the project won't be published and the corresponding docker image can't be built, and you will receive this error. This error is produced because some Docker image can't be built. This is because the project is not published. All projects are published in their `obj/Docker/publish` folder. If there is any compilation error, the project won't be published and the corresponding docker image can't be built, and you will receive this error.
**Note**: When you run the project using F5 from VS2017, projects are not published, so you won't receive this error in VS2017. **Note**: When you run the project using F5 from VS2017, projects are not published, so you won't receive this error in VS2017.
### When I build the SPA I receive a `Cannot read property '0' of undefined` in "npm install"
This is because of npm 5.3.0 on newer versions of nodejs. Downgrade to npm 5.2.0 until a fix is released. For more info check [this issue](https://github.com/dotnet-architecture/eShopOnContainers/issues/268)