Update webpack-command to the latest version 🚀 #113
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.3.0 of webpack-command was just published.
[webpack-command](https://github.com/webpack-contrib/webpack-command)
The version 0.3.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of webpack-command.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v0.3.0Bugfixes
Features
wp
binary in package to avoid binary name conflicts (#40)Updates
webpack-command
is no longer just a proof of concept, but a legitimate replacement for webpack-cli.Commits
The new version differs by 15 commits.
11e7799
chore(release): 0.3.0
77e6411
chore: update circleci config
9c232b7
test: update relative path reporter test snapshot
a5cff71
feat: allow --reporter to be relative to CWD (#24)
5786adc
docs: update README details
17a73b4
chore: eslint@5 has issues with eslint-webpack-config. downgrade
a31d9c5
chore: update deps, metadata
19b486a
test: update reporter snapshots for context fix
ec64060
fix: add handling for exit codes on error (#35)
76f6869
feat: add JSON reporter. fixes #16 (#39)
5afbcee
feat: export
wp
binary in package to avoid binary name conflicts (#40)331eb8d
fix: context overriden by flags default value. fixes #36 (#38)
204b5f9
feat: warn if bail is used in watch mode (#21)
32d4f63
docs: remove "proof of concept" from description
75ff73c
fix: define flag documentation, run-dev and run-prod implementation (#34)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴