reshuffled dependencies in package.json to make it compatible with Beanstalk

Author: Vladimir Budilov

README.md

@@ -50,7 +50,7 @@ while Elastic Beanstalk gives you the capability of adding backend operations to
 * [What is Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html)
 * [What is S3](http://docs.aws.amazon.com/AmazonS3/latest/dev/Welcome.html)
 
-** createResources.sh requires your [aws cli to be configured](http://docs.aws.amazon.com/cli/latest/userguide/controlling-output.html) for JSON output.  **
+**createResources.sh requires your [aws cli to be configured](http://docs.aws.amazon.com/cli/latest/userguide/controlling-output.html) for JSON output.**
 
 ```
 # Install the AWS resources and deploy your application to either Elastic Beanstalk or S3
@@ -75,6 +75,11 @@ npm run build; cd dist; aws s3 sync . s3://[BUCKET_NAME]/
 # Test your deployed application
 curl –I http://[BUCKET_NAME].s3-website-[REGION].amazonaws.com/
 ```
+__*NOTE: You might want to reshuffle some of the "package.json" dependencies and move the ones that belong to devDependencies 
+for a leaner deployment bundle. At this point of time, AWS Beanstalk requires all of the dependencies, 
+including the devDependencies to be under the dependencies section. But if you're not using Beanstalk then you can
+optimize as you wish.*__
+
 *or*
 
 ### _Beanstalk:_ Update, Build and Deploy

package.json

@@ -48,10 +48,7 @@
     "webpack-dev-server": "2.4.2",
     "webpack-md5-hash": "0.0.5",
     "webpack-merge": "4.1.0",
-    "extract-text-webpack-plugin": "2.1.0"
-
-  },
-  "devDependencies": {
+    "extract-text-webpack-plugin": "2.1.0",
     "@angular/cli": "1.0.0",
     "@angular/compiler-cli": "4.0.0",
     "protractor": "5.1.1",
@@ -62,5 +59,9 @@
     "jasmine-spec-reporter": "2.5.0",
     "@types/jasmine": "2.2.30",
     "@types/selenium-webdriver": "2.44.26"
+
+  },
+  "devDependencies": {
+
   }
 }