Webpack-cli: Required git?

[sam-s4s]

I'm very confused right now.

Firstly - all I need to do is provide a path to webpack... webpack --config demo/webpack.config.js. So it seems very silly that in order to do that I need to install a whole other package for webpack.

Secondly - I can't even install webpack-cli, because it requires git to be installed on my machine (and all of my company's other dev boxed and build boxes, which is not possible).

a) why does webpack-cli require git to be installed at all? This seems like a very bad decision. We have a large pipeline, and no other packages require git to be installed - including webpack itself.

b) the fact that it requires git to be installed is not mentioned anywhere - until npm install throws an error. If this project has such a strange requirement, it should be mentioned in bold text right at the top of the documentation.

Any help or explanations would be greatly appreciated. Thanks!

[itsMapleLeaf]

It looks like one of the dependencies is a local fork from git. If we can, would we be able to resolve the issue after removing this, @ev1stensberg ?

[evenstensberg]

Removing it this week

[sam-s4s]

Ah that would be great :D

Thanks for checking that!

Also just a quick query... the current docs say...

The latest webpack release is: 4.1.1

To install the latest release or a specific version, run one of the following commands:

npm install --save-dev webpack

...

"scripts": {
    "start": "webpack --config webpack.config.js"
}

But this will not work, right, because it will also need webpack-cli ?

[ematipico]

Yeah exactly, you need webpack-cli package installed. Although as you mentioned we have a problem with one of our dependencies where they cannot be installed via proxy. We are working on a fix. The issue can be tracked here #161

[evenstensberg]

323