ff-stream-web

git clone git://archive.git.mtrnord.blog/MTRNord/ff-stream-web.git
Log | Files | Refs | README | LICENSE

commit 35c04b77ca650d3258b59552325fe9aaf3bf78db
parent d496698e9be478774e004d6135d27b8fa522385d
Author: Konstantin Tarkus <koistya@gmail.com>
Date:   Wed, 17 Feb 2016 06:47:15 +0300

Merge pull request #445 from alexwhb/patch-1

fixed a typo
Diffstat:
Mdocs/recipes/using-npm-and-webpack-as-a-build-tool.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/recipes/using-npm-and-webpack-as-a-build-tool.md b/docs/recipes/using-npm-and-webpack-as-a-build-tool.md @@ -40,7 +40,7 @@ platforms (Mac OS X, Windows, Linux). The same way you can run [Webpack](http://webpack.github.io/) module bundler to compile the source code of your app into a distributable format. Since -Webpack has numerous of [configuration options](http://webpack.github.io/docs/configuration), +Webpack has numerous [configuration options](http://webpack.github.io/docs/configuration), it's a good idea to have all of them in a separate configuration file, as opposed to feeding them to Webpack's CLI as command line arguments. As a rule of thumb, you want to keep the "scripts" section in your `package.json` file