1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

嗨, 您好
在學習CH05的時候,遇到一個問題
發現在 webpack.config.js 裡面的 module: { preLoaders: [ { ... } ],
似乎造成webpack錯誤 無法執行

如下terminal截圖

稍微查了一下,解決方法是用 webpack@2.1.0-beta.22 版本
我目前是 "webpack": "^2.2.0", _應該也

Any refrence on how to enable swagger documentation on the express routes ?

Currently in your examples is hard to determinate what attributes should be applied to get exact results without checking the source code of a demo files.
So I suggest to use the https://github.com/storybooks/storybook

Improve the readme.md documentation before 1.0 release.

• improve configuration section (specifically concerning outputs)
• improve documentation on usage of lib/sharp tarball
• add sample/example configuration files in ~/examples including how to setup with a single bucket, single existing bucket, etc.
• add a bit about what IAM permissions are required to deploy with Serv

I think it would be nice to have an organized overview of all the features on the README. Ideally, this would give the public an idea of what distinguishes this package from others, which is quite a lot. And then perhaps move all the release history stuff to CHANGELOG.md?

If this sounds okay, I can get a PR started in the next few days/weeks.

Hello,

First of all, thank you very much for this amazing project. It is what LS needs, from my perspective.
However, the entry point for a total newcomer is a bit tough.
I've been reading documentation a couple of times and I'm still not clear, and the fact that examples are on LS is not helping either.
Seems that I have to write a compiler file, with a babel options inside it ? This is a b