From 87810e601618765b08703c9908d3dc9ac0d6b862 Mon Sep 17 00:00:00 2001 From: Legends Date: Sat, 18 Aug 2018 10:32:59 +0200 Subject: [PATCH] removing webpack-command In response to #2447 --- src/content/guides/installation.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/content/guides/installation.md b/src/content/guides/installation.md index f8a9537b70c4..555facd5b129 100644 --- a/src/content/guides/installation.md +++ b/src/content/guides/installation.md @@ -28,18 +28,12 @@ npm install --save-dev webpack npm install --save-dev webpack@ ``` -If you're using webpack v4 or later, you'll need to install a [CLI](/api/cli/). +If you're using webpack v4 or later, you'll need to install the [CLI](/api/cli/). ``` bash npm install --save-dev webpack-cli ``` -or - -``` bash -npm install --save-dev webpack-command -``` - Installing locally is what we recommend for most projects. This makes it easier to upgrade projects individually when breaking changes are introduced. Typically webpack is run via one or more [npm scripts](https://docs.npmjs.com/misc/scripts) which will look for a webpack installation in your local `node_modules` directory: