Split out of #225...

I was wondering about drastically simplifying the .merge() section of the docs, so that instead of being a copy-paste of every webpack config option, it only listed the areas where the data structure differed from the real webpack config schema (plus perhaps a few examples from the options that were identical).

ie:

  // Differences from webpack config

This is a Bug Report

Description

For bug reports:

• What went wrong?
  When I was using only one package, web3 could be bundled successfully.
  But, I needed to restruct my project to using yarn workspace. So, I only restructed (not code edited) my project and I came across some bundling errors.

(skip warning)

ERROR in D:/Users/jormal/WebstormProjects/TX_COLLECTOR/tx-collector/n

想新增一个alias，像vue脚手架默认填写的：
resolve: {
alias: {
'vue$': 'vue/dist/vue.esm.js',
'@': resolve('src')
}
},

即将@指向到某一个目录，比如app/web/目录，我在webpack.config.js文件添加了

module.exports = {
egg: true,
devtool: 'eval',
target: 'web',
entry: {
admin: 'app/web/page/admin/index.js'
},
cssExtract: true,
dll: ['vue', 'vue-router', 'vuex',

A list of docs that need to be written:

• how to write a custom renderer
• complete API documentation (API.md)

In the future getting the docs and usage up on a website would be ideal.

This might be helpful. Two persons already asked for supporting React and Preact.

We know that we have to add a dependency, a babel plugin (or preset) for JSX, configure ESLint etc … but it isn’t a no brainer at all.

Attached you find a patch for setting a minimal preact example.

I would like to propose using GitHubs

The website isn't currently mobile friendly.
Can you show me how I can contribute a PR to do a quick fix or otherwise add to your backlog please?