-
-
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
[Feature] #199
Comments
@TheLarkInn @ev1stensberg @sokra sorry if this has been discussed elsewhere (I searched and didn't find anything), but why was The standard for separate CLI packages seems to be the other way around: the CLI depends on the node API. For example, If it's simply because you want installing the It seems odd for |
#202 #203 , @billyjanitsch yep, you're right 👍 |
@ev1stensberg I don't think #202 is quite right. I'm suggesting that If you want |
@billyjanitsch We're gonna make the CLI a peerdep in webpack before releasing |
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
This package is installed using npm
If the current behavior is a bug, please provide the steps to reproduce.
If this is a feature request, what is motivation or use case for changing the behavior?
Since now this is a dependency of webpack/webpack, we should probably also move this over to yarn as well. Initial testing shows trying to link webpack/webpack locally wasn't working to friendly with webpack-cli.
webpack-cli@latest
The text was updated successfully, but these errors were encountered: