chore(upgrade): webpack 4.2 and other dependencies

[dhruvdutt]

No description provided.

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[ematipico]

This is something that bugs me. Shouldn't we have ^4.0.0 and that's it? If not, why?

[montogeek]

Why does it bugs you?

[ematipico]

The cli should have a loose dependency from webpack as far as I understood. The cli uses only some utilities from webpack. So I still have some unclear thoughts about how this relation is inside the cli. Just personal doubts :)

[dhruvdutt]

About loose dependency, I think it depends on the peer dependency which is currently "^4.0.0".

webpack-cli/package.json

Lines 109 to 111 in 2222f1d

	"peerDependencies": {
	"webpack": "^4.0.0"
	},

IMO we should keep our project's dependencies up to date to update the lock file since all npm installation would pick from the versions specified in lock file and not the latest version based on ^ (unless you remove the lock file explicitly before npm installations).

The loose dependency should still carry as it's a peer.

[ematipico]

Thanks!

[webpack-bot]

@dhruvdutt Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@ev1stensberg Please review the new changes.

[dhruvdutt]

Upgraded yargs as well.