up hero-cli to 2.1.1

.editorconfig

@@ -5,11 +5,7 @@ root = true
 [*]
 end_of_line = lf
 indent_style = space
-indent_size = 4
+indent_size = 2
 charset = utf-8
 trim_trailing_whitespace = true
 insert_final_newline = true
-
-[package.json]
-indent_style = space
-indent_size = 2

.eslintrc

@@ -0,0 +1,27 @@
+{
+  "root": true,
+  "parser": "babel-eslint",
+  "extends": "standard",
+  "env": {
+    "browser": true
+  },
+  "rules": {
+    "object-curly-spacing": [
+      2,
+      "always"
+    ],
+    "space-before-function-paren": [
+      2,
+      {
+        "anonymous": "never",
+        "named": "never",
+        "asyncArrow": "always"
+      }
+    ],
+    "no-var": 2,
+    "semi": [
+      2,
+      "never"
+    ]
+  }
+}

README.md

@@ -1,5 +1,7 @@
 # hero-cli
 
+[中文文档](https://github.com/hero-mobile/hero-cli/blob/master/README.zh.md)
+
 Create Hero apps with no build configuration.
 
 * [Getting Started](#getting-started) – How to create a new app.
@@ -61,14 +63,17 @@ It will create a directory called `my-app` inside the current folder.<br>
 Inside that directory, it will generate the initial project structure and then you can run command `npm install` to install the dependencies manually:
 
 ```
+├── environments
+│   ├── environment-dev.js
+│   └── environment-prod.js
+├── platforms
+│   ├── android
+│   └── iOS
 ├── public
 │   ├── ...
 │   └── favicon.ico
 ├── src
 │   ├── ...
-│   ├── environments
-│   │   ├── environment-dev.js
-│   │   └── environment-prod.js
 │   ├── index.html
 │   └── index.js
 ├── .babelrc
@@ -82,15 +87,16 @@ Inside that directory, it will generate the initial project structure and then y
 ```
 For the project to build, **these files must exist with exact filenames**:
 
+* `platforms` folder contains Android/iOS codes.
 * `src/index.html` is the entry page;
 * `src/index.js` is the JavaScript entry point.
-* `.hero-cli.json` is the configuration file for hero-cli build, it tell hero loads which configuration when you run command `hero start -e dev` or `hero build -e prod`(which is invoked by `npm start` or `npm build`) according to the value of `-e` parameter. For more build options please refer to [Build Scripts](#build-scripts).
+* `.hero-cli.json` is the configuration file for hero-cli build, it tell hero loads which configuration when you run command `hero start -e dev` or `hero build -e prod`(which is invoked by `npm start` or `npm run build`) according to the value of `-e` parameter. For more build options please refer to [Build Scripts](#build-scripts).
 
 You can delete or rename the other files.
 
 * `public` assets like images inside this folder will **copied into the build folder untouched**. It will not be processed by Webpack.
 * `src` For faster rebuilds, only files inside this folder are processed by Webpack. You need to **put any JS and CSS files inside this folder**, or Webpack won’t see them.
-* `src/environments` where your configurations exists(these file path configured in file `.hero-cli.json`, you can change it later) and you can access the configuration values in JavaScript or HTML code. See [Adding Custom Environment Variables](#adding-custom-environment-variables).
+* `environments` where your configurations exists(these file path configured in file `.hero-cli.json`, you can change it later) and you can access the configuration values in JavaScript or HTML code. See [Adding Custom Environment Variables](#adding-custom-environment-variables).
 
 You may curious about where is the `pages/start.html`. Yes, it's generated by hero-cli. See [Generate HTML](#generate-html)
 
@@ -107,7 +113,7 @@ You may curious about where is the `pages/start.html`. Yes, it's generated by he
   * [Android](#android)
   * [iOS](#ios)
 * [Build Scripts](#build-scripts)
-  * [`hero start`](#hero-start)
+  * [`hero dev`](#hero-dev)
   * [`hero build`](#hero-build)
   * [`hero serve`](#hero-serve)
   * [`hero init`](#hero-init)
@@ -122,26 +128,16 @@ Any JS file meet the following 2 conditions will treat as JavaScript entry point
 
 Which would cause a HTML file generated using Webpack plugin [html-webpack-plugin](https://www.npmjs.com/package/html-webpack-plugin):
 
-* Options specified in `@Entry(options)` will passed to `html-webpack-plugin` transparently.
-* Destination of generated HTML file will keep the file path structure of the Javascript entry, or you can override it using the option `filename` provided by `html-webpack-plugin`.
+* You can specify options during generate HTML via `@Entry(options)`.
+* Destination of generated HTML file will keep the file path structure of the Javascript entry, or you can override it using the option `path`.
 * Generated HTML file can access the [Custom Environment Variables](#adding-custom-environment-variables).
 
 Example:<br>
 
 Below JavaScript file `src/pages/start.js` will generate a HTML file access by URL `/pages/start.html`, that's why we can visit [http://localhost:3000/pages/start.html](http://localhost:3000/pages/start.html).
 
 ```javascript
-// content of file: src/pages/start.js
-import { Entry } from 'hero-cli/decorator';
-
-// class marked by @Entry
-// will generate HTML accessed by URL /pages/start.html
-// Equal to
-// @Entry({
-//   filename: 'pages/start.html'
-// })
-//
-@Entry()
+
 export class DecoratePage {
 
     sayHello(data){
@@ -151,6 +147,14 @@ export class DecoratePage {
 }
 
 ```
+If you want to rename filename, you can add a key/val to `router.js`:
+````javascript
+// router.js
+module.exports = {  
+  rename_home: require.resolve('./src/pages/start.js')
+}
+````
+than build will emit `rename_home.html`
 
 ### Adding Custom Environment Variables
 Your project can consume variables declared in your environment as if they were declared locally in your JS files. By default you will have any environment variables starting with `HERO_APP_`. These environment variables can be useful for consuming sensitive data that lives outside of version control.<br>
@@ -243,11 +247,10 @@ module.exports = environment;
 When you run command `hero start -e dev` or `hero build -e dev`, all variables from `src/environments/environment-dev.js` can be accessed via `process.env`.
 
 ### Proxying API Requests in Development
-People often serve the front-end React app from the same host and port as their backend implementation.
+People often serve the front-end appplication from the same host and port as their backend implementation.
 For example, a production setup might look like this after the app is deployed:
 ```
-/             - static server returns index.html with React app
-/todos        - static server returns index.html with React app
+/             - static server returns index.html with application
 /api/todos    - server handles any /api/* requests using the backend implementation
 
 ```
@@ -270,7 +273,7 @@ To tell the development server to proxy any unknown requests to your API server
 
 ```
 
-This way, when you `fetch('/api/v2/todos')` in development, the development server will proxy your request to `http://localhost:4000/api/v2/todos`, and when you `fetch('/feapi/todos')`, the request will proxy to `https://localhost:4001`.
+This way, when you `fetch('/api/v2/todos')` in development, the development server will proxy your request to `https://localhost:4000/api/v2/todos`, and when you `fetch('/feapi/todos')`, the request will proxy to `https://localhost:4001/feapi/todos`.
 
 ### Build Native App
 #### Android
@@ -286,12 +289,13 @@ This way, when you `fetch('/api/v2/todos')` in development, the development serv
 * `ANDROID_HOME`
 * `GRADLE_HOME`
 
-Currently, generated android apk will loads resources hosted by remote server. In order to make the appliation available in the your mobile.
+Currently, generated native app will loads resources hosted by remote server. In order to make the appliation available in the your mobile.
 
-Firstly, you have to deploy the codes generate by command [`hero build`](#hero-build) into remote server.<br>
-Secondly, before you generate the apk, you should using parameter `-e` to tell the apk loads which url when it startup.
+* Firstly, you can using command [`hero build`](#hero-build) to generate the package which contains the application codes for deploy.<br>
+* Secondly, specify the entry url in file `.hero-cli.json` when native app startup.
+* Finally, using command [`hero platform build`](#hero- platform-build) build the native app. before you generate the apk, you should using parameter `-e` to tell the apk loads which url when it startup.
 
-For example, you can config the url in file `.hero-cli.json` like this:
+For example:
 
 ```json
 {
@@ -316,6 +320,7 @@ For more options, see command of Build Scripts: [`Build Android App`](#build-and
 
 
 ### Build Scripts
+Below scripts support option `--verbose` to output more details.
 
 #### `hero start`
 
@@ -342,7 +347,7 @@ You will see the build errors and lint warnings in the console.
 
 * `-e`<br>Environment name of the configuration when start the application
 * `-s`<br>Build the boundle as standalone version, which should run in Native App environment. That's to say, build version without libarary like [webcomponent polyfills](http://webcomponents.org/polyfills/) or [hero-js](https://github.com/hero-mobile/hero-js)(These libarary is necessary for Hero App run in web browser, not Native App).
-* `-i`<br>Inline JavaScript code into HTML. Default value is [false].
+* `-i`<br>Inline JavaScript/CSS code into HTML. Default value is [false].
 * `-b`<br>Build pakcage only contain dependecies like hero-js or webcomponents, withou code in <you-project-path>/src folder. Default value is [false]
 * `-m`<br>Build without sourcemap. Default value is [false], will generate sourcemap.
 * `-f`<br>Generate AppCache file, default file name is "app.appcache". Default value is [false], will not generate this file.
@@ -385,7 +390,7 @@ This will let Hero App correctly infer the root path to use in the generated HTM
 After `hero build` process completedly, `build` folder will generated. You can serve a static server using `hero serve`.
 
 #### `hero init`
-You can run `hero build -h` for help. It will generate the initial project structure of Hero App. See [Creating an App](#creating-an-app).
+You can run `hero build -h` for help. It will generate the initial project structure of Hero App. See [Quick Overview](#quick-overview).
 
 #### `hero platform build`
 This command used for build native app. And you can run `hero platform build -h` for help.<br>
@@ -418,7 +423,7 @@ Once command `hero platform build android -e prod` execute successfully, a andro
 
 ###### How to specify the android build tool version in SDK
 Hero will dynamic using the lastest available one from your local install versions by default.
-You might have multiple available versions in the Android SDK. You can specify the `ANDROID_HOME/build-toos` version and compile `com.android.support:appcompat-v7` version following the keyword `android` and seperated by colon.
+You might have multiple available versions in the Android SDK. You can specify the `ANDROID_HOME/build-toos` version and compile `com.android.support:appcompat-v7` version following the command `hero platform build android` and seperated by colon.
 
 For example, you can using the below command specify the `ANDROID_HOME/build-toos` version `23.0.2` and compile `com.android.support:appcompat-v7` version `24.0.0-alpha1`: