Hi, I've been using the workflow described at http://www.debuggable.com/posts/how-to-fork-patch-npm-modules:4e2eb9f3-e584-44be-b1a9-3db7cbdd56cb to handle custom modifications to modules published on npm.
The basic workflow is to create a fork and set up the package.json to point to the tar.gz of the updated code. This method has a drawback in that npm always has to fetch the tar.gz file as it doesn't know if it's been updated. I'm wondering if there are any other workflows for handling this. I'm tempted to re-publish the fork on npm under a different name, but I hate to pollute the package listing. Any ideas? Thanks, Chris -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
