An in-range update of babel-runtime is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Version 6.23.0 of babel-runtime just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-runtime |
| Current Version | 6.22.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-runtime is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the greenkeeper/babel-runtime-6.23.0 comparison and the linked Travis CI build to identify why the dependency update fails. Update babel-runtime to a compatible version or adjust the dependency configuration, then confirm that the Travis CI build passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100