An in-range update of espower is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 2.0.1 of espower just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | espower |
| Current Version | 2.0.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As espower 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
Commits
The new version differs by 5 commits .
-
63500832.0.1 -
dfe87c3docs(CHANGELOG): add CHANGELOG for 2.0.1 -
869ed49Merge pull request #34 from power-assert-js/arrow-function-with-concise-body -
19d2a78fix(espower): use upper block when assertion is a concise body of ArrowFunctionExpression -
02900d5chore(travis): gulp is installed locally
See the full diff.
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 by reproducing the failed build with espower 2.0.1 using the linked CircleCI and AppVeyor build results, then compare it with the current 2.0.0 dependency. Trace the failure in the project’s build or test entry points and verify that the dependency update no longer breaks the build or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100