An in-range update of @types/parse5 is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 713
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
The devDependency @types/parse5 was updated from 5.0.1 to 5.0.2.
This version is covered by your current version range and after updating it in your project the build failed.
@types/parse5 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).
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 🌴
Contributor guide
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 linked failing branch and its Travis CI build details, comparing the @types/parse5 update from 5.0.1 to 5.0.2. Trace which build or test step fails after the update and identify a compatible dependency state; done means the Travis CI build passes again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100