chore(*): check in package-lock.json

README.md

@@ -39,8 +39,8 @@ The `depth=1` tells git to only pull down one commit worth of historical data.
 
 ### Install Dependencies
 
-We have two kinds of dependencies in this project: tools and AngularJS framework code. The tools help
-us manage and test the application.
+We have two kinds of dependencies in this project: tools and AngularJS framework code. The tools
+help us manage and test the application.
 
 * We get the tools we depend upon and the AngularJS code via `npm`, the [Node package manager][npm].
 * In order to run the end-to-end tests, you will also need to have the
@@ -54,14 +54,15 @@ can simply do:
 npm install
 ```
 
-Behind the scenes this will also call `npm run copy-libs`, which copies the AngularJS files and other
-front end dependencies. After that, you should find out that you have two new directories in your project.
+Behind the scenes this will also call `npm run copy-libs`, which copies the AngularJS files and
+other front end dependencies. After that, you should find out that you have two new directories in
+your project.
 
 * `node_modules` - contains the npm packages for the tools we need
 * `app/lib` - contains the AngularJS framework files and other front end dependencies
 
-*Note copying the AngularJS files from `node_modules` to `app/lib` makes it easier to serve the files
-by a web server.*
+*Note copying the AngularJS files from `node_modules` to `app/lib` makes it easier to serve the
+files by a web server.*
 
 ### Run the Application
 
@@ -99,10 +100,12 @@ app/                  --> all of the source files for the application
   app.js                --> main application module
   index.html            --> app layout file (the main html template file of the app)
   index-async.html      --> just like index.html, but loads js files asynchronously
-karma.conf.js         --> config file for running unit tests with Karma
 e2e-tests/            --> end-to-end tests
   protractor-conf.js    --> Protractor config file
   scenarios.js          --> end-to-end scenarios to be run by Protractor
+karma.conf.js         --> config file for running unit tests with Karma
+package.json          --> Node.js specific metadata, including development tools dependencies
+package-lock.json     --> Npm specific metadata, including versions of installed development tools dependencies
 ```
 
 
@@ -248,13 +251,13 @@ This really depends on how complex your app is and the overall infrastructure of
 the general rule is that all you need in production are the files under the `app/` directory.
 Everything else should be omitted.
 
-AngularJS apps are really just a bunch of static HTML, CSS and JavaScript files that need to be hosted
-somewhere they can be accessed by browsers.
+AngularJS apps are really just a bunch of static HTML, CSS and JavaScript files that need to be
+hosted somewhere they can be accessed by browsers.
 
-If your AngularJS app is talking to the backend server via XHR or other means, you need to figure out
-what is the best way to host the static files to comply with the same origin policy if applicable.
-Usually this is done by hosting the files by the backend server or through reverse-proxying the
-backend server(s) and web server(s).
+If your AngularJS app is talking to the backend server via XHR or other means, you need to figure
+out what is the best way to host the static files to comply with the same origin policy if
+applicable. Usually this is done by hosting the files by the backend server or through
+reverse-proxying the backend server(s) and web server(s).
 
 
 ## Continuous Integration