assets-bundler
bundles your assets. creates symbolic links
for development and copies
for production.
features
-
you can use the whole glob syntax in the
src
anddest
pattern, as well as the glob-var variables starting with a colon:
-
in development,
symbolic links
are created, using glob-ln -
in production,
copies
are created, using glob-cp
install
npm install assets-bundler -g
use
you can either use
assets-bundler
programmatically or via command-line:
node.js
var bundle = ; var opts = src: __dirname + '/node_modules/:module/public' dest: __dirname + '/public/:module'; // async version; // or with the sync versionbundle;// all done
command line
// use NODE_ENV
options
assets-bundler -h Usage: assets-bundler [options] ["<src>" "<dest>"] Please use quotes when providing '<src>' and '<dest>' Options: -h, --help output usage information -V, --version output the version number -s, --src [value] source path -e, --env [value] environment: "prod[uction]" or "dev[elopment]", default: "production" -f, --force remove destination before the operation -r, --recursive recursive copy
src
- The source path. It can be relative or absolute.
- When you don't provide an absolute path, an absolute path is created from the current working directory of the process using
process.cwd()
.
dest
- The destination path. It can be relative or absolute.
- When you don't provide an absolute path, an absolute path is created from the current working directory of the process using
process.cwd()
.
env
- You can either set the
env
option (wins), or the environment variableNODE_ENV
(lower precedence).
force
- With force, assets-bundler does the job without moaning when switching the environment [production, development].
- The destiation always gets deleted before symlinking or copying, wether it is currently a link or file or folder.
recursive
- Recursive Copy, only relevant for
procuctuion
mode. Without it, only the first level of directories gets copied over.
test
npm test
author
Andi Neck | @andineck
license
MIT