Deprecate koa-bodyparser

[AaronMoat]

Hi there,

It looks like in #152 the package name was changed.

Should we deprecate the old name, so consumers know to go to the new one? Alternatively, revert the name change given the number of dependents?

• koa-bodyparser has 2593 dependents: https://www.npmjs.com/package/koa-bodyparser?activeTab=dependents
• @koa/bodyparser has 12 dependents: https://www.npmjs.com/package/@koa/bodyparser?activeTab=dependents

[3imed-jaberi]

@titanism could you work around this task due to blurring for the publishing process ...
We need similar behavior to what we have on the router module, once we publish a new release we need to publish for 2 names/alias on npm;

• https://www.npmjs.com/package/koa-router
• https://www.npmjs.com/package/@koa/router

And/or we need to add a deprecation message for the koa-bodyparser module.

@titanism I will contact you on the coming days through slack or email!

[tadhglewis]

Can we action this? There's bugs in koa-bodyparser which have been fixed by @koa/bodyparser such as #162 so we have a lot of services using an abandoned yet-not-deprecated package

Also it'd be great to have #164 merged beforehand so migrating off the deprecated package doesn't require a new dependency!