NodeJS is best suited to high IO workloads with relatively light processing requirements. These arise out of the evened nature of `libuv` and the lack of a lightweight threading or fiber API for NodeJS. This may change over time, however the contemporary approach (2019) is to spawn additional processes to handle computational concerns.
NodeJS versus IOJS
In early 2015 core contributors finished a fork of NodeJS rebranded as io.js. They updated the v8 runtime and poured a great deal of effort into ensuring libraries supported both platforms. With the updated v8 runtime newer ES6 features are supported in addition to a number of bug fixes and other improvments.
Node Package Manager (NPM)
Not technically apart of node it's self, however this system is the default dependency manager for the system.
NPM provides an awesome mechanism to list the outdated dependencies of a proejct.
This will list dependencies on the stadnard output of the process.
Notes - To be expanded on later
- Autmoated workflow for browser related code: http://24ways.org/2013/grunt-is-not-weird-and-hard/ Another!: https://www.erianna.com/using-grunt-to-minify-and-compress-assets