Allow node modules to be installed from svn repos
Installing this module will make changes to your project's package.json file.
Installing this module via
npm install will add an install hook to your
project's package.json. Once this hook is added anytime your run
for your project svn-npm-crutch looks through your package.json file for an
svnDependencies block where you can list your subversion stored node modules.
npm install svn-npm-crutch
After installing svn-npm-crutch you may use list dependencies from subversion
repositories in your
package.json under a "svnDependencies" key. e.g.
Run a test with
grunt test then take a look at
grunt test instead of
npm test? Running
npm test initializes some
environment variables. We could go through and clean that up during the testing
process... but it's easier to just test with grunt directly.
- More tests... yep
- Be less invasive? Right now this rewrites your entire package.json after adding it's install hook using JSON.stringify... This isn't horrible but clobbers things like white space.
- Don't perform an
svn updateif a specific repo tag/revision number is specified... maybe clean out the old module and do a fresh checkout?
- Better detection of when the module is being installed as a dependency vs
being itself installed (i.e. running
npm installon the project itself)
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.
- Tests added
- Refactored install routine
- More descriptive status reporting
svn updateafter attempting to install (get module changes)
- Make sure updates to svn modules are fetched
- Share stdio with childprocesses, allow for svn prompts to be addresses
- More efficient testing... us npm programmatically to install this mod in a test dir
- Added a
svn cleanupphase after the
npm installrather than
cp.spawn... seems to be an issue on Windows
Copyright (c) 2012 iVantage Health Analytics Licensed under the MIT license.