@next is confusing across all packages

[niftylettuce]

We should standardize how we address packaging this version-wise, and then go out to all packages using Koa@next and let them know of the standards. This is super confusing to end-users. It seems like Koa@next is unstable by not being the latest. Is Koa@1.x even really used as much as Koa@2.x? It's just super confusing to package maintainers to have to make a version that's not the latest but SHOULD be used (since it's newer/better - we should just add deprecation notices to people if they install a new version that is using koa@next? maybe we standardize the deprecation notice?).

[jonathanong]

i wish i knew usage statistics between v1 and v2.

[niftylettuce]

@jonathanong I reached out to NPM support, let's get them numbers!

[dead-horse]

we are using v1 with 100+ production apps and more than 40, 000 download per month(from our private registry). :)

[niftylettuce]

Is Koa@next not stable or something? Can't we release an official version? There's native Promise support now.

[PlasmaPower]

Quick observational study: koa-static introduced Koa v2 support on March 24th. Looking at the per month download graph at npm-stat I see no increase with the introduction of Koa v2. However, this is probably due in large part to koa-convert being used in place of v2 support. This does, however, imply that either Koa v2 is not being used very much (unlikely) or Koa v2 users are fine with using koa-convert for important parts of their system for the time being (likely).

@niftylettuce The plan is to wait until async/await support arrives stable in Node, so users will get a more function*/yield style experience.

[niftylettuce]

@PlasmaPower that makes sense - any idea when async/await will get added in Node stable? Is there a blog post about it or any GH issues on Node side?

[PlasmaPower]

@niftylettuce nodejs/promises#4 is the main one. It's landed in git, but it'll be a while before it's in a release. In addition, it'll probably be hidden behind a harmony flag first. We have yet to decide if we'll be releasing Koa v2 then, or when it becomes default, but it looks like we won't be waiting for it to be default (see discussion in #533).

[onbjerg]

@niftylettuce It's "expected" to come out in 2017 (all finished proposals for the next versions of ES are listed here).

[ide]

async/await is now in Chrome 55 (stable) without a flag and will likely ship with Node 8 which is slated for April 2017 and perhaps a Node 7.x release if V8 5.5 gets merged (in progress but who knows what the outcome will be). That being said, I don't think it's actually helpful to wait for Node 8 because even if the latest version of Node supports async/await, everyone on Node 6 or 7 for example will need to compile their async/await code to generators anyway...

[ralyodio]

Its working with node v7 and harmony flag: --harmony-async-await

[ide]

@chovy FYI the async/await flag introduces a memory leak which isn't fixed until V8 5.5 gets backported to Node 7 or Node 8 is released. I imagine most people won't want to use native async/await yet for that reason. nodejs/node#9339

[lopezjurip]

Well, good news: nodejs/node#11029

[bonesoul]

it happened: https://nodejs.org/en/blog/release/v7.6.0/