Browse Source

Fix Image URLs on Read me file

Fix Image URLs on Read me file. It seems to be broken
pull/1170/head
Gajendra Babu Thokala [MSFT] 5 years ago
committed by GitHub
parent
commit
92b435d658
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 6 deletions
  1. +7
    -6
      src/Web/WebSPA/README.md

+ 7
- 6
src/Web/WebSPA/README.md View File

@ -7,29 +7,30 @@ The SPA application is using a newer version of NPM than the one provided by Vis
NPM is bundled with NODE.JS. Installing NPM and NODE is pretty straightforward by using the installer package available at https://nodejs.org/en/ NPM is bundled with NODE.JS. Installing NPM and NODE is pretty straightforward by using the installer package available at https://nodejs.org/en/
<img src="../../../../img/spa/installing_npm_node.png">
<img src="../../../img/spa/installing_npm_node.png">
You can install the version "Recommended For Most Users" of Node which at the moment of this writing was v6.9.3 LTS and comes with a newer version of NPM. You can install the version "Recommended For Most Users" of Node which at the moment of this writing was v6.9.3 LTS and comes with a newer version of NPM.
You can see your initial NPM version and the installed NPM version with the command You can see your initial NPM version and the installed NPM version with the command
<b>npm -v</b>, as shown below. <b>npm -v</b>, as shown below.
<p> <p>
<img src="../../../../img/spa/npm-versions-powershell.png">
<img src="../../../img/spa/npm-versions-powershell.png">
### Set NPM path into Visual Studio ### Set NPM path into Visual Studio
NPM will be usually installed under this path: NPM will be usually installed under this path:
<b>C:\Program Files (x86)\nodejs</b>. <b>C:\Program Files (x86)\nodejs</b>.
You need to update that path in Visual Studio 2015 under the "External Web Tools" location paths, as shown below: You need to update that path in Visual Studio 2015 under the "External Web Tools" location paths, as shown below:
<p> <p>
<img src="../../../../img/spa/vs-tools-path-custom-node.png">
<img src="../../../img/spa/vs-tools-path-custom-node.png">
### Build the SPA app with NPM ### Build the SPA app with NPM
Finally, you need to build the SPA app (TypeScript and Angular based client app) with NPM. Finally, you need to build the SPA app (TypeScript and Angular based client app) with NPM.
* Open a command-prompt window and move to the root of the SPA application (src\Web\WebSPA\eShopOnContainers.WebSPA) * Open a command-prompt window and move to the root of the SPA application (src\Web\WebSPA\eShopOnContainers.WebSPA)
* Run the command <b>npm run build:prod</b> as shown below: * Run the command <b>npm run build:prod</b> as shown below:
<p> <p>
<img src="../../../../img/spa/npm-run-build.png">
<img src="../../../img/spa/npm-run-build.png">
If you get an error like <b>"Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x"</b>, then run the command <b>npm rebuild node-sass</b> as in the following screenshot: If you get an error like <b>"Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x"</b>, then run the command <b>npm rebuild node-sass</b> as in the following screenshot:
<img src="../../../../img/spa/npm-rebuild-node-sass.png">
<img src="../../../img/spa/npm-rebuild-node-sass.png">
Then, run again the <b>npm run build:prod</b> command that should finish with no errors. Then, run again the <b>npm run build:prod</b> command that should finish with no errors.
### Build/create the Docker images ### Build/create the Docker images
@ -41,6 +42,6 @@ Deploy/run the Docker containers with <b>"docker-compose up"</b> as explained in
### Test the SPA web application ### Test the SPA web application
Test the SPA app by running the following URL in a browser: Test the SPA app by running the following URL in a browser:
<b> http://TBD</b>
<b> http://localhost:5104</b>

Loading…
Cancel
Save