cache dependency manager installs to local machine
Want to see pretty graphs? Log in now!
npm install npm-cache
|8||downloads in the last day|
|64||downloads in the last week|
|141||downloads in the last month|
|Last Published By|
|Version||0.0.6 last updated 4 days ago|
|Keywords||npm, cache, install, bower, composer, local|
|Dependencies||MD5, async, glob, nomnom, shelljs|
npm-cache is a command line utility that caches dependencies installed via
It is useful for build processes that run
[npm|bower|composer] install every time as part of their
build process. Since dependencies don't change often, this often means slower build times.
helps alleviate this problem by caching previously installed dependencies on the build machine.
npm-cache can be a drop-in replacement for any build script that runs
How it Works
When you run
npm-cache install [npm|bower|composer], it first looks for
composer.json in the current working directory depending on which dependency manager is requested.
It then calculates the MD5 hash of the configuration file and looks for a filed named
.tar.gz in the cache directory ($HOME/.package_cache by default). If the file does not
npm-cache uses the system's installed dependency manager to install the dependencies. Once the
dependencies are installed,
npm-cache tars the newly downloaded dependencies and stores them in the
cache directory. The next time
npm-cache runs and sees the same config file, it will find the tarball
in the cache directory and untar the dependencies in the current working directory.
npm install -g npm-cache
npm-cache install # try to install npm, bower, and composer components npm-cache install bower # install only bower components npm-cache install bower npm # install bower and npm components npm-cache install bower --cacheDirectory /home/cache/ # install components using /home/cache as cache directory npm-cache install bower --forceRefresh # force installing dependencies from package manager without cache npm-cache clean # cleans out all cached files in cache directory