leecade / leecade/koa-webpack-middleware
An in-range update of koa is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Version 2.0.1 of koa just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | koa |
| Current Version | 2.0.0 |
| Type | peerDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As koa is “only” a peerDependency 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
- ❌ ci/circleci Your tests failed on CircleCI Details
Commits
The new version differs by 43 commits (ahead by 43, behind by 1).
6c6aa4d2.0.14e5deaehistory++6506108package: remove publish tagd4b3223docs++f191c0dpackage: oops re-add babel-eslinta7c4236fix: add named arrow function for request and response handlers (#805)cd02834travis: only test node v7.6.0+9671addtest: remove babel tests as they are no longer needed in node v7.6df7b4ffdocs: replace the reference to co00156dfremove unused app.name (#899)152b6d7Fix response.status default value documentation (#889)8435268Upgrade mocha (#900)d48291fRelease 2.0.0-alpha.87ae9c3eFix malformed content-type header causing exception on charset get (#898)2db3b1bFix typo for accepts(). (#863)
There are 43 commits in total. 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 with the failed ci/circleci run linked in the issue and compare the greenkeeper/koa-2.0.1 branch with the current dependency configuration. Identify why koa 2.0.1 breaks the build, update the dependency or compatibility as appropriate, and confirm CircleCI passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100