使用 Mock mock 数据的时候，需要硬编码数据到代码里面

使用 easy-mock 需要外网访问

使用 http-mock-middleware 仅仅需要新增如下 devServer.after 的配置项，就可以很方便的管理假数据，也方便开发者任意的修改假数据，而不需要提交：

const httpMockMiddleware = require("hm-middleware");

module.exports = {
    devServer: {
        after: function(app, server){
            app.use(httpMockMiddleware({
      

Section: Optimizing - Minifying - Minifying Css
By default, the cssnano would remove the vendor prefix of the stylesheet. So I think it better to disable the autoprefixer, or at least inform the reader somewhere in this section.

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

A pull request by @vankop was merged and maintainers requested a documentation change.

See pull request: webpack/webpack#10557

We need to make this example mobile responsive.

Any takers?

svg-sprite-loader is good loader for svg.

But the example custom-runtime-generator only include React.

I create a repo for use svg-sprite-loader in vue through runtime-generator.

Please see this repo: https://github.com/Akimyou/svg-sprite-vue-generator

But i want to add some example in svg-sprite-loader main repo or in docs, can U give me some suggestion about it?

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

It would be helpful to have tooltips or documentation to explain the significance of "weighted" vs. "size", and "dependants" vs "imports".

This could be useful for contributors to test any changes (manually for now) inside the repo, not having to use an external environment.
This folder should be in .npmignore.

Automated testing I think is out of the scope of this project since it's more of a wrapper plugin for Browsersync.
Perhaps some unit tests for the css emissions check?