amd-graph --linearize option did not sort topologically
New feature: amd-normalize and amd-resolve can now accept input from stdin
New command: amd-unused - finds unused modules in a project
Allow a leading slash for --base-url to better accomodate RequireJS
configurations running on web servers (the vast majority). Also try
process.cwd() as a default value for --entry-point (the web server root) when
trying to pin down the absolute path of --base-url.
Avoid throwing errors when passed modules with the special '??' "directory",
which is used to denote shimmed modules which may not actually exist. This can
happen implicitly when the --recursive/-R option of some commands is used to
trace the dependency graph of each explicity passed module (getDependencyGraph
in libamd will return these '??' paths when leaves in the graph do not exist on
the filesystem).
Bug in amd-check and most other commands: when passed "common" options like
--base-url, the <module> or <pool> argument to each of these commands could be
misinterpreted. This was due to the option parser not knowing about the common
options.
Added an automatic configuration detection fallback if no explicit
configuration (--config, --base-url, --entry-point, .amdconfig file) is
provided.