Skip to content
This repository was archived by the owner on Apr 24, 2019. It is now read-only.

Conversation

@edorivai
Copy link

@edorivai edorivai commented Oct 24, 2017

First attempt to upgrading to Koa 2.

Solves #37

Summary

  • Tested on Node 7.10.1 and 8.5.0
  • Updated a bunch of dependencies
  • Replaced all use of generators with async functions

Problems

I have all test passing, except the encoding test. The problem with this test is that if you want to decode the response body, you'll have to wait for the entire stream to finish. I'm not sure whether decoding the response body should really part of this library. One could simply decode in an upstream middleware if they want, right?

So I have commented out the decoding, and switched the test to pending. Please let me know if you want to keep support for decoding, we can discuss options.

Version

I guess this would be a major version bump, since it will require Koa 2.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling e8a6d36 on edorivai:master into ** on popomore:master**.

@coveralls
Copy link

coveralls commented Oct 24, 2017

Coverage Status

Changes Unknown when pulling 5bac2f9 on edorivai:master into ** on popomore:master**.

@coveralls
Copy link

coveralls commented Oct 24, 2017

Coverage Status

Changes Unknown when pulling fbef5fe on edorivai:master into ** on popomore:master**.

@coveralls
Copy link

coveralls commented Oct 24, 2017

Coverage Status

Changes Unknown when pulling 2a717ca on edorivai:master into ** on popomore:master**.

@moaxaca
Copy link

moaxaca commented Nov 15, 2017

Please get this merged or publish the fork on NPM. <3

@mbarisa
Copy link

mbarisa commented Mar 2, 2018

Can we get this merged?

@chrisveness
Copy link
Contributor

Since @popomore has apparently abandoned koa-proxy, could you see if npm would transfer the package name to you for you to take the project over?

I think it would be much appreciated!

@edorivai
Copy link
Author

edorivai commented Apr 4, 2019

@chrisveness I've emailed @popomore, and CC'd npm support. On their disputes page, npm indicates it may take a couple of weeks, so stay tuned!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants