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

The dependency babel-loader was updated from 8.0.2 to 8.0.3.

🚨 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

• ✅ deployment/now: Deployment has completed (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v8.0.3

Features

• #687 - Add customize option

Bugs

• #685 - Also pass the caller option to loadPartialConfig

Docs

• #681 - Update the README links to use the new options docs
• #683 - Add .mjs to the examples

Internal

Some dev dependency updates and CI tweaks.

Commits

The new version differs by 12 commits.

• 800181b 8.0.3
• 7d8500c Also pass the caller option to loadPartialConfig (#685)
• a507914 Expose the full loader options to all overrides hooks.
• ac0c869 Tweak the customize implementation to be a bit more strict.
• 9b70a02 Add overrides option
• c8d7a72 Add .mjs to the examples (#683)
• 4619993 bable options link update (#681)
• 8f240b4 Use node 10 on appveyor
• 7e4189e Change appveyor to use babel account
• eeaee46 Update devDeps to use most recent versions, and fix tests.
• 3e5fb5e chore(package): update lockfile
• 2b8e479 chore(package): update eslint-config-babel to version 8.0.0

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 🌴

[nvwebd]

Maybe this could help: https://github.com/zeit/next.js/issues/5231 ?

Seems something like this.

Build Log says:

Module build failed (from ./node_modules/next/dist/build/webpack/loaders/next-babel-loader.js): ReferenceError: Unknown helper getPrototypeOf

and so forth. Seems a “next” config problem?

And I can normally build on this branch … Locally at least. Docker image is another story: I’ve got lots of imports unresolved:

import { getCodeSchoolsPromise } from '../common/constants/api';

this works but the original

import { getCodeSchoolsPromise } from 'common/constants/api';

fails to import…

Just give me a day to read into the code 😉

[kylemh]

My babel config may be off now that babel 7 is being consumed by our biggest libraries.

Potentially may need something like this, but the Babel 7 way: https://github.com/zeit/next.js/issues/4291#issuecomment-398447718