An in-range update of whatwg-fetch 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 1.1.0 of whatwg-fetch just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | whatwg-fetch |
| Current Version | 1.0.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As whatwg-fetch is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 48 commits .
-
76f6a09fetch 1.1.0 -
08e6a85Attach FileReader event handlers before calling itsread*method -
a8695f9Merge branch 'array-buffer' -
abfe072Shorten body extraction tests -
9a703baArrayBuffer can now be consumed throughblob()/text() -
9a04a06Share identical tests between Request & Response -
7f55e03Remove duplicate test -
578784eSimplify ArrayBuffer tests -
7021a0cMerge branch 'master' into array-buffer -
4949171Definenpm testscript -
5f9254fRemove Bower dependency in development -
5fd8402Default Response status is 200 OK -
4528229Merge pull request #430 from mislav/array-buffer-view -
211d5caSupport ArrayBuffer in BodyInit -
25f7646Test against PhantomJS 2.1.1 on Travis
There are 48 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 CircleCI and AppVeyor builds linked in the issue, then compare the Greenkeeper whatwg-fetch 1.1.0 branch with the current project state. Identify the reported build failure and verify that the dependency update no longer breaks the project’s build and 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
- Needs clarification
- Newbie friendliness
- 35/100