{"_id":"bashpack","_rev":"36-f203da59642e7cd10983459bbb89578a","name":"bashpack","description":"packs a nodejs project into a single bash file","dist-tags":{"latest":"0.0.16"},"versions":{"0.0.1":{"name":"bashpack","version":"0.0.1","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"*","winston":"*","temporary":"*","shelljs":"*","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n## Installation:\n\n $ npm install bashpack\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var baseDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(baseDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n## Limitations\n\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n## Todos/Ideas\n\n- provide option to specify tempdir\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.1","dist":{"shasum":"c6dce4d9aa1be9463957da23e295d9e359809c9d","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.1.tgz","integrity":"sha512-jhbzhxouPAtAEn9IJZf9AykAJo7zgi8cfg9DaiV1gYJZB1JxrMI5prMtkOhWPQ2g/m/iRggK7ya0Nv9HKmsDxw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDmZdEf7+iJyejn+fJYTaDnjN1OJME+UhXdkrr/dNbdRAiBOc03nwB6/0VNIrJz2H12rLO4iFt3cgJonpQPFHWF/4w=="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.2":{"name":"bashpack","version":"0.0.2","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"*","winston":"*","temporary":"*","shelljs":"*","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n## Installation:\n\n $ npm install bashpack\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var baseDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(baseDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n## Limitations\n\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n## Todos/Ideas\n\n- provide option to specify tempdir\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.2","dist":{"shasum":"dade2769acbe3815dface977305e3a33feae33fc","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.2.tgz","integrity":"sha512-yL5zNapbLXwstEdf7A3coXPtlz1bCrEP1X7HpK5miDSCzBfmIOxJFFZC+Kg989Xpnyq9MT/BrjCJPsktUvoVmw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCXCOTN8c3VTqu1m51Mp2Ok939iXYxusa7KnHbO0H2zBwIhAKIF5TesKFqi7eF4fxxQVGPuYIBKl96yQX5Cmcj1WbAK"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.3":{"name":"bashpack","version":"0.0.3","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"*","winston":"*","temporary":"*","shelljs":"*","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -t, --temp-dir Directory to use for tempory [auto-detect from TMP_DIR]\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n## Limitations\n\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n## Todos/Ideas\n\n- provide option to specify tempdir\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.3","dist":{"shasum":"841f23dc2a1463a5b84d59616a9d002ddff84035","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.3.tgz","integrity":"sha512-vJ5UuQaqZWmEjNd0JmxmM6HXmxKwCZ/AMIeU1bA2pT7fY/WdnBUkI0TuPM5qfafQ+0ib6zLGX6VhAftdFwVCag==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDPT6a5FWQ4PDrS8vArLIUdJs71WFnhtbFsiujg72J3/QIhAJ8i56Ap3m7K1JSTIMQBoW+ZYmj2Gz6BAjlaXcvlTXG+"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.4":{"name":"bashpack","version":"0.0.4","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.4","dist":{"shasum":"3ccc83e67cfb44e2fd79d7f9d6797ce122b89282","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.4.tgz","integrity":"sha512-RmQGiDor2ySwe5r6nllm/NDTr1hC91l0Y9ioUs243CVXvYEMhikzLadYnPBdiZj1SSitBhVNT558XLsQIx5yiQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDeuYKThmx+lp/hB/iCv6U+v/OOPOx8f4h6JSq4arA8GAIhAL4WK0N8k/f6XgELVaXQjRU6KOrqzZlcXm9SiaYbx2Wa"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.5":{"name":"bashpack","version":"0.0.5","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.5","dist":{"shasum":"7ff191cbb69594a3d1509987af6a5d8c02db4de7","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.5.tgz","integrity":"sha512-AMcCu+P4YaU25yEIpX0anzSto32k0Ta0FRmAJCDPzYzj5DPmv1oyQDsjte8Yy2gqBFcOJFSOMk4QC22D/RbruQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDMW35MHnMOBvTDaG/ryFFCrDNIBnpjRIlUVv4SLIqpkAIgEUwylWW9kBxXS+WAj7B/5NHUS3xZMIZXCYbmGxzd/40="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.6":{"name":"bashpack","version":"0.0.6","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.6","dist":{"shasum":"97533d1f33a0ec094067418e18103bec51430475","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.6.tgz","integrity":"sha512-WVpNHjue7LSwlobQYCvwitS+OTb94Zhn64s9pLwaV5SD/XkbpMuhcln7eiiYw9OYd4tfdQ0kohMCuu7WqIp5oA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIF0fuhNn8y6Fxdzr0P53WB0aR7skn1td5jGdcxvqc44pAiEA2gqiD6eao8/nkOObsRm/B7W5BHmR+jlyuOB/+u3b+eM="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.7":{"name":"bashpack","version":"0.0.7","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"make MOCHA=mocha JSHINT=jshint test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"*"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.7","dist":{"shasum":"65ac5fb0bdb8c6c04e8ab9f246dcf3df3738245b","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.7.tgz","integrity":"sha512-r2S+fEPfKUZeBd6JQu6hW1ZcaEYzWEXZLP2sq+GyleWQcorBH5Bt6XchaPGn/hra1v3CRggjYziwPRrncW7Y3g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGTQzqViXoOV1gHeYBXOiwP6zjdMN9impBKa/qbmLl0oAiADyN4ZOyI4tm+7g3zuI4gPDgVCY1D3U2Pz8DP7sQE53A=="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.8":{"name":"bashpack","version":"0.0.8","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.8","dist":{"shasum":"95ccb893e8df6cceee2bf803c625e237219f14f0","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.8.tgz","integrity":"sha512-0ZcybR7aHDB6e5ry2mBAzXbo55fNuaSyOqaJMcpg2SSNCcxULPgDYq6sHyZjasDY26Bh8+ZT+vqOYlZrgTlnTg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHeG7QUGK8VQ0zPpHcev25KyeHTIiQU52QSTxyMamCs8AiEApQRvA+QBti7Ksw6eZbEdfSsGdUWgQ5ogMffAuGL+etw="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.9":{"name":"bashpack","version":"0.0.9","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5"},"license":"MIT","engine":{"node":">=0.6"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.9","dist":{"shasum":"a5278b6535cb1b072af1118e1ef4366159502f54","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.9.tgz","integrity":"sha512-E1aBTrgL2P8GT5ug6bUY6ExGQdUrhlz43OvnjuvoBetxE5g10iSPXE0qZrnW3ciWKFJBnAmvD9U7nAZ4bCOlSg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCoR2bwhbEo/POCPmPGmPqJILyh1PHCH+uKnOOi7fUwMwIhAP16LhmOlAXgvy8NBR0Sj/uhu1UNhbT5h/NZ0AbbSae8"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.10":{"name":"bashpack","version":"0.0.10","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.10","dist":{"shasum":"ed320bd80c092b454a9edecc53aaf303ceafb8a2","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.10.tgz","integrity":"sha512-l/63qEP598GPk0EQmaj+cVMaKqJtXjsHw57pap9C0DsCU9ty4MzOXgKJJm8iDU/KS7xhGqzKHfr/4ac3KZEDSg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD3fxQn0QJo25RO6hWY9ZxRTbwodslRMD/fCVp1kxOfOwIhAJR1M1py7Smh7iU/08+y2WPsXhGMVZSmacSTjARQxQFq"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.11":{"name":"bashpack","version":"0.0.11","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","temporary":"0.0.5","shelljs":"0.1.4","shell-quote":"~1.3.3"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(projectDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.11","dist":{"shasum":"51a2075574407e12118852a20287a9760549ccbf","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.11.tgz","integrity":"sha512-8HkN/JUFHjMHB7pqRkntQkgUoZl55CswtvbMQ8HUIwaewLXz++TL60NbHE1CPOL0Ihpqy7lseacTC3PRC6rfaw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDIE6bOHqzZxocc9HP2m+B5AIH0MXbECX1GWf51yD7L0wIgBpdS2MKm6GmTeEvj5FHKFzWIIG6u8h1czvV5Hn+jaHg="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.12":{"name":"bashpack","version":"0.0.12","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","node-fetcher":"~0.0.6","async":"~0.2.9","temp":"~0.5.1","ncp":"~0.4.2","hashmerge":"~1.0.2"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5","grunt-docco2":"~0.1.1","shelljs":"~0.1.4","longjohn":"~0.2.1"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n var options = {\n outputFile: 'mybashpack.run'\n };\n\n bashPack.build(projectDir, startScript, options, function(err, filename) {\n if (err) {\n console.log('error happened:'+ err.message);\n } else {\n console.log('created bashpack '+ filename);\n }\n });\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n\n- include DYLIBS in bashpack\n\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.12","dist":{"shasum":"c43724774d7461291353bb442636421fe53651ba","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.12.tgz","integrity":"sha512-N9NYeRQaBo43D1LXPa9bW87sNTQILa78Syz+P1EmUBM26lquXBSahAaHdyDXHotDQaHVYbPdXZWmdu4vi50VgQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCXW4wz7T5syIAZSXRQqzscA2x9YM3wLr4nA8SRPV6KngIhANEP8vRRq/sKQZsljwKATu2TLGisWkhWtVtrUdowgKti"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.13":{"name":"bashpack","version":"0.0.13","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","node-fetcher":">=0.0.7","async":"~0.2.9","temp":"~0.5.1","ncp":"~0.4.2","hashmerge":"~1.0.2","minimatch":"~0.2.12"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5","shelljs":"~0.1.4"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the (shell)patterns to exclude\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary [auto-detect from path]\n\nBy default it includes a node-binary in your bashpack.run file, if you want to avoid that use the --skip-node-include option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n var options = {\n outputFile: 'mybashpack.run'\n };\n\n bashPack.build(projectDir, startScript, options, function(err, filename) {\n if (err) {\n console.log('error happened:'+ err.message);\n } else {\n console.log('created bashpack '+ filename);\n }\n });\n\n## Build Options/Defaults\n\n```js\n // The overall defaults if not specified\n var _defaults = {\n logMute: true, // no output by default\n logLevel: 'info',\n logTimestamp: false,\n logPrettyPrint: false,\n includeNode: true,\n exclude: [ '.git/*','doc/*','test/*' ],\n name: 'the anonymous module',\n outputFile: ['bashpack' , process.platform , process.arch].join('-') + '.run',\n configName: 'bashpack.json',\n libs: undefined, // Array of native libs to add and load\n force: false, // overwrite Bashpack outputFile\n excludeFile: undefined , // no exclude file speficied\n node: {\n platform: process.platform, // darwin, linux, sunos\n arch: process.arch, // x86 | x64\n version: 'system' // system, latest, 0.10.x..\n },\n nodeBinary: undefined // Override node file used\n```\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- to pack a node binary in the bashpack file, it needs to be available in your path , or specified by hand with --node-binary option\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n- build a bashpack from a GIT repo or NPM Tarball\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n\n- include DYLIBS in bashpack\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.13","dist":{"shasum":"fde4e8351668ac84c92a931c6d720610be04e425","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.13.tgz","integrity":"sha512-X9XyNX60WqJ1uivXOShrcKtYdneNpi4ewPvMl8WdU2ScqTOMglT5bf8cyMFHsCgk4MkfgkK1jsDhbvyN4L0HaQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCrrEoKjp6L7pNuKK5MhcGGaEhFC414Dj1zK48s1RPZ9wIhAKQ+dSH3nHPzq9NpSP83d+SjN0gj6LdCpVNru9c6vPK4"}]},"_from":".","_npmVersion":"1.2.30","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.14":{"name":"bashpack","version":"0.0.14","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","node-fetcher":">=0.0.9","async":"~0.2.9","temp":"~0.5.1","ncp":"~0.4.2","hashmerge":"~1.0.2","fstream-ignore":"0.0.7"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5","shelljs":"~0.1.4"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install -g bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the patterns to exclude [auto-detect from $projectdir/{.gitignore, .npmignore, .bashpackignore\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary\n --node-version Node version to include. Use system|latest|va.b.c [system]\n --node-platform Node platform to download. darwin|linux|sunos [darwin]\n --node-arch Node arch to download. x86|x64 [x64]\n -c, --config-file JSON File containing bashpack settings [auto-detect from $projectdir/bashpack.json]\n\nBy default it includes your 'system' node-binary in your bashpack.run file.\nIf you specify a `node-version` it will download the node-binary from `http://nodejs.org/download`\n\nIf you want to avoid the inclusion of a node-binary use the `--skip-node-include` option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n var options = {\n outputFile: 'mybashpack.run'\n };\n\n bashPack.build(projectDir, startScript, options, function(err, filename) {\n if (err) {\n console.log('error happened:'+ err.message);\n } else {\n console.log('created bashpack '+ filename);\n }\n });\n\n## Build Options/Defaults\n\n```js\n var _defaults = {\n logMute: true, // no output by default\n logLevel: 'info',\n logTimestamp: false,\n logPrettyPrint: false,\n includeNode: true,\n exclude: [ '.git/*','doc/*','test/*' ],\n name: 'the anonymous module',\n outputFile: ['bashpack' , process.platform , process.arch].join('-') + '.run',\n configName: 'bashpack.json',\n libs: undefined, // Array of native libs to add and load\n force: false, // overwrite Bashpack outputFile\n excludeFile: undefined , // no exclude file speficied\n nodePlatform: process.platform, // darwin, linux, sunos\n nodeArch: process.arch, // x86 | x64\n nodeVersion: 'system', // system, latest, 0.10.x..\n nodeBinary: undefined // Override node file used\n };\n```\n\n## ignore files\n\nBashpack reads packIgnores from: `.gitignore`, `.npmignore`, `.bashpackignore`\nThe file **override** the ignores, they do NOT merge\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n- build a bashpack from a GIT repo or NPM Tarball\n\n- report warning if packing on a different architecture\n- report error if bashpack is run on the wrong architecture\n- ability to pass nodejs options\n\n- include DYLIBS in bashpack\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.14","dist":{"shasum":"ed381cf5a5902fe23cfcdad2fcfa6520de5cb39d","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.14.tgz","integrity":"sha512-+8pDjJ9ZQm5bp/MWI2SCZ4gJlhdMxH7+pT81hgT+Glfw0Drj2zlmZfVvgp48149N/ZM5QodFUIJ0KR53YZgj0Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIH1fG0ZnqUBcjlFJN46cD01qaeryKdpHxTc7wkBlvfprAiBGf5VWWJSHJ7jbGDabJd8l9LV3vRF25QM4oMeXAZH80A=="}]},"_from":".","_npmVersion":"1.2.30","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.15":{"name":"bashpack","version":"0.0.15","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","node-fetcher":">=0.0.9","async":"~0.2.9","temp":"~0.5.1","ncp":"~0.4.2","hashmerge":"~1.0.2","fstream-ignore":"0.0.7","npm":"~1.3.9"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5","shelljs":"~0.1.4"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install -g bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the patterns to exclude [auto-detect from $projectdir/{.gitignore, .npmignore, .bashpackignore}]\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary\n --node-version Node version to include. Use system|latest|va.b.c [system]\n --node-platform Node platform to download. darwin|linux|sunos [darwin]\n --node-arch Node arch to download. x86|x64 [x64]\n -c, --config-file JSON File containing bashpack settings [auto-detect from $projectdir/bashpack.json]\n\nBy default it includes your 'system' node-binary in your bashpack.run file.\nIf you specify a `node-version` it will download the node-binary from `http://nodejs.org/download`\n\nIf you want to avoid the inclusion of a node-binary use the `--skip-node-include` option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n var options = {\n outputFile: 'mybashpack.run'\n };\n\n bashPack.build(projectDir, startScript, options, function(err, filename) {\n if (err) {\n console.log('error happened:'+ err.message);\n } else {\n console.log('created bashpack '+ filename);\n }\n });\n\n## Build Options/Defaults\n\n```js\n var _defaults = {\n logMute: true, // no output by default\n logLevel: 'info',\n logTimestamp: false,\n logPrettyPrint: false,\n includeNode: true,\n exclude: [ '.git/*','doc/*','test/*' ],\n name: 'the anonymous module',\n outputFile: ['bashpack' , process.platform , process.arch].join('-') + '.run',\n configName: 'bashpack.json',\n libs: undefined, // Array of native libs to add and load\n force: false, // overwrite Bashpack outputFile\n excludeFile: undefined , // no exclude file speficied\n nodePlatform: process.platform, // darwin, linux, sunos\n nodeArch: process.arch, // x86 | x64\n nodeVersion: 'system', // system, latest, 0.10.x..\n nodeBinary: undefined // Override node file used\n };\n```\n\n## ignore files\n\nBashpack reads packIgnores from: `.gitignore`, `.npmignore`, `.bashpackignore`\nThe file **override** the ignores, they do NOT merge\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n- build a bashpack from a GIT repo or NPM Tarball\n\n- report warning if packing on a different architecture\n- report error if bashpack is run on the wrong architecture\n- ability to pass nodejs options\n\n- include DYLIBS in bashpack\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.15","dist":{"shasum":"bd433a5da2226e64bf9b93bdc1c0e22e7dd19cd2","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.15.tgz","integrity":"sha512-aZVyHuLQmTUGYzfLUa1CEJmofAOMMPgmnOBd7NjqZkXblTWzPISxySd1oZ7AA38FjfhqRw8OgDrY721gDiNrHg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEMCHyhl+JqAr0sR/FKPOI2GnUQdd+nNMI3wHVaArC4CAr0CIEoHzH+bTWTk4k9COLObRl/f+ZOLNCrahzHfmqdim2lZ"}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]},"0.0.16":{"name":"bashpack","version":"0.0.16","private":false,"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"description":"packs a nodejs project into a single bash file","scripts":{"test":"grunt test"},"main":"./lib/bashpack.js","bin":{"bashpack":"./bin/bashpack"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"keywords":["binary","packaging","distribution","package"],"dependencies":{"commander":"1.3.0","winston":"0.7.2","node-fetcher":">=0.0.9","async":"~0.2.9","temp":"~0.5.1","ncp":"~0.4.2","hashmerge":"~1.0.2","fstream-ignore":"0.0.7","npm":"~1.3.9"},"devDependencies":{"mocha":"*","jshint":"*","jscoverage":"*","nodewatch":"*","assert":"*","expect.js":"*","should":"0.5.1","grunt":"~0.4.1","grunt-contrib-jshint":"~0.6.0","grunt-contrib-watch":"~0.4.4","grunt-release":"~0.3.5","grunt-mocha-test":"~0.5.0","blanket":"~1.1.5","shelljs":"~0.1.4"},"license":"MIT","engine":{"node":">=0.8"},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n[![Build Status](https://travis-ci.org/jedi4ever/bashpack.png?branch=master)](https://travis-ci.org/jedi4ever/bashpack)\n\n## Installation:\n\n $ npm install -g bashpack\n\n## CLI options\n\n### Create init file\n $ ./bin/bashpack init --help\n\n Usage: init [options] \n\n Options:\n\n -h, --help output usage information\n -f, --force Force overwrite\n\n\n### Build a bashpack\n\n $ ./bin/bashpack build --help\n\n Usage: build [options] ,\n\n Options:\n\n -h, --help output usage information\n --log-level Set loglevel [info]\n --log-timestamp Enable timestamps in log-output\n --no-log-colorize Disable colors in log-output\n --no-log-pretty-print Disable pretty-print log-output\n -m, --log-mute Disable log-output\n -d, --debug Enable debug level\n -o, --output-file Outputfile [bashpack.run]\n -f, --force Force overwrite\n -e, --exclude Pattern to exclude ['.git/*']\n -l, --libs Shared libraries to include []\n -X, --exclude-file File that contains the patterns to exclude [auto-detect from $projectdir/{.gitignore, .npmignore, .bashpackignore}]\n -s, --skip-node-include Don't include a node binary in the bashpack\n -b, --node-binary File path to node binary\n --node-version Node version to include. Use system|latest|va.b.c [system]\n --node-platform Node platform to download. darwin|linux|sunos [darwin]\n --node-arch Node arch to download. x86|x64 [x64]\n -c, --config-file JSON File containing bashpack settings [auto-detect from $projectdir/bashpack.json]\n\nBy default it includes your 'system' node-binary in your bashpack.run file.\nIf you specify a `node-version` it will download the node-binary from `http://nodejs.org/download`\n\nIf you want to avoid the inclusion of a node-binary use the `--skip-node-include` option\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init .\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var projectDir = '.';\n var startScript = 'bin/statsd';\n var options = {\n outputFile: 'mybashpack.run'\n };\n\n bashPack.build(projectDir, startScript, options, function(err, filename) {\n if (err) {\n console.log('error happened:'+ err.message);\n } else {\n console.log('created bashpack '+ filename);\n }\n });\n\n## Build Options/Defaults\n\n```js\n var _defaults = {\n logMute: true, // no output by default\n logLevel: 'info',\n logTimestamp: false,\n logPrettyPrint: false,\n includeNode: true,\n exclude: [ '.git/*','doc/*','test/*' ],\n name: 'the anonymous module',\n outputFile: ['bashpack' , process.platform , process.arch].join('-') + '.run',\n configName: 'bashpack.json',\n libs: undefined, // Array of native libs to add and load\n force: false, // overwrite Bashpack outputFile\n excludeFile: undefined , // no exclude file speficied\n nodePlatform: process.platform, // darwin, linux, sunos\n nodeArch: process.arch, // x86 | x64\n nodeVersion: 'system', // system, latest, 0.10.x..\n nodeBinary: undefined // Override node file used\n };\n```\n\n## ignore files\n\nBashpack reads packIgnores from: `.gitignore`, `.npmignore`, `.bashpackignore`\nThe file **override** the ignores, they do NOT merge\n\n## bashpack run files options\nA bashpack file, is a shell script, with a payload.\nAs the payload is bzip2-ed, they are small compared to the node-binary size.\n\nRunning a bashpack is simple ``./bashpack.run``.\nAll arguments specified will be directly passed to the node startScript\n\nIn addition to that, the bashpack also responds to some internal commands (prefixed with --bashpack)\n\n # Show bashpack help\n ./bashpack.run --bashpack-help\n\n # List all included files\n ./bashpack.run --bashpack-list\n\n # Check integrity of bashpack\n ./bashpack.run --check\n\n # Info on creation\n ./bashpack.run --bashpack-info\n\n # Don't run the script\n ./bashpack.run --bashpack-noexec\n\n # Extract in a directory\n ./bashpack.run --bashpack-target /opt/somedir\n\n # Treat the bashpack as a tar file\n ./bashpack.run --bashpack-tar -tvf\n\n## Tips\n\n- if you like to create a '.deb', '.rpm' etc.. package - consider using [fpm](https://github.com/jordansissel/fpm)\n- to speed up execution of your bashpack.run file, you need trim down the files that are included. You can do this by adding paths/patterns to the exclude\n- also if you do this from your working directory and you did not specify ``--production`` to your ``npm install``, your node_modules will be larger than necessary. Consider running this on a clean projectdir with ``--production``\n\n\n## Limitations\n\n### Dependencies\n\n- the bashpack.run file uses uuencode, bzip2 , tar . These need to be in your path when running the bashpack.run file\n\n### Native modules\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n### Platforms\n\n- any unix-alike , or macosx should work\n- windows is currently not supported\n\n## Todos/Ideas\n- build a bashpack from a GIT repo or NPM Tarball\n\n- ability to pass nodejs options\n\n- include DYLIBS in bashpack\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/jedi4ever/bashpack/issues"},"_id":"bashpack@0.0.16","dist":{"shasum":"31efdbac895a26b6196fea2569101d717bff4e1a","tarball":"https://registry.npmjs.org/bashpack/-/bashpack-0.0.16.tgz","integrity":"sha512-rAF92+uFSFnhFc0DOKTBj9MIuOL+xVkhMxs9LTCMgCYfU10vVwxiMIqBXKjm0yl55Jv+gtEsOpc2x4xh8cSiBA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDZlhyNt3ocSmwh90i+LTEUk6pCsi8hJTbRPny1UrllUgIgZ6iHG51cj/5iUMvncfhHh0aAEnf/L+9SB0Q7j6/dBxQ="}]},"_from":".","_npmVersion":"1.2.21","_npmUser":{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"},"maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}]}},"readme":"# Bashpacker\n\n**bashpacker** packs a nodejs project into a single bash file that can be executed without the need to install nodejs or anything else\nIt will include the nodejs binary to be executed\n\n## Installation:\n\n $ npm install bashpack\n\n## Sample CLI usage\n\nThis is how we would create a bashpack from the statsd project\n\n # Get a fresh repo\n $ git clone https://github.com/etsy/statsd.git\n $ cd statsd\n\n # Install all dependencies (--production will limit the ones needed for production)\n $ npm install --production\n\n # Dedupe the node_modules used by dependencies\n $ npm dedupe\n\n # Create a bashpack config\n $ bashpack init\n\n # Create a bash script 'statsd.run' from 'current dir' and launch 'bin/statsd' on run\n $ bashpack . bin/statsd -o statsd.run\n\n # Now run the bashpack\n $ ./statsd.run exampleConfig.js\n\n## Sample code usage\n\n var BashPack = require('bashpack');\n var bashPack = new BashPack();\n var baseDir = '.';\n var startScript = 'bin/statsd';\n\n bashPack.build(baseDir, startScript, function(err) {\n if (err) {\n console.log('error happened:'+ err.message);\n }\n });\n\n## Inspired by\n\nMakeself - \n\nTweaks made:\n- fix for md5 to work\n- prefix the archive options (info, list, check) with --bashpack-\n- pass all arguments directly to script that is started\n\n## Limitations\n\nWhen the bashpack is created, it will include the '.node' (native modules) for the architecture it is created on.\nThere is currently no good way of providing multi-architecture node/native modules.\n\nIf your module does not have native module dependencies, you can specify a node file from another architecture to be included\n\nAlso it can not guess the additional shared libs your application was compiled against, so you have to manually specify them.\n\n## Todos/Ideas\n\n- provide option to specify tempdir\n- report error if bashpack is run on the wrong architecture\n- integrate .bashpack-ignore in package.json\n- ability to pass nodejs options\n- grunt plugin\n\n- include DYLIBS in bashpack\n\n- guess the startScript from the main in the package.json\n- guess the archive name from the module description\n- bashpackignore syntax to be similar from gitignore & npmignore\n\n- auto-build backfrom from npm (download, install --production, dedupe, bashpack)\n- copy baseDir first and rebuild it from a clean node_modules dir\n\n- auto-download nodejs binary/arch/version/etc to be included\n\n- multi architecture bashpacks : by including multiple nodejs binaries in the bashpack and selecting the correct one\n\n","maintainers":[{"name":"jedi4ever","email":"Patrick.Debois@jedi.be"}],"time":{"modified":"2022-06-13T04:22:12.758Z","created":"2013-07-16T10:39:51.895Z","0.0.1":"2013-07-16T10:39:54.702Z","0.0.2":"2013-07-16T11:35:49.814Z","0.0.3":"2013-07-16T14:15:25.222Z","0.0.4":"2013-07-16T18:38:52.139Z","0.0.5":"2013-07-17T07:15:39.842Z","0.0.6":"2013-07-17T08:34:26.572Z","0.0.7":"2013-07-17T10:30:04.479Z","0.0.8":"2013-07-17T12:29:58.581Z","0.0.9":"2013-07-17T13:09:16.688Z","0.0.10":"2013-07-17T13:46:34.938Z","0.0.11":"2013-07-17T13:54:05.359Z","0.0.12":"2013-08-21T14:07:07.273Z","0.0.13":"2013-08-22T07:35:14.973Z","0.0.14":"2013-08-22T14:15:14.786Z","0.0.15":"2013-08-26T07:21:20.620Z","0.0.16":"2013-08-26T07:46:10.778Z"},"author":{"name":"Patrick Debois","email":"patrick.debois@jedi.be"},"repository":{"type":"git","url":"https://github.com/jedi4ever/bashpack.git"},"users":{"djblue":true}}