NPM 4 was released recently, about 2 weeks ago, and with it came some major changes. Some breaking, some not, but there is an interesting deprecation that happened with regards to the prepublish script. Currently, if you had a prepublish entry in your package.json: { scripts: { prepublish: "nsp check" } } This would be run whenever you performed a npm publish. Which is probably what you would expect with a name like prepublish. Another thing was also happening though...
Node.js 7.0.0 was released just last week, and the announcement dropped a bombshell. I'm guessing the following announcement might freak some people out: DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. While the UnhandledPromiseRejectionWarning has been in node since 6.6.0, this deprecation warning is new --- basically, it means you've rejected a promise in your code, but you are not handling it, and...
Node.js is a JavaScript runtime built on top of Chrome's V8 JavaScript engine. It is highly event-driven, and leverages non-blocking I/O model that makes it lightweight, efficient, and incredibly productive to use. It's that last bit, "productive", that I want to focus on today. One of the things that i feel makes Node(and NPM) so great is the ease in which you can add and use third-party modules. As most node.js developers know, to start using an external module, you...
Article
