Release `next` branch to npm about mount HOT 5 CLOSED

@jonathanong May I publish koa-mount@2 (Of course as dist-tag next)

from mount.

+1 from me. Looks fine, assuming next dist-tag.

from mount.

Since existing next branch has never been published, and according to koajs/koa#625, just close this for now.
I'm going to delete the existing promise based next branch.

from mount.

imo-

• if there's already a working next branch and koa convert doesn't work for mount, i'd just publish this to npm
• if koa convert does work for mount, ignore this. no point of converting to promise-based middleware

from mount.

Why was the branch decidedly deleted? Was it clutter?

Edit: Ahh I see it utilized promises instead of just async/await. Unfortunately that didn't affect me because Babel replaced async/await with Promises anyway, so they were one and the same. Implementation was compatible.

from mount.