thoughts on boilerplate & generate design

currently download from github export master zip

Planning to switch to npm pkg because:

1. version control
2. generate tasks integration

but npm download slowly, try to direct download the tar pkg

common generate tasks (add mock) provided by fe module and others within boilerplates:

• boilerplate directory structure:

package.json
meta.js
index.js
boilerplate/
generate/

• index.js includes tasks scripts:

export default {
    'generate:component': env => {
       copy('folder', 'project/src')
    },
    'build:XXX': () => {
    }
};

• export tasks in packge.json way

{
  "main": "index.js"
}

Review the proposed package.json, meta.js, index.js, boilerplate/, and generate/ layout, starting with the current GitHub master-zip download flow. Compare the npm package and direct tar download options, then define how tasks such as generate:component and build:XXX should be exported; done requires an agreed design and implementation scope.