Closed dasoncheng closed 6 years ago
for koa v1
yarn add koa-body@latest
for koa v2
yarn add koa-body@next
This strategy can cause confusion when using automated dependency alert systems, and feels a bit odd given the ubiquity of koa2.
I would strongly prefer keeping the latest
tag in sync with the latest stable release, as this is the behavior I've come to expect from broader norms in the npm community.
(Oh, and fantastic library, btw! 😊)
The intention at the time was to follow the koa tag convention.
Will migrate to the following tags, following koa's tagging scheme https://www.npmjs.com/package/koa
2.6.0 latest