An in-range update of babel-loader is breaking the build 🚨

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The dependency babel-loader was updated from 8.0.6 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

babel-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

Release Notes for 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)

Commits

The new version differs by 18 commits.

• 3ff9926 8.1.0
• 0817bb6 Bump deps for audit (#834)
• ecb2b02 Bump acorn from 6.3.0 to 6.4.1 (#828)
• 13a8238 feat: expose webpack target via babel caller (#826)
• b568420 Merge pull request #814 from nicolo-ribaudo/tla
• 1c35731 Update src/injectCaller.js
• 5f55638 Add schema validation (#822)
• 8b47312 Merge pull request #821 from PatNeedham/docs/contributing-typo
• a967311 docs(contributing): fix typo
• 758d4b5 docs(readme): fix typo (#818)
• 8a0a25a Add supportsTopLevelAwait to caller
• 15df92f chore: Do not run node 6 in appveyor
• 26d1676 chore: Upgrade more dev dependencies
• 26aa687 chore: Update some dev dependencies
• a961168 Bump eslint-utils from 1.3.1 to 1.4.2 (#806)

There are 18 commits in total.

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 🌴

[greenkeeper]

After pinning to 8.0.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.