Skip to content

dependents/node-taxicab

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

TaxiCab npm npm

Find a driver

npm install -g taxicab

Finds the application entry points (i.e., driver scripts) that depend on a given module.

Motivation

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.

Usage

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.

Shell usage:

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

About

Find a driver related to a given module

Resources

Stars

Watchers

Forks

Packages

No packages published