From fc61d3cbb95e0c54811c85af51de36f6f44b50c5 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Fri, 4 Aug 2017 12:33:10 -0700 Subject: [PATCH] Updated 06. Setting the Web SPA application up (markdown) --- 06.-Setting-the-Web-SPA-application-up.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/06.-Setting-the-Web-SPA-application-up.md b/06.-Setting-the-Web-SPA-application-up.md index 6e44c9a..c3bdb0f 100644 --- a/06.-Setting-the-Web-SPA-application-up.md +++ b/06.-Setting-the-Web-SPA-application-up.md @@ -27,14 +27,14 @@ http://www.hanselman.com/blog/VisualStudio2015FixingDependenciesNpmNotInstalledF ### Build the SPA app with NPM -Now, you need to build the SPA app (TypeScript and Angular 2 based client app) with NPM. +Now, you need to build the SPA app (TypeScript and Angular 4 based client app) with NPM. * Open a command-prompt window and move to the root of the SPA application (src\Web\WebSPA\eShopOnContainers.WebSPA) * Run the command npm install as shown below: --------------- -**IMPORTANT NOTE/UPDATE (In research):** As of early August 2017, seems like some potential changes in NPM environment might be impacting the project. If you have a similar issue than [this issue](https://github.com/dotnet-architecture/eShopOnContainers/issues/253): try running **"npm install enhanced-resolve@3.3.0"** instead "npm install". This NOTE will be updated as soon as we have explored this issue in further details. +**IMPORTANT NOTE/UPDATE:** Seems like in some NPM environments running just "npm install" does not work properly. If you have a similar issue than [this issue](https://github.com/dotnet-architecture/eShopOnContainers/issues/253): try running **"npm install enhanced-resolve@3.3.0"** instead "npm install". (Please, provide your experience at that mentioned issue) ---------------