{"_id":"amd-utils","_rev":"41-54e223da3a10d2e3987d21f2b3fa52c9","name":"amd-utils","description":"Utility methods written in the AMD format","dist-tags":{"latest":"0.10.0"},"versions":{"0.0.1":{"name":"amd-utils","description":"Utility methods written in the AMD format","homepage":"http://millermedeiros.github.com/amd-utils/","keywords":["utilities","functional"],"version":"0.0.1","repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"devDependencies":{"mdoc":">= 0.3.1","handlebars":">= 1.0.1"},"_npmUser":{"name":"millermedeiros","email":"miller@millermedeiros.com"},"_id":"amd-utils@0.0.1","dependencies":{},"engines":{"node":"*"},"_engineSupported":true,"_npmVersion":"1.1.0-alpha-2","_nodeVersion":"v0.6.3","_defaultsLoaded":true,"dist":{"shasum":"f642dc9de23d2e732ea75c67853dc01bf8d49eec","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.0.1.tgz","integrity":"sha512-qHjJMfq8vbz85+7E3cR+xE/Xq17v5zH0IdRsXn3p0zPBrt/cS4S7b+XVelDbKSMQ/BYDCVtUsK9q189wsXKohQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIE4VcfMBCcE/RAPNsn3J4IlHPjcNx4Ju0Y2G7mDllfXsAiEAmV8BhideTWo9XTZPA2iZMCX38Ion4SJN5awNFxs+zL0="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}],"directories":{}},"0.1.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.1.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./pkg/index.js","dependencies":{"amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./pkg"},"devDependencies":{"wrench":"~1.3.9","mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"","_id":"amd-utils@0.1.0","dist":{"shasum":"ea2eb0ef925377be0cbb9f5d5c7e4828d76b258f","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.1.0.tgz","integrity":"sha512-xubKR9xMivThqgHg4tkakzsb9QzZ7z0ooOerjlyP1LLmN83m4CDhCG43QTTnZQV02Z3GL7zl/uatwU3OMucDQw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHPzjbOgMOv2nZI8IvmCcGbWkGRisauqauZ40WjJXE9jAiB9oN9rKlLlJpt9+6KNxAOSGaUZqWfMB8A/yIF2zxJ0FQ=="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.2.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.2.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./pkg/index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./pkg"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n   npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible module.\n\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.2.0","dist":{"shasum":"edc5608691ed913798bdfbc15c1e7b13e444217f","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.2.0.tgz","integrity":"sha512-ff4uhUfSGJ2C4cjALeZnFOoNaEvgQHoaSl8wTzH3lQ+5w6XEFlCX1aSWCzSkHw1uZ5z2PcTLxDGEe+x/yKXmNA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGPfhdCONO6hDoTRyeiVGARjbdvglHcc+aan6UUy5YJ2AiAze+ifhif5r4Xjl3D7z/KGhHa2Rp/KbgFiMI5nI932aw=="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.3.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.3.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./pkg/index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./pkg"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n   npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible module.\n\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.3.0","dist":{"shasum":"5caed3446779cf87a89fdee1554e69b12c8154df","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.3.0.tgz","integrity":"sha512-28qK7KTLus1DXJkNymyV3H4Xm0JmktEALzF6UgQsO4lwi9yhmjBYDXx4VamoAZPU+UTrqXw8B3tiFAr1mD1V+w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC/2/wQ7VPzGrLPyhcr785v1PPtgdOi8wuF8pDUGog1KwIhAPZO37hNTIfoemb4uCKPr8UkWVMdPeXLzdvgu0cqDcOD"}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.4.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.4.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./pkg/index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./pkg"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n   npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible module.\n\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.4.0","dist":{"shasum":"c41ef30588aa3993f217609c4830cb6476ce318a","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.4.0.tgz","integrity":"sha512-dstg2rnJueYA1FVOel2v5ANuIqDDvCJ/+idGk8ITw8FIuN4799OOvwNs36OVP6H53RJdasCsFTLbfXZkVv1tlQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDLc7Ltewkl7z8ILoiKGOHBe8BEZEhSziun12442oDsWQIgLnhIIe8x83FKOHsV8Zl2V8wqhChOV/HhdIvEA1WshPM="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.5.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.5.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n   npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.5.0","dist":{"shasum":"f882f201bcf128cc7489e75ccee6cbccf6d35c26","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.5.0.tgz","integrity":"sha512-UBETlHHAU1v8NKOBLQUA+B41ulzEW541PdUvCvQWXA8OOVvZKsrpllj3uYuGqB9xhN3hMqjy+UTr1dhKGTHfKA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDwVAGnSEwxOOXL6LAu4jhwyBGLW/9mGLFnS6TTndv4jQIgPhDAoM1xPwuZLvkqb2NAwU6/NbIv2hVOYZPldGJfPaY="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.5.1":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.5.1","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n   npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.5.1","dist":{"shasum":"fc86fe46d44062a1668f19c5d2cffff6a4cd1f2d","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.5.1.tgz","integrity":"sha512-rRTBsr0H7qlCit0BW9o5b8UWt5+/Ae+dQ04E0K2H0zZZgLcsNdoNUtw2+zxjxdTOjH+txy0qgxw723YkSFFueA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDbXTigMbkXbJlrRU4BvNi6xyQi2cv+q2aZ9XvaP1fDQAiEA8bEZe2zGzAcZ5E23K3KXYxWWwA+vkY+uZrBJRr2nNX8="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.6.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.6.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node ./_build/convert.js"},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install .\n    node build\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\n","_id":"amd-utils@0.6.0","dist":{"shasum":"3a860ed3a5339e1afa1ba888c37582430beb66f0","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.6.0.tgz","integrity":"sha512-m6g/MqSri9hSAUbFqtHjAtzFHnUJteLsvNl/z6XC3PEE17FC+9MjqFOMSmlapxAvrVM2dlopZAMVlkh/arLnGw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBo25GWIi3SHfHnra7mtfq5Q3CgIrJ3eIJaT1nc07UG4AiAu3nOD6tSnV/PYF1o4C7+Z/EdFDmOwHisGeIrbazd8xA=="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.7.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.7.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","dependencies":{"wrench":"~1.3.9","amdefine":">= 0.0.2"},"scripts":{"install":"node build cjs ."},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6","commander":"~1.0.5"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install --dev\n    node build doc\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\n\n\n## Keeping packages and specs in sync ##\n\nThe build script can be used to update packages and specs files:\n\n    node build pkg\n\nYou can also add new modules with the command `node build add\npackage/moduleName`, this will create a new module `moduleName` inside the\nfolder `src/package` and also a failing spec inside the `tests` folder.\n\nFor other available options see `node build -h`.\n\n\n\n## Documentation ##\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\nor inside the `doc` folder.\n","_id":"amd-utils@0.7.0","dist":{"shasum":"b0cfe1086a557b36973709b3df99d1f80bccd443","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.7.0.tgz","integrity":"sha512-YdOxlie/KxmueZy5SJcC+vXcw2uauPn3amc63EQQfpU6hQ0qpb1jAdaJXB2gfpTSV4vxZGXUZ4vLqHffLDIr2A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFL+SyBL00RoyJoDttb+SFEX3+Zj/UeJewq33tiDZUQtAiEAvq9dQ3RVqo3XFnlP9ns1pDkaAJWbCkT0etThgCkQdqw="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.8.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.8.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","dependencies":{"wrench":"~1.3.9","nodefy":"0.2.x"},"scripts":{"install":"node build cjs ."},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"mdoc":"~0.3.2","handlebars":"~1.0.6","commander":"~1.0.5"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install --dev\n    node build doc\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\n\n\n## Keeping packages and specs in sync ##\n\nThe build script can be used to update packages and specs files:\n\n    node build pkg\n\nYou can also add new modules with the command `node build add\npackage/moduleName`, this will create a new module `moduleName` inside the\nfolder `src/package` and also a failing spec inside the `tests` folder.\n\nFor other available options see `node build -h`.\n\n\n\n## Documentation ##\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\nor inside the `doc` folder.\n","_id":"amd-utils@0.8.0","dist":{"shasum":"3035acf2f50d8a4d6408d2556da9233a46bca696","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.8.0.tgz","integrity":"sha512-wS006dqf1sxzo38sLCTkFhl/MP1HJyB8xBQD4z8N/F45vXu8GaQQGHzqOp7L3297CvwiLD88fGFeSPYVtJzvbA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDiI/6m1i3VswzEVqGX+g7gLv146cQxNxJvH5FyDafrGAIgYijMJKahALvu9OQXSnccwFiKJHpP1Owg1oWPMX1PlMU="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.8.1":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.8.1","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","scripts":{"prepublish":"node build cjs ."},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"nodefy":"0.2.x","mdoc":"~0.3.2","handlebars":"~1.0.6","commander":"~1.0.5"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install --dev\n    node build doc\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\n\n\n## Keeping packages and specs in sync ##\n\nThe build script can be used to update packages and specs files:\n\n    node build pkg\n\nYou can also add new modules with the command `node build add\npackage/moduleName`, this will create a new module `moduleName` inside the\nfolder `src/package` and also a failing spec inside the `tests` folder.\n\nFor other available options see `node build -h`.\n\n\n\n## Documentation ##\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\nor inside the `doc` folder.\n","_id":"amd-utils@0.8.1","dist":{"shasum":"f3e9f7ba184d4d78aea1d1fa05bcb56e052ff0d2","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.8.1.tgz","integrity":"sha512-kjIU55B7M2gPBbi9oGoqfDzuCoMCp2wMDvu0PHM3ggVDM1yGZXeDulIsrHBbyedp6Z9hvc/zXYws8cxkWVATZA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDVNP6A/dR3k0bDmJuFXgPmoKF0SlvX7j0eelYIVbQpFQIgXqdKqSYXjk4lqTp3ZqxvBjXNm5QcbRnXLNXp4J9vJZM="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.9.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.9.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional","amd"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","scripts":{"prepublish":"node build cjs ."},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"nodefy":"0.2.x","mdoc":"~0.3.2","handlebars":"~1.0.6","commander":"~1.0.5"},"readme":"# amd-utils #\n\nhttp://millermedeiros.github.com/amd-utils\n\nmodular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!** Read these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n\nYour mileage may vary...\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Building The Documentation ##\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    npm install --dev\n    node build doc\n\nIt will replace all the files inside the `doc/html` folder and update packages\nand specs runners, this way we avoid human mistakes.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\n\n\n## Keeping packages and specs in sync ##\n\nThe build script can be used to update packages and specs files:\n\n    node build pkg\n\nYou can also add new modules with the command `node build add\npackage/moduleName`, this will create a new module `moduleName` inside the\nfolder `src/package` and also a failing spec inside the `tests` folder.\n\nFor other available options see `node build -h`.\n\n\n\n## Documentation ##\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\nor inside the `doc` folder.\n","_id":"amd-utils@0.9.0","dist":{"shasum":"6be0b53a365eb4528026a24aad37d52de12f4138","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.9.0.tgz","integrity":"sha512-MLS6eT9sDWP6VgN5MqpHir+XpdgMgeUTNoKBjmjPJTcIeSw7bjjjYvEIdFgRxsoirQx2Vj0T7rO6F1nTlLUsVw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFZfQhqmcke43m/9TFQLNlm9R/nhgauCzaFlhrihDuFMAiA5YZOqJtoZ5E5NtofvcvN60A+sz7J3XMLvSytxd4U1hQ=="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]},"0.10.0":{"name":"amd-utils","description":"Utility methods written in the AMD format","version":"0.10.0","homepage":"http://millermedeiros.github.com/amd-utils/","author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"},"keywords":["utilities","functional","amd"],"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"licenses":[{"type":"MIT","url":"http://www.opensource.org/licenses/mit-license.php"}],"bugs":{"url":"https://github.com/millermedeiros/amd-utils/issues/"},"main":"./index.js","scripts":{"prepublish":"node build cjs .","pretest":"node build pkg","test":"node node_modules/istanbul/lib/cli test tests/runner.js"},"directories":{"doc":"./doc/mdown","lib":"./"},"devDependencies":{"istanbul":"https://github.com/millermedeiros/istanbul/tarball/latest","jasmine-node":"~1.0.28","requirejs":"2.x","nodefy":"*","mdoc":"~0.3.2","handlebars":"~1.0.6","commander":"~1.0.5"},"readme":"# amd-utils #\n\n[![Build Status](https://secure.travis-ci.org/millermedeiros/amd-utils.png)](https://travis-ci.org/millermedeiros/amd-utils)\n\nhttp://millermedeiros.github.com/amd-utils\n\nModular JavaScript utilities written in the\n[AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) format.\n\nAll code is library agnostic and consist mostly of helper methods that aren't\ndirectly related with the DOM, the purpose of this library isn't to replace\nDojo, jQuery, YUI, Mootools, etc, but to provide modular solutions for common\nproblems that aren't solved by most of them.\n\n\n\n## Main goals ##\n\n - increase code reuse;\n - be clear (code should be clean/readable);\n - be easy to debug;\n - be easy to maintain;\n - follow best practices;\n - follow standards when possible;\n - **don't convert JavaScript into another language!**\n - be compatible with other frameworks;\n - be modular;\n - have unit tests for all modules.\n\n\n\n## What shouldn't be here ##\n\n - UI components;\n - CSS selector engine;\n - Event system - pub/sub;\n - Template engine;\n - Anything that could be a separate library and/or isn't a modular utility...\n\n\n\n\n## Why AMD? ##\n\n**Because AMD is awesome!**\n\nBy keeping each function in a separate package we can require just the\nmethods/packages that are required by our app and let the RequireJS optimizer\nbundle only what is currently being used. We also have an extra benefit that we\nsplit the methods into separate packages so we reduce the chance of name\ncollisions and the code is more organized. AMD is flexible and enables things\nthat wouldn't be possible with a different module system or with a conventional\nnamespace approach (remapping a module, conditionally loading, etc).\n\nRead these links if you still can't see why:\n\n - [Why AMD?](http://requirejs.org/docs/whyamd.html)\n - [AMD is better for the web than CJS modules](blog.millermedeiros.com/2011/09/amd-is-better-for-the-web-than-commonjs-modules/)\n - [AMD & CommonJS modules](http://briancavalier.com/presentations/pgh-js-amd-10-2011/)\n - [AMD vs. CJS](http://unscriptable.com/index.php/2011/09/30/amd-versus-cjs-whats-the-best-format/)\n - [Namespaces are Old School](http://blog.millermedeiros.com/namespaces-are-old-school/)\n\nPS: Your mileage may vary...\n\n\n\n## Node.js ##\n\nAMD-utils also works on [node.js](http://nodejs.org), just run:\n\n    npm install amd-utils\n\nIt will download amd-utils from the NPM repository and convert the AMD modules\ninto a node.js compatible format using\n[nodefy](https://github.com/millermedeiros/nodefy), there is no extra overhead,\nyou can use it like a regular node.js package.\n\n    // you can load individual methods\n    var map = require('amd-utils/array/map');\n    map([1, 2], function(v){ return val * val; }); // [1, 4]\n\n    // a single package\n    var stringUtils = require('amd-utils/string');\n    stringUtils.camelCase('Foo Bar'); // \"fooBar\"\n\n    // or the whole lib\n    var utils = require('amd-utils');\n    console.log( utils.math.clamp(100, 0, 50) ); // 50\n\n\n\n## Important ##\n\nSince each function is a separate module they have independent version numbers\nand a last edit date.\n\nSince code is very modular (broken into multiple files) it is really important\nthat you run an optimizer before deploying the code to a server, otherwise you\nmay end up having too many file requests which can [degrade load-time\nperformance](http://developer.yahoo.com/performance/rules.html#num_http) a lot.\nSee [RequireJS optimization](http://requirejs.org/docs/optimization.html) for\nmore info.\n\n\n\n## Contributing ##\n\nFork the project on Github: https://github.com/millermedeiros/amd-utils\n\n > \"Write clearly, don't be too clever\" - The Elements of Programming Style\n\nAvoid unnamed functions and follow the other modules structure. By only using\nnamed functions it will be easier to extract the code from the AMD module if\nneeded and it will also give better error messages, JavaScript minifiers like\n[Google Closure Compiler](http://code.google.com/closure/compiler/) and\n[UglifyJS](https://github.com/mishoo/UglifyJS) will make sure code is as\nsmall/optimized as possible.\n\n > \"Make it clear before you make it faster.\" - The Elements of Programming Style\n\nBe sure to always create tests for each proposed module. Features will only be\nmerged if they contain proper tests and documentation.\n\n > \"Good code is its own best documentation.\" - Steve McConnell\n\nWe should do a code review before merging to make sure names makes sense and\nimplementation is as good as possible.\n\nCheck the [contributors list at github](https://github.com/millermedeiros/amd-utils/contributors).\n\n\n## Build Script ##\n\nThe build script have a set of very helpful commands, run `npm install --dev`\n(only required once) and then check the available commands:\n\n    node build --help\n\n\n### Keeping packages and specs in sync ###\n\nThe build script can be used to update packages and specs files:\n\n    node build pkg\n\nThe packages/specs are automatically updated every time you run `npm test` as\nwell.\n\nYou can also add new modules with the command `node build add\npackage/moduleName`, this will create a new module `src/package/moduleName.js`\nand also a failing spec `tests/spec/package/spec-moduleName.js`.\n\n\n### Tests & Code Coverage ###\n\nTests can be found inside the `tests` folder, to execute them in the browser\nopen the `tests/runner.html`. The same tests also work on node.js by running\n`npm test`.\n\nWe should have tests for all methods and ensure we have a high code coverage\nthrough our continuous integration server\n([travis](https://travis-ci.org/millermedeiros/amd-utils)). When you ask for\na pull request Travis will automatically run the tests on node.js and check the\ncode coverage as well.\n\nWe run `node build pkg` automatically before any `npm test`, so specs and\npackages should always be in sync. (will avoid human mistakes)\n\nTo check code coverage run `npm test --coverage`, it will generate the reports\ninside the `coverage` folder and also log the results. Please note that node.js\ndoesn't execute all code branches since we have some conditionals that are only\nmet on old JavaScript engines (eg. IE 7-8), so we will never have 100% code\ncoverage (but should be close to it).\n\n\n### Building The Documentation ###\n\nThe documentation is generated based on markdown files inside the\n`doc/mdown` folder using [mdoc](https://github.com/millermedeiros/mdoc).\nTo compile the docs run:\n\n    node build doc\n\nIt will replace all the files inside the `doc/html` folder.\n\nDocumentation files should be always up-to-date since modules are only\ncommitted to the `master` branch after they get proper tests and documentation.\n\n\n\n\n## Documentation ##\n\nOnline documentation can be found at http://millermedeiros.github.com/amd-utils\nor inside the `doc` folder.\n\n\n\n## License ##\n\nReleased under the [MIT License](http://www.opensource.org/licenses/mit-license.php).\n\n","_id":"amd-utils@0.10.0","dist":{"shasum":"c2885559721d6669c3ca08809215ed6957ee400c","tarball":"https://registry.npmjs.org/amd-utils/-/amd-utils-0.10.0.tgz","integrity":"sha512-+/itpNFL/apEH+2CUrwfVAMjS/TcoploY7k4qb0JJT02LUu727G/XIErB8+pYoNUzO0r4FCpW9/VbxlYixlpEw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIC3u+1rgoiAk/haurHADbUAedciIWhJmO3MqgsWIs6FxAiEA0kwfQKxHfUgq3YZ3qSa0cqqwc5b/K/tV43k8TYLrhfI="}]},"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}]}},"readme":null,"maintainers":[{"name":"millermedeiros","email":"miller@millermedeiros.com"}],"time":{"modified":"2022-06-13T02:44:11.511Z","created":"2012-04-16T19:55:21.076Z","0.0.1":"2012-04-16T19:55:22.966Z","0.1.0":"2012-08-08T03:44:34.899Z","0.2.0":"2012-08-17T13:07:13.451Z","0.3.0":"2012-08-31T01:37:15.699Z","0.4.0":"2012-09-27T03:56:14.264Z","0.5.0":"2012-10-01T20:40:57.286Z","0.5.1":"2012-10-01T20:59:02.481Z","0.6.0":"2012-10-07T04:42:22.248Z","0.7.0":"2012-11-19T14:45:20.913Z","0.8.0":"2012-11-20T14:18:12.550Z","0.8.1":"2012-11-22T11:53:01.523Z","0.9.0":"2012-11-30T04:31:22.900Z","0.10.0":"2012-12-20T02:11:08.135Z"},"repository":{"type":"git","url":"git://github.com/millermedeiros/amd-utils.git"},"author":{"name":"Miller Medeiros","url":"http://blog.millermedeiros.com"}}