From b3e0e2885d015df619cfb1770a78ca5b27639324 Mon Sep 17 00:00:00 2001
From: ajay2507 <pajay2507@gmail.com>
Date: Sat, 6 Oct 2018 13:55:45 -0700
Subject: [PATCH] update readme and version bump

---
 README.md    | 23 ++++++++++++++---------
 package.json |  2 +-
 2 files changed, 15 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index 7f8da20..0c86d79 100644
--- a/README.md
+++ b/README.md
@@ -31,12 +31,8 @@ Creates lasso-analyze.html in your project directory.
 </p>
 
 ## Usage as CLI ##
-1. make the bundlingEnabled flag to true in config.json
-``` bash
-"bundlingEnabled": true,
-"outputDir": "build/static/",
-```
-2. Bundled file is created under "build/static/" folder. Run the CLI as shown below
+
+1. Bundled file is created under "build/static/" folder. Run the CLI as shown below
 
 ```bash
 lasso-analyzer <--bundle path-->
@@ -44,15 +40,24 @@ lasso-analyzer <--bundle path-->
 
 For Example:
 
+a. Options to provide direct Output js file.
+``` bash
+lasso-analyzer static/build.js
+```
+or
+
+b. Options to provide Output Folder like this, it iterates entire folder and create lasso-analyze.html.
+
 ``` bash
-lasso-analyzer build/static/index.js
+lasso-analyzer static
 ```
-3. lasso-analyze.html file is created in root path of your project structure.
+
+2. lasso-analyze.html file is created in root path of your project structure.
 
 ``` bash
 open lasso-analyze.html
 ```
-4. It shows you a treemap visualization as shown below.
+3. It shows you a treemap visualization as shown below.
 
 
 ## Issues ##
diff --git a/package.json b/package.json
index f7994c0..b42409f 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "lasso-analyzer",
-  "version": "1.1.8",
+  "version": "1.1.9",
   "description": "A tool to analyze the bundle created by Lasso",
   "main": "src/lasso-analyzer-plugin.js",
   "bin": {