Came to say the same... also, if I see anything else called "Unity" in software, like ever, I'll just go on an insane unidirectional killing spree (not really, but it's irritating to say the least).
I had expected a blog series on SOLID principles applied to JS.
Interesting... wondering how many breaking changes there are, and if it would be possible to shim a few of them, and just make this "npm@4" somewhere in node@7 before the branch to node@8 starts.
I really hope that the final result will be some of the effects of yarn going into npm4 instead of a long term fragmentation here. I'm still looking at projects that are/have used bower, and that's enough to make things annoying, to say the least. At least Yarn seems to build on npm's conventions.
Not ES6, but with async/await, I tend to put this in the top of quite a few of my files, easier as a oneliner than pulling in from a library module a lot of the time.
const sleep = ms => new Promise(res => setTimeout(res, ms));
Said this earlier... I’ve pretty much rallied against any package manager that needs node+npm to install in the first place, it’s mostly redundant. In this case, it appears to work in line with the node_modules, package.json, and npm’s services, so I’m less disturbed by it… would prefer to see some push to get these changes aligned *in* npm@4/node@8, as there will be a lot of shifting for es6-style module support in that timeframe anyway.
I believe it was recently moved to stage 4... I've been using async functions since fairly early on (nearly 2 years now) via babel, and have to say, what the do for your async code is awesome... even Promise chains are very ugly by comparison.
again.. not sure why this is so hard to spread... const sleep = ms => new Promise(res => setTimeout(res, ms)); ... await sleep(10000);Not ES6, but with async/await, I tend to put this in the top of quite a few of my files, easier as a oneliner than pulling in from a library module a lot of the time. const sleep = ms => new Promise(res => setTimeout(res, ms));