Update babel-loader: 8.0.6 → 8.2.5 (minor)

[depfu]

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?

✳️ babel-loader (8.0.6 → 8.2.5) · Repo · Changelog

Release Notes

8.2.5

What's Changed

• fix: respect inputSourceMap loader option by @alan-agius4 in #896

New Contributors

• @alan-agius4 made their first contribution in #896

Full Changelog: v8.2.4...v8.2.5

8.2.4

What's Changed

• doc(README.md): fix a broken markdown link by @loveDstyle in #919
• Bump loader-utils to 2.x by @stianjensen in #931
• Use md5 hashing for OpenSSL 3 by @pathmapper in #924

Thanks @loveDstyle, @stianjensen and @pathmapper for your first PRs!

8.2.3

This release fixes compatibility with Node.js 17

• Use md5 hash for caching on node v17 (#918)

Thanks @Reptarsrage!

8.2.1

• Move @ava/babel to devDependencies #881 (@jvasseur)

8.2.0

• Replace mkdirp with make-dir 47958ca (@JLHwung)
• Use async config loading when available d8cff97 (@the-spyke)

8.1.0

• docs(readme): fix typo #818 (@frederickfogerty)
• docs(contributing): fix typo #821 (@PatNeedham)
• Add schema validation #822 (@ogonkov)
• Add supportsTopLevelAwait to caller #814 (@nicolo-ribaudo)
• feat: expose webpack target via babel caller #826 (@DylanPiercey)
• Bump deps for audit #834 (@existentialism)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 52 commits:

• 8.2.5
• fix: respect `inputSourceMap` loader option (#896)
• 8.2.4
• Use md5 hashing for OpenSSL 3 (#924)
• Bump loader-utils to 2.x (#931)
• doc(README.md): fix a broken markdown link (#919)
• 8.2.3
• Use `md5` has for caching on node v17 (#918)
• chore: update readme example (#907)
• Fix failing main (#903)
• fix: add all babel config files to file dependency (#887)
• Add note about top-level IIFE to the 'Troubleshooting' section (#886)
• docs(readme): options.metadataSubscribers (#857)
• 8.2.2
• Upgrade dependencies & replace pify (#884)
• Add trouble shooting about how to transpile node_modules (#883)
• 8.2.1
• Test on Node.js 8 (#882)
• Move `@ava/babel` to `devDependencies` (#881)
• 8.2.0
• master -> main [skip ci]
• Use Yarn 2 (#878)
• Update `devDependencies` (#879)
• fix: use async config loading if available (#825)
• Update Babel (#876)
• docs(src/cache): update JSDoc comments (#846)
• test: apply webpack@5 (#868)
• Add docs for using babel with Webpack (#869)
• Remove build badges from README
• ci: migrate to github ci (#867)
• Bump elliptic from 6.5.1 to 6.5.3 (#860)
• Bump lodash from 4.17.15 to 4.17.19 (#859)
• Merge pull request #839 from babel/replace-mkdir-by-make-dir
• chore: replace mkdirp by make-dir@2
• 8.1.0
• Bump deps for audit (#834)
• Bump acorn from 6.3.0 to 6.4.1 (#828)
• feat: expose webpack target via babel caller (#826)
• Merge pull request #814 from nicolo-ribaudo/tla
• Update src/injectCaller.js
• Add schema validation (#822)
• Merge pull request #821 from PatNeedham/docs/contributing-typo
• docs(contributing): fix typo
• docs(readme): fix typo (#818)
• Add supportsTopLevelAwait to caller
• chore: Do not run node 6 in appveyor
• chore: Upgrade more dev dependencies
• chore: Update some dev dependencies
• Bump eslint-utils from 1.3.1 to 1.4.2 (#806)
• Bump mixin-deep from 1.3.1 to 1.3.2 (#807)
• Bump lodash.merge from 4.6.1 to 4.6.2 (#801)
• Bump lodash from 4.17.11 to 4.17.14 (#800)

---

👉 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:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with 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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)