An in-range update of @types/node is breaking the build 🚨
- Dominant language
- TypeScript
- Stars
- 5.3k
- Forks
- 364
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 3
Description
## The devDependency [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) was updated from `10.12.21` to `10.12.22`.
🚨 [View failing branch](https://github.com/benjamn/recast/compare/master...benjamn:greenkeeper%2F%40types%2Fnode-10.12.22).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
@types/node is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/benjamn/recast/builds/490342837?utm_source=github_status&utm_medium=notification)).
---
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Greenkeeper failing branch and inspect Travis CI build 490342837 to identify what @types/node 10.12.22 breaks. Done means the dependency update no longer causes the project build to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100