{"_id":"caddy","_rev":"30-5d17ba55434a1af61f18cbaed45e101a","name":"caddy","description":"caddy =====","dist-tags":{"latest":"0.0.13"},"versions":{"0.0.1":{"name":"caddy","version":"0.0.1","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n","readmeFilename":"README.md","_id":"caddy@0.0.1","description":"caddy =====","dist":{"shasum":"8e8c4df41c12ace09d10f0c4fa06ec6d05d952bc","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.1.tgz","integrity":"sha512-+QDpxmPPZgoTbFa1uj/u+s2Bh7kppBmB/rqZjz9G9rmFk24xnnJV13ZrYVRB0sL8fmLs+gFsnVvn7NeeZsqPFw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEWbroic4h+0EU9h1ggyd05VRpD5IZbRlf3cOChvUhhKAiEA4I1O2bxF2bBk/IiFZqYayeNEZbCC7c8Y0LXJVuwFojs="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.2":{"name":"caddy","version":"0.0.2","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.2","description":"caddy =====","dist":{"shasum":"a4694ce86b984637a21e9285f395e0c75a05e2e3","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.2.tgz","integrity":"sha512-421TvqPCbwLmBr3RJMWbrawsH1rxGYA3mmFj8M7q4vimRbzHnotjVmMoI3yZjVg/SzhX0xu3LXyGKM+iNu3irA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDIAfmMJwuQrokIwLTm8EDckELb1dvh/MEob9R3xhdIMgIgMu1W2k4oxGIzxHgJuAuS4JMO2Q7shFi7oWnH/3w3k6s="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.3":{"name":"caddy","version":"0.0.3","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.3","description":"caddy =====","dist":{"shasum":"428e1c9c0aebffdcaa3ee067277d042f7dba000a","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.3.tgz","integrity":"sha512-dsny/p0BFweFCGth1eyr3AVskDvWYXxSq9QVtt1uKls42CJvjqpOkiJX8KWRAM0KWW5utTsVUxzmPisprUs3Iw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIG/zWjxcFdkwcU8xl1C4w7DS/FwMbymWArgyfTmsYz+FAiBuZnWo8ySVNmK66CNiGDGq7P08uuJkEAjnlLg7zkLmdA=="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.4":{"name":"caddy","version":"0.0.4","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.4","description":"caddy =====","dist":{"shasum":"926a4380e60462f13241b9df5deecb407ec0fad4","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.4.tgz","integrity":"sha512-I/XBrRJ0cL4LOrC385nzu87ZhRUWeA/H3hCjUZ6dzRdYQclUoHO9BVlDKBVBlvqa4yXajySuQPCw0HRLVtUvLg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFTdbIQgqBbiWps/B8uBSz9hYlv4sMTYlcNZ+QVZBsXJAiEA1dJehweRIznjEd86gaZNpTV9SuZFIQieGs7yJTSLTpM="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.5":{"name":"caddy","version":"0.0.5","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.5","description":"caddy =====","dist":{"shasum":"8f39a8c006aacdfad7f131b412aaf63703c46bab","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.5.tgz","integrity":"sha512-zkCq17tKdyrDtVUVIPnko9s3Xhjhjtg7/UyFRI/0w1PltTMPVWcw0TFupKcxbro+vzotevfDr2qIL7Vtj3on0g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBLy0rinhR+7pvAqzmmW2p266/X4hzG6Sm01veBr/mVAAiBuDuweIa9D/D0b9Iq4vIb+y6gF+koVZhRfDld5hksP6Q=="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.6":{"name":"caddy","version":"0.0.6","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.6","description":"caddy =====","dist":{"shasum":"0fe3b347b055bab094d9252a978e36e42acbd7c1","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.6.tgz","integrity":"sha512-4U0oB6xl+aNPi4yI1YlsFOnp+2gfwfSihoJ7CMDjmXoffQSs9J2m/eVv9kb6x21lJgk5G4m9DL96u3KhiPnETw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDdJyBgQZbEPvCfxA0vZvP9kumvLmNjDMSK58/L7R/gSwIgRViQzpcPbdlsd2ZR85gNrmSZWToorF7OCrp6S+Eyo7M="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.7":{"name":"caddy","version":"0.0.7","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","_id":"caddy@0.0.7","description":"caddy =====","dist":{"shasum":"0a60ee713d3e5bae349190f05455d633fb6c3039","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.7.tgz","integrity":"sha512-JU5yMEpcThTPQGXGFzPiRzi9J2XI2orM8TPhh83pECagG9u9YnAp3ddf6qnNYSRXclyyxayAAEgHh/Ur3O3F0A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHlsiYytAomM5YpKyJ5/LzNpXiTKf+NBLoTu1SdHM4VBAiEAxc/YAQUC7I5yLU6a/gmxhtxpwPNBO9uOGKYdL8Wgjjk="}]},"_from":"./","_npmVersion":"1.2.14","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.8":{"name":"caddy","version":"0.0.8","private":false,"main":"./dist/caddy.js","dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","_id":"caddy@0.0.8","dist":{"shasum":"a3d3536b1f6c3953836449cb0cf832c09a682751","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.8.tgz","integrity":"sha512-uHr15R5N0srhFu9XZwpntAjgrO//NXEwoL2B/w8/wcv4/uykeWb7QHQmYaVfOayPTs5mX6zg8Z/RDnwzfowSvQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFLCMNAsFi9t11PqI5WMzpMm5oxYKHIzXxQM6F2IaA4CAiA6zfrMqhenKPvqUmgH4xvaIxobC1kJsJm97ZNYKNuklg=="}]},"_from":"./","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.9":{"name":"caddy","version":"0.0.9","private":false,"main":"./dist/caddy.js","repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"},"dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","bugs":{"url":"https://github.com/ainsleychong/caddy/issues"},"_id":"caddy@0.0.9","dist":{"shasum":"a09dc57a9fa513056818e223594a402d103bc7e8","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.9.tgz","integrity":"sha512-e8hu8qubE5n9OaadqZaL8OGAti8KRpXw7zCjDkKcBUSppoIi68fITGeeFcRz5oEkKpTkKgH681HM2wYh3SHS1Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDyTCOPbVmygeJshQjBLS9hdc4zxLLbcs9RW706Eozj9QIgaLJk+4ArEc8Wn4IVHatIkXrBLPFZO3LFB0sX6y+ZBnE="}]},"_from":"./","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.10":{"name":"caddy","version":"0.0.10","private":false,"main":"./dist/caddy.js","repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"},"dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","bugs":{"url":"https://github.com/ainsleychong/caddy/issues"},"_id":"caddy@0.0.10","dist":{"shasum":"2ed5996727341fa7b18ef5a4bff5e0d58524b830","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.10.tgz","integrity":"sha512-6PALsMLBRacUkdc6sN9rwHI29UlC0YefUVTAtmHen6LtlQyqO7xoOjFcTIJGSyJoEzU4jXv6kNvsCpuF13un8Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCAUEfYIRBYe3KgT4NzSFQ7CAIA5WjZMhcaw7IJ1BNFegIgfICFs/b1EtARPOGtSQ49VXETtU2OyCVBjtFk+Ygl3sE="}]},"_from":"./","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.11":{"name":"caddy","version":"0.0.11","private":false,"main":"./dist/caddy.js","repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"},"dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","bugs":{"url":"https://github.com/ainsleychong/caddy/issues"},"_id":"caddy@0.0.11","dist":{"shasum":"f856650ca1574a43fb282d05548060a08c6bd600","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.11.tgz","integrity":"sha512-0q0DMl2qIR7MpvaImIYF7Xn2N7Itu/8ujo2BHvDIj9erc1n4cdudhThnqLD73kmu3Ch+Tax8KFIYH9EIpl9Lvg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD4sUJWbrFkbF98eROsiehsGhyZiyc5jFnaA5ogQnSpMAIgLllXE7Hbb2Hik/RDM4SDuhkCMJquq2n/bimYlGazhfg="}]},"_from":"./","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.12":{"name":"caddy","version":"0.0.12","private":false,"main":"./dist/caddy.js","repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"},"dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","bugs":{"url":"https://github.com/ainsleychong/caddy/issues"},"_id":"caddy@0.0.12","dist":{"shasum":"26a6b6585f9ba507e24dbd89b63c69511abe4ec4","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.12.tgz","integrity":"sha512-wmJJsJ8Q5a/weZqgSr3pdcx9J1b0Q0V1Loy+7f3tt7uJL6g6EwYDx9I2UD4XQMi14xWUPJgY1LbkM0ActyG6YA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCTXMClRMr27SZHDA+dc+W5djD3zRnaqGzKvSPVfMvsCQIgWIJxY8lvM5rHSe+r227pH8uOnwIGmLx9zBclK5WW0ng="}]},"_from":"./","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}},"0.0.13":{"name":"caddy","version":"0.0.13","private":false,"main":"./dist/caddy.js","repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"},"dependencies":{},"devDependencies":{"mocha":"1.8.x","chai":"1.5.x","sinon":"latest","grunt":"0.4.x","grunt-contrib-coffee":"latest","grunt-contrib-watch":"0.3.x","grunt-contrib-jshint":"0.3.x","grunt-cafe-mocha":"0.1.x","coffee-script":"latest"},"readme":"caddy\n=====\n\nPer-request storage for arbitrary data.\n\nWhen the Caddy middleware is called (ex by Express), Caddy creates a data store that is accessable from any sub-modules used while handling the request. This can be a lot cleaner than attaching data to the res/req objects, which then have to be repeatedly passed around as parameters.\n\nEach request has it's own instance of the Caddy data store. There is no chance for the Caddy data of seperate requests to interact with each other, and no need for the user to keep track of which data belongs to which request.\n\nThe data store is maintained across events and other async functions such as process.nextTick(). By extension, the store will still be available after higher-level async functions like http.request().\n\nInstall\n===\n\n```sh\n$ npm install caddy\n```\n\nMiddleware\n===\n\n```js\nvar Caddy = require('caddy');\nvar express = require('express');\nvar app = express();\n\napp.use(Caddy.connect);\n```\n\nAPI\n===\n\nOnce the Caddy middleware has been called, you can get() and set() data from anywhere in your code.\n\n```js\nvar Caddy = require('caddy');\n\nCaddy.set('key', 'data');\nexpect(Caddy.get('key')).to.equal('key');\n```\n","readmeFilename":"README.md","description":"caddy =====","bugs":{"url":"https://github.com/ainsleychong/caddy/issues"},"_id":"caddy@0.0.13","dist":{"shasum":"d5bcf91ef4c11440842ef5253d901c704f0548c7","tarball":"https://registry.npmjs.org/caddy/-/caddy-0.0.13.tgz","integrity":"sha512-rc9RPEM0O32dzL52y9Udm+Y/2ll8cbaIVx0x4Q6yBrUtPvSyaDj46XPzhexLhfD0nh63+PsPVW1uMSsrTVZgag==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDaJvl5s2TUFslak2dpgEfTjDDWTjwYJ3Qq4FgeAzRPSQIhAMmiu5u8xfi7x2zCIb7NGpu2ecgOt9gEBKS0hnk5+SAs"}]},"_from":".","_npmVersion":"1.2.32","_npmUser":{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"},"maintainers":[{"name":"ainsleychong","email":"Ainsley.Chong@gmail.com"}],"directories":{}}},"readme":"caddy\n=====\n","maintainers":[{"email":"fisch0920@gmail.com","name":"fisch0920"}],"time":{"modified":"2022-06-13T05:24:07.106Z","created":"2013-07-01T22:51:10.783Z","0.0.1":"2013-07-01T22:51:11.980Z","0.0.2":"2013-07-09T00:09:39.056Z","0.0.3":"2013-07-09T00:16:05.283Z","0.0.4":"2013-07-09T21:37:18.645Z","0.0.5":"2013-07-09T22:42:37.598Z","0.0.6":"2013-07-09T22:55:55.669Z","0.0.7":"2013-07-14T21:54:37.310Z","0.0.8":"2013-08-02T21:02:00.102Z","0.0.9":"2013-08-02T21:04:49.995Z","0.0.10":"2013-08-05T19:14:26.737Z","0.0.11":"2013-08-05T19:27:15.928Z","0.0.12":"2013-08-05T23:36:33.452Z","0.0.13":"2013-11-28T19:50:11.189Z"},"repository":{"type":"git","url":"https://github.com/ainsleychong/caddy.git"}}