-
-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Required git? #318
Comments
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 ? |
Removing it this week |
Ah that would be great :D Thanks for checking that! Also just a quick query... the current docs say...
But this will not work, right, because it will also need webpack-cli ? |
Yeah exactly, you need |
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!
The text was updated successfully, but these errors were encountered: