This package has been deprecated
Deprecated in favour of the npm-which & npm-run packages :)
bin-path gives you absolute paths to dependee modules' executable scripts.
This module's approach does not work for modules that do not have a 'main' in their package.json.
This is fixed in timoxley/npm-which which duplicates npm's PATH setting machinery.
// pass in require so we can resolve relative to the calling module.var binPath = require
npm binwill return the location of the
node_modules/.bindirectory, but it does not take into account being called within the context of another module, this is a problem because:
- You can't rely on
__dirname + '/node_modules/'actually containing your module, the module may exist higher in the hierarchy due to deduping. If the module does exist higher, then
node_modules/.binwill also be missing for your module.
- Shelling out to
npm binis slow anyway; it has to wait for all of npm to boot up, and npm is a heavy dependency to include if all you want is to get a bin path.
- Relying on hard paths to executables is brittle e.g. linking directly to a module's
bin/executable. Using the the
package.jsonallows module authors to change the path ofthe actual executable without breaking dependee modules. Finding the actual path to the executable is also a problem because of point 2 above.
bin-path resolves module location, and loads
package.json directly, resolving to normalized, absolute paths.
Invoke your modules via npm scripts (e.g. npm start), this will set up the
$PATH to find
executables correctly. This still incurs the startup time of npm though, and isn't always
practical, for example, npm scripts cannot accept commandline parameters (though you can use
environment variables largely for the same purpose).