An in-range update of babel7 is breaking the build π¨
greenkeeper opened this issue Β· comments
There have been updates to the babel7 monorepo:
-
- The
dependency
@babel/parser was updated from7.1.0
to7.1.1
.
- The
- The
dependency
@babel/traverse was updated from7.0.0
to7.1.0
. - The
dependency
@babel/types was updated from7.0.0
to7.1.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.
babel7 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
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
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 π΄
- The
dependency
@babel/parser was updated from7.1.1
to7.1.2
. - The
dependency
@babel/traverse was updated from7.0.0
to7.1.0
. - The
dependency
@babel/types was updated from7.1.1
to7.1.2
.
Your tests are still failing with these versions. Compare changes
- The
dependency
@babel/parser was updated from7.1.2
to7.1.3
. - The
dependency
@babel/traverse was updated from7.1.0
to7.1.3
. - The
dependency
@babel/types was updated from7.1.2
to7.1.3
.
Your tests are still failing with these versions. Compare changes
- The
dependency
@babel/parser was updated from7.1.2
to7.1.3
. - The
dependency
@babel/traverse was updated from7.1.3
to7.1.4
. - The
dependency
@babel/types was updated from7.1.2
to7.1.3
.
Your tests are passing again with this update. Explicitly upgrade to these versions π
- The
dependency
@babel/parser was updated from7.1.3
to7.1.5
. - The
dependency
@babel/traverse was updated from7.1.4
to7.1.5
. - The
dependency
@babel/types was updated from7.1.3
to7.1.5
.
Your tests are passing again with this update. Explicitly upgrade to these versions π
Good bot! I think I'm running afowl of this breakage when I updated babel-eslint from 9 to 10 because npm update
doesn't by default update transitive dependencies. Removing node_modules
and package-lock.json
and npm install
fixes the problem, but to fix past versions without having to do this, I think babel-eslint needs to Explicitly upgrade to these versions
Also, I can reproduce my issue when trying to update babel-eslint at a certain point in my project, I'd be happy to test that upgrading those dependencies here does fix the update from 9 to 10.
Thank you for the issue. Now that @babel/eslint-parser
has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.