npmf (npm forever) is a proxy for npm that forever preserves the packages you rely on. No more randomly missing packages.
Any package you install through npmf will be cached indefinitely so that it will still be available the next time you deploy your software, even if the original author as “unpublished” said version.
Note… npmf does not actively replicate npm’s registry. npmf only saves packages installed through npmf. npmf does not save versions of packages that have not been installed through npmf.
curl http://npmjs.org/install.sh | sh
npm config set registry http://npmfjs.org:9000
npm install <PACKAGE>
npm --registry http://registry.npmjs.org install quadraticon@0.1.7
npm --registry http://npmfjs.org:9000 install quadraticon@0.1.7
Voting is now closed.







(8)
gerad
therazorbladeThis is a really nice idea and something that can be very useful, especially in this early phase of the community. However, messing with NPM config is not really acceptable to most people. Instead, I would like to see this submitted as an NPM feature where you can config it to default to the backup if the primary doesn’t have it. | |||
maraksquiresGood idea, could potentially have a lot of utility for many people, if open-sourced. Without the source code I can’t judge the design or completeness. I’m also not going to test, as I don’t want to pass my credentials through without seeing the source. | |||
__mario__You scratched your itch. | |||
I really don’t see the pont of this. | |||
rjkentLooks useful! Can’t wait until I have the need to install tons of code via npm :) | |||
I gave it a shot and unfortunately I got a nasty error and I have to assume that means it’s really broken. This would be so cool to have on-hand though in a production environment that I’d really like to see this made into a tested/reliable thing you could set up for yourself. | |||
It’s just job well done. I didn’t check is it doing what it is said to do, but I believe it does. | |||
Great for developers obviously. Had this problem myself! | |||
Really smart to solve a problem that you have had during Node Knockout. I also like that you figured out how to integrate with npm so easily. In terms of utility, I’d have to say that this is slightly dangerous more than useful, as many packages are unpublished due to security vulnerabilities. Maybe you could have it provide some sort of warning when you’re using a package with a vulnerability? All in all, nice work!