Package Exports
- trucker
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (trucker) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
#trucker
Trucker is a command-line tool for developers using Node that helps you to move source files without breaking inter-file require dependencies.
It hauls your files around without breaking them.
You can think of it as a require-aware wrapper for a subset of mv. (See limitations section below).
#Installation
npm install -g trucker
(note: trucker requires node.js and npm)
#Usage
trucker [flags] [source] [destination]
##Options
-h, --help prints the help
-n, --dry-run tells trucker not to move any files, but to instead print out a list of all of the changes that would have been made if this option was not set.
-s, --scope can be used to expand or contract the set of files that trucker searches for dependencies. This defaults to the present working directory. If you have a very large project you may wish to constrain the scope for performance reasons (analysis takes time), or in some cases you may wish to expand the scope beuyon the current directory. Use --scope for this.
Supported file types
Trucker supports javascript and coffeescript source files. It can handle projects that have both of these file types intermixed.
Limitations
no globbing (yet)
As compared with mv, you can't do this:
trucker lib/foo*.js lib/foorequire syntax
Trucker only recognizes basic require syntax.
Trucker doesn't recognize this, for example:
var x = '../foo/bar'
var y = require(x);