-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support koa@2 #41
Comments
@kunyan are you planning on making a PR? |
@vhpoet I can't push a new branch to upstream :( |
@kunyan can you publish this as a module, perhaps koa-cors-next ? |
@evert0n can you checkout a new branch named "next". and I will create a PR to it. I think this way will be better. |
I check it out this weekend guys, I will also catch up with the other issues too, Thank you |
Just in time for the arrival of native |
exactly. one more thing we don't have to have babel transpile |
@evert0n - any update to this? thanks! |
@evert0n - hey, is there any possible update to this? |
pls use this until @evert0n push new patch
|
What's needed to get @kunyan's changes into an official release? Would be nice to get rid of the deprec warning. :) Thanks! |
It would be great to get @kunyan's change published to npm as koa-cors@next. What is the next step? |
Until this gets merged, you can use https://github.com/th507/koa-adapter to get rid of the deprecation warning. |
Guys, you can use CORS from main organization https://github.com/koajs/cors. |
Hi @evert0n would you be open to having someone else help maintain this library? |
@bradleyayers why not just use the module maintained by the project? https://github.com/koajs/cors |
@shellscape that's a great q.. I can't remember why I didn't personally use it, but I vaguely remember being some reason. I should probably take a second look at it. thanks for the tip. |
Are you planning to support koa@2?
The text was updated successfully, but these errors were encountered: