Mobile Web development Real-machine testing

Some experiences on real-computer test of mobile web development.

Before the development are used Chrom simulation, but the effect is not as good as the real machine, summed up a few points, as for the detailed installation process on the Internet has a tutorial http://www.cnblogs.com/xiaohuochai/p/5512051.html, here is not to repeat.

Browsersync is based on node. JS and is a node module, so we need to first install Nodejs (*^__^*) hehe ... Browsersync allows the PC, the pages on each mobile device to respond to file changes in real time, without refreshing the operation ~ ~

The approximate process is:

1. Installing Node.exe

2. Download NPM Decompression

3. Configure a path for the Node.exe, and Node_path as the node_modules path

4. Install Express: Open the cmd command line (in the Nodejs directory, hold down the shift button, then right-click, the "Open command Window Here" option and click), use the command line to navigate to this node directory, type the instructions NPM install Express

5. After the installation is complete, enter NODE-V in the command line if the output Nodejs version is installed successfully

-------------------------------------

The next step is to install the Browsersync monitoring, of course, you can also install on your convenient desktop monitoring (http://www.cnblogs.com/eva1963/p/5149168.html)-" Note the command that runs at the end of the article is not legible and can refer to the first (http://www.cnblogs.com/xiaohuochai/p/5512051.html)

Throughout the process is very smooth, just when the final start of the Web page opened to find is cannot get here to think what is the problem ....

The attentive person will eventually find out when opening the browser is localhost:3000 rather than the final path of your project ~ ~ ~ (localhost:3000/one/index.html)

Mobile Web development Real-machine testing