Find a driver
npm install -g taxicab
Finds the application entry points (i.e., driver scripts) that depend on a given module.
In a multi-bundle architecture (where each bundle contains an entry-point/driver-script), a module gets reused across several bundles. If you're changing a module, it's helpful to know which apps will be affected.
var findDriver = require('taxicab');
findDriver({
filename: 'path/to/a/js/file',
directory: 'path/to/all/js',
config: 'path/to/requirejs/config.js', // optional
webpackConfig: 'path/to/webpack/config.js', // optional
success: function(err, drivers) {
console.log(drivers);
}
});
- You may pass additional options supported by
get-driver-scripts
to handle pulling driver scripts from a RequireJS build config or resolving aliased paths via a requirejs config.
taxicab --directory=path/to/my/js path/to/a/file
- See
taxicab --help
for more information and supported options.
Prints:
/path/to/a.js
/path/to/b.js