In Node.js global package installs should only be done for those tools where we need to have global $PATH
access to that bin/executable. That is to say, when we need command line access to the command at any path in our file system tree.
The following list of packages are some commonly found in my global assembly:
- coffee-script
-
clean, elegant and succinct JavaScript derivative: drop brackets and enter significant white space, often used by me for
.litcoffee
- nesh
-
REPL for node.js with autocomplete and color tree parsing of objects in JS and CS: highly modular
- season
-
better CSON to JSON parsing with
csonc
command although neither this author, norcson2json
author Bevry seem to get the idea behind stdin. Also annoying that.cson
extensions are required, both have very few options - npm-research
-
better npm sesrch results with popularity index number for viewing which have been downloaded/used (not sure) a lot
- json
-
JSON pretty printing / formatting from the command line, can be used when CSON produces minimized or garbled output
- js2coffee
-
convert JavaScript to CoffeeScript easily, set a shell wrapper or alias to cover for your 4-spaced indent if you want it (I do) since default is
2
- loopback
-
LoopBack is a highly-extensible, open-source Node.js framework. Quickly create dynamic end-to-end REST APIs. Connect devices and browsers to data and services.
- jslint
-
check your JavaScript against best practices