Update webpack-dev-middleware: 3.7.0 → 3.7.1 (patch) #20
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ webpack-dev-middleware (3.7.0 → 3.7.1) · Repo
Release Notes
3.7.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 50 commits:
chore(release): 3.7.1
chore(deps): update dependency husky to ^3.0.5 (#462)
chore(deps): update dependency eslint to ^6.3.0 (#460)
chore(deps): update dependency cross-env to ^5.2.1 (#461)
fix: the `writeToFile` option has compatibility with webpack@5 (#459)
chore(deps): update all patch dependencies (#444)
chore: update deps (#458)
chore(deps): update jest-junit to v8 (#456)
chore(deps): update package-lock.json (#457)
chore(deps): update dependency file-loader to v4 (#416)
chore(deps): update dependency eslint to ^6.2.0 (#455)
chore(deps): update all minor dependencies to ^24.9.0 (minor) (#454)
refactor: lib/util.js (#452)
chore(deps): update dependency webpack to ^4.39.0 (#450)
chore(docs): fix typo (#449)
chore(deps): update dependency standard-version to v7 (#448)
chore(deps): update dependency webpack to ^4.38.0 (#447)
chore(deps): update dependency eslint to v6 (#426)
chore(deps): update dependency jest-junit to v7 (#446)
chore(deps): update dependency webpack to ^4.37.0 (#445)
chore(deps): update deps (#442)
chore(deps): update all minor dependencies (#431)
chore(deps): update lint-staged and @commitlint/cli (#441)
fix: displayStats only logged (#427)
fix: directly used mkdirp instead of through Webpack (#436)
chore(renovate): update config (#438)
chore(deps): update dependency husky to v3 (#434)
chore(deps): update dependency webpack to v4.35.2 (#432)
chore(deps): update dependency eslint-plugin-import to v2.18.0 (#429)
chore(deps): update dependency @webpack-contrib/defaults to v5.0.1 (#430)
chore(deps): update dependency husky to v2.5.0 (#428)
chore(deps): update dependency webpack to v4.35.0 (#425)
chore(deps): update dependency lint-staged to v8.2.1 (#424)
chore(deps): update dependency webpack to v4.34.0 (#423)
chore(deps): update dependency husky to v2.4.1 (#422)
chore(deps): update dependency prettier to v1.18.2 (#421)
chore(deps): update dependency prettier to v1.18.1 (#420)
chore(deps): update dependency prettier to v1.18.0 (#419)
chore(deps): update dependency lint-staged to v8.2.0 (#418)
chore(deps): update dependency husky to v2.4.0 (#417)
chore(deps): update dependency webpack to v4.33.0 (#415)
chore(deps): update dependency commitlint-azure-pipelines-cli to v1.0.2 (#414)
chore(deps): update dependency @webpack-contrib/defaults to v5 (#413)
chore(deps): update commitlint monorepo to v8 (#412)
chore(deps): update dependency @webpack-contrib/defaults to v4.1.1 (#407)
chore(deps): update all patch dependencies (patch) (#408)
Create FUNDING.yml
chore(deps): update all patch dependencies (patch) (#406)
chore(deps): update dependency webpack to v4.32.0 (#404)
chore(deps): update dependency express to v4.17.0 (#403)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/
.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands