NG
NG copied to clipboard
nodejs
Next Generation JavaScript IO Platform
iojs -t
Transpilation is here to stay. Even though IOJS ships with **some** ES6 features, I find myself using `babel-node` all the time because I want other features that are not presently...
If issues of this repository are considered as proposals for NG, maybe doing a list showing rejected proposals (and the reason), deferred proposals, still discussing proposals and already approved proposals...
With ESNext, there's a whole suite of new functionality previously provided by core. Given the opportunity for breaking changes, NG should strive to be idiomatic JavaScript in all regards (**EDIT:**...
Related to ES6 modules, https://github.com/nodejs/NG/issues/5, and following a lengthy discussion in https://github.com/npm/npm/issues/8222. Obviously, I'm not talking about `require()` here, changing it would be insane. But since ES6 module loader would...
I'm going to try and write out some of my most recent thinking about NG. What I first thought of as an opportunity to adopt new patterns I now see...
It's time to start thinking about things we can implement today that set us up for some of the bigger ideas we've been talking about in this repo. After a...
any chance of code coverage? i'm sure many people would love to help add tests. specifically, this would help protect against issues like https://github.com/iojs/io.js/pull/1412 where features that weren't ever tested...
Existence of modules like `fs-plus` or `fs-extra` seems to be an indicator that current `fs` module can be not enough. For example there are no methods for copying / moving...
Recently `co` moved to using promises, or more specifically yielding promises. https://github.com/tj/co There's been talk of having APIs in NG return promises. What are the downsides/upsides of return vs. yield?
As of right now, there exists a wonderful HTTP module, which interweaves libuv, the http_parser, v8 and JavaScript into a perfect request and server suite, complete with all the features...
