Updated version that works with npm/browserify, and fixes unnecessary purging

[ropez]

The purpose of this PR is to see if there is anyone paying attention to this project.

We're been using (a copy of) this in our software for several years. Now we need to fix a couple of issues, and would like to use it as a proper npm package, using browserify.

I found rstuven's fork that has already done some of the work of porting it to npm. I've re-purposed this for browserify, by removing the "dynamic" require calls, and added new tests for the localStorage backend.

I've also fixed an issue with the purge function being called many times when adding many items to a full cache.

Now, I would like to start pushing this to npm, and maybe set up a travis-ci job for running the tests. The question is, would it be Ok if I just went ahead and published this as "cachai" on npm, or do you want to hold on to the maintainer status, as the original author of the project?

[monsur]

Please, by all means, feel free to take this project and run with it. What do you need from me to move forward? Thanks for reaching out!

[ropez]

Thanks.

You don't need to do anything, apparently @rstuven took the job https://github.com/rstuven/node-cachai/pull/2

[tomten]

I'm using this in one of my projects. Will this particular github repository receives updates from now on? And should I change the attribution in my project?

[goldensunliu]

@rstuven wanna ask @monsur to give up the jscache npm repo name so we can get https://github.com/rstuven/node-cachai co-branded as jscache?