{"_id":"grunt-coffee-build","_rev":"49-9ffba47e8358b4d9ad23371ba616719a","name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","dist-tags":{"latest":"1.4.12"},"versions":{"0.0.1":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map":"~0.1.27","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"coffee-script":"~1.6.3"},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\nThis plugin requires Grunt `~0.4.1`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Usage Examples\n\n```coffeescript\ngrunt.initConfig\n  clean:\n    tests: ['build']\n\n  coffee_build:\n    options:\n      wrap: true\n      sourceMap: true\n      disableModuleWrap: ['index.coffee']\n    file:\n      cwd: 'test'\n      src: '**/*.coffee'\n      dest: 'build/build.js'\n    directory:\n      ext: '.js'\n      expand: true\n      flatten: false\n      cwd: 'test'\n      src: '**/*.coffee'\n      dest: './build/all'\n```\n\nWhen passing a filename to 'dest', the task will merge all files, parsing\n'require' calls to take dependency order into consideration. It will also\nreplace require calls with automatically generated identifiers representing the\nmodules(using the file path) so it can be used without commonjs.\n\nSince when combining every file is wrapped, the disableModuleWrap option can be\nused to override this behavior for certain files.\n\nWhen passing a directory to 'dest', it will compile each source file\nindividually.\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.1","dist":{"shasum":"b1f017faa0527ab95a1dda4b9290c3988bccc931","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.1.tgz","integrity":"sha512-VfYXnUKwshkX4KM49Jl0mXEthJBREGCsqLKbecmpHxzPEB2Yh32Ne1tfKvCltrGlRN1BddW/mKYRhXMsoc4J8Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFdSHwayq6dRPDpfHVKwzlIp6JQYmPC8lwrbOH6Snyx+AiByEM36vjNJqhDc36HHwUtsXCaI/kaMwAEQwIORwm1gEA=="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.2":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.2","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map":"~0.1.27","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour coffeescript files. It intends to provide a one-stop solution for\nbuilding web browsers or node.js coffeescript projects.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like closure. All require\ncalls are replaced by a module identifier generated from the file path(An\nidea taken from the google-traceur compiler)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be recompiled.\n\n### Example usage\n\nThis example shows how one can configure grunt to build a library that will\nwork seamless across web browsers and node.js:\n\n```coffeescript\ngrunt.initConfig\n  clean:\n    all: ['build']\n\n  coffee_build:\n    options:\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n      disableModuleWrap: ['index.coffee'] # disable module wrapping for the files listed here when doing a concatenated build\n    browser_build: # browser version is distributed as a single file\n      files: [\n      # src files\n      {cwd: 'src', src: '**/*.coffee', dest: './dist/browser/src.js'}\n      # test files\n      {cwd: 'test', src: '**/*.coffee', dest: './dist/browser/test.js'}\n      ]\n    nodejs_build: # nodejs version files are compiled individually\n      files: [\n      # src files\n      {expand: true, cwd: 'src', src: '**/*.coffee', dest: './dist/nodejs/src'}\n      # test files\n      {expand: true, cwd: 'test', src: '**/*.coffee', dest: './dist/nodejs/test'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment, excluding files passed to the 'disableModuleWrap'\noption(useful if you want a piece of code that isn't bound to a scope that has\nmodule/exports defined).\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: provide me with a single javascript file/source map\nthat maps(correctly) to the original source files\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.2","dist":{"shasum":"3b0f35c097c142093f44b88be632a5899c8acbd2","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.2.tgz","integrity":"sha512-5ZPLz6SedHpQ9uAN2cwnj95oBDy3pBnGTn633KG+9a2Gyar73zA9rvJb9cT1Xrm4Ztb8oQHsHsZ5O5+nCbGgrw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDHEpKGGyMF+zO4zXdEbQMeQdEEQV3gKSHPhRo5xCZ6RwIgTB0jlUcjZ3BgcEjltO+gi4LFq08i/k0UYKMHINAInCY="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.3":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.3","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour coffeescript files. It intends to provide a one-stop solution for\nbuilding web browsers or node.js coffeescript projects.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like closure. All require\ncalls are replaced by a module identifier generated from the file path(An\nidea taken from the google-traceur compiler)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be recompiled.\n\n### Example usage\n\nThis example shows how one can configure grunt to build a library that will\nwork seamless across web browsers and node.js:\n\n```coffeescript\ngrunt.initConfig\n  clean:\n    all: ['build']\n\n  coffee_build:\n    options:\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n      disableModuleWrap: ['index.coffee'] # disable module wrapping for the files listed here when doing a concatenated build\n    browser_build: # browser version is distributed as a single file\n      files: [\n      # src files\n      {cwd: 'src', src: '**/*.coffee', dest: './dist/browser/src.js'}\n      # test files\n      {cwd: 'test', src: '**/*.coffee', dest: './dist/browser/test.js'}\n      ]\n    nodejs_build: # nodejs version files are compiled individually\n      files: [\n      # src files\n      {expand: true, cwd: 'src', src: '**/*.coffee', dest: './dist/nodejs/src'}\n      # test files\n      {expand: true, cwd: 'test', src: '**/*.coffee', dest: './dist/nodejs/test'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment, excluding files passed to the 'disableModuleWrap'\noption(useful if you want a piece of code that isn't bound to a scope that has\nmodule/exports defined).\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: provide me with a single javascript file/source map\nthat maps(correctly) to the original source files\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.3","dist":{"shasum":"a60c023687300f873360a3cc5d77ab2ec2653044","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.3.tgz","integrity":"sha512-lfCR/EucOt8PMHNBm/WBLXBdaUNADeOQ9mU1WkrHzH5I9WUN45RzH35m8zOmAf/OpZCjo1dbaC08urRRHRvexg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA4rkzLKZexrkELx7QtgaIMC1hMWJTjNZ3XpOza20AkGAiAyW5qt9vpEHJo8CTxBBgcoiJlQLiI6rGzMsRgIyKGQQw=="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.4":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.4","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour coffeescript files. It intends to provide a one-stop solution for\nbuilding web browsers or node.js coffeescript projects.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like closure. All require\ncalls are replaced by a module identifier generated from the file path(An\nidea taken from the google-traceur compiler)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be recompiled.\n\n### Example usage\n\nThis example shows how one can configure grunt to build a library that will\nwork seamless across web browsers and node.js:\n\n```coffeescript\ngrunt.initConfig\n  clean:\n    all: ['build']\n\n  coffee_build:\n    options:\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n      disableModuleWrap: ['index.coffee'] # disable module wrapping for the files listed here when doing a concatenated build\n    browser_build: # browser version is distributed as a single file\n      files: [\n      # src files\n      {cwd: 'src', src: '**/*.coffee', dest: './dist/browser/src.js'}\n      # test files\n      {cwd: 'test', src: '**/*.coffee', dest: './dist/browser/test.js'}\n      ]\n    nodejs_build: # nodejs version files are compiled individually\n      files: [\n      # src files\n      {expand: true, cwd: 'src', src: '**/*.coffee', dest: './dist/nodejs/src'}\n      # test files\n      {expand: true, cwd: 'test', src: '**/*.coffee', dest: './dist/nodejs/test'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment, excluding files passed to the 'disableModuleWrap'\noption(useful if you want a piece of code that isn't bound to a scope that has\nmodule/exports defined).\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: provide me with a single javascript file/source map\nthat maps(correctly) to the original source files\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.4","dist":{"shasum":"5e465cf7204d8a299fe972e02a223e62c1890752","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.4.tgz","integrity":"sha512-XDhd5a7yV2sBddFZsZ8KdBbzp2FZI0twi/tDTd5Y3anUaDEfcrRUR5fYYGTHB6Lqz2sckoRU/UjbE/9xZpsUWA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCw+RCsLpVrgl0bJmaRr2uoEFBxmtgt+ti/og/oGNsNbwIgKqjJT1h/zZq1hzUGrYDWVZ3fBd0Zvr6dXtOf+ouSTys="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.5":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.5","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. It also supports merging javascript files, and the\nresulting source map will contain information about each individual file.\n\nWhile the name is 'coffee-build', this task may be used with javascript-only\nprojects just for the automatic dependency resolution and merged source map\ngeneration.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like closure. All require\ncalls are replaced by a module identifier generated from the file path(An\nidea taken from the google-traceur compiler).\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be recompiled.\n\nThis intends to provide a one-stop solution for building projects for\nweb browsers or node.js using coffeescript and/or javascript\n\n### Example usage\n\nThis example shows how you can configure a project that includes third party\nlibraries and needs to have platform-specific builds (browser/node.js):\n\n```coffeescript\n# Gruntfile.coffee\ngrunt.initConfig\n  # This project should work seamless in browser and node.js. Each platform\n  # will have a single .js file containing all the code, and a single .map\n  # file that can be used to easily debug using node-inspector or any browser\n  # that supports source map debugging.\n \n  coffee_build:\n    options:\n      # default options\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n    browser_build:\n      options:\n        # Merge the third party library into the browser dist, but disable source\n        # map generation and module wrapping for it. The browser_export.js file\n        # will export the public API to the window object(it needs to be included last).\n        disableModuleWrap: ['third_party/lib.js', 'platform/browser_export.js']\n        disableSourceMap: ['third_party/lib.js']\n      files: [\n      # src files\n      {src: ['third_party/lib.js', 'src/**/*.coffee'], dest: './dist/browser_src.js'}\n      # Test files. Since sources are likely to be required by the test files,\n      # 'browser_test' is the only file that needs to be included in the\n      # index.html that bootstraps the tests\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js' ], dest: './dist/browser_test.js'}\n      ]\n    nodejs_build:\n      options:\n        # The node.js version dont need to merge the library, but cannot include\n        # it using require in the sources shared with the browser(require calls to\n        # relative paths are preprocessed), so we use a special node-only file that is\n        # concatenated first and will require the library into the package namespace.\n        # Besides dependency initialization, this file might contain nodejs-specific code,\n        # so we dont include it in 'disableSourceMap' for debugging. We also need to\n        # export the package API, so the 'index.js' file is not wrapped into a module so\n        # the 'module/exports' names are bound to the nodejs module object.\n        disableModuleWrap: ['platform/nodejs_init.js', 'platform/nodejs_export.js']\n      files: [\n      # src files\n      {src: ['platform/nodejs_init.js', 'src/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_src.js'}\n      # test files\n      {src: ['platform/nodejs_init.js', 'test/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_test.js'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment, excluding files passed to the 'disableModuleWrap'\noption(useful if you want a piece of code that isn't bound to a scope that has\nmodule/exports defined).\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests),\ndebugging with [node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2)\nor google chrome should just work.\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.5","dist":{"shasum":"f7ff16878b4cf0befba8ca29a825b2e8b2d9b83d","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.5.tgz","integrity":"sha512-c/4prCl/D7jbUahrd8W+fVglCZlNvInVP9FHiRxUD98lFmnjFvVUschpXBAaXP1JbC2XAp8QWC/E/syZ2pu2hA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHNGp63tpBvp+wjnSpB6i0mbu5r6IT+vezIERSGpx00yAiEA2Z6LYJUJfoxJs2ZRr1PvUGlvXZMBavv7X6V/wpLTLJg="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.6":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.6","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\nprojects just for the automatic dependency resolution and merged source map\ngeneration.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be reprocessed.\n\n### Example usage\n\nThis example shows how you can configure a project that includes third party\nlibraries and needs to have platform-specific builds (browser/node.js):\n\n```coffeescript\n# Gruntfile.coffee\ngrunt.initConfig\n  # This project should work seamless in browser and node.js. Each platform\n  # will have a single .js file containing all the code, and a single .map\n  # file that can be used to easily debug using node-inspector or any browser\n  # that supports source map debugging.\n \n  coffee_build:\n    options:\n      # default options\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n    browser_build:\n      options:\n        # Merge the third party library into the browser dist, but disable source\n        # map generation and module wrapping for it. The browser_export.js file\n        # will export the public API to the window object(it needs to be included last).\n        disableModuleWrap: ['third_party/lib.js', 'platform/browser_export.js']\n        disableSourceMap: ['third_party/lib.js']\n      files: [\n      # Src build\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_src.js'}\n      # Test build. Since sources are likely to be required by the test files,\n      # 'browser_test.js' is the only file that needs to be included in the\n      # index.html that bootstraps the tests.\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_test.js'}\n      ]\n    nodejs_build:\n      options:\n        # The node.js version doesn't need to merge the library, but cannot include it\n        # using 'require' calls in the sources shared with the browser(only require calls\n        # to relative paths are preprocessed, but 'require' will be unavailable in the\n        # browser), so we use a special node-only file (node_init.js) that is concatenated\n        # first and will require the library into the package namespace. Besides\n        # dependency initialization, this file might contain nodejs-specific code, so we\n        # won't include it in 'disableSourceMap' since we need to debug.  We also need to\n        # export the package API, so the 'nodejs_export.js' file is not wrapped into an internal\n        # module since the 'module/exports' names need to be bound to the real nodejs\n        # module object(this file must be included last).\n        disableModuleWrap: ['platform/nodejs_init.js', 'platform/nodejs_export.js']\n      files: [\n      # src files\n      {src: ['platform/nodejs_init.js', 'src/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_src.js'}\n      # test files\n      {src: ['platform/nodejs_init.js', 'test/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_test.js'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps back to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment. Files added to the 'disableModuleWrap' option will be\nexcluded.\n\nIf a directory is specified as dest, files will be transformed individually.\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with [node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2)\nor google chrome should just work.\n\nThis intends to provide a one-stop solution for building projects for\nweb browsers or node.js using coffeescript and/or javascript. Enjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.6","dist":{"shasum":"7970aaf22644b2d925ad122b8feb3a23f38df6ab","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.6.tgz","integrity":"sha512-oVVUkDOcg4IKbWrCBrU9ESHN6bEd+kJSyYMC+MlWmq+aEoV3lqEwUaxfXx8X62YMJ2tx58FS+JPxIO95aI4rvg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDLz9b8QV3u4Jz7VnlzL3oW05WUKNAqOY6euGhaDvpSMwIgZgXmmJqbJ0O3tJvdb2uo9kT5RE774C/ke2p2NBjtTnc="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.7":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.7","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\nprojects just for the automatic dependency resolution and merged source map\ngeneration.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be reprocessed.\n\n### Example usage\n\nThis example shows how you can configure a project that includes third party\nlibraries and needs to have platform-specific builds (browser/node.js):\n\n```coffeescript\n# Gruntfile.coffee\ngrunt.initConfig\n  # This project should work seamless in browser and node.js. Each platform\n  # will have a single .js file containing all the code, and a single .map\n  # file that can be used to easily debug using node-inspector or any browser\n  # that supports source map debugging.\n \n  coffee_build:\n    options:\n      # default options\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n    browser_build:\n      options:\n        # Merge the third party library into the browser dist, but disable source\n        # map generation and module wrapping for it. The browser_export.js file\n        # will export the public API to the window object(it needs to be included last).\n        disableModuleWrap: ['third_party/lib.js', 'platform/browser_export.js']\n        disableSourceMap: ['third_party/lib.js']\n      files: [\n      # Src build\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_src.js'}\n      # Test build. Since sources are likely to be required by the test files,\n      # 'browser_test.js' is the only file that needs to be included in the\n      # index.html that bootstraps the tests.\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_test.js'}\n      ]\n    nodejs_build:\n      options:\n        # The node.js version doesn't need to merge the library, but cannot include it\n        # using 'require' calls in the sources shared with the browser(only require calls\n        # to relative paths are preprocessed, but 'require' will be unavailable in the\n        # browser), so we use a special node-only file (node_init.js) that is concatenated\n        # first and will require the library into the package namespace. Besides\n        # dependency initialization, this file might contain nodejs-specific code, so we\n        # won't include it in 'disableSourceMap' since we need to debug.  We also need to\n        # export the package API, so the 'nodejs_export.js' file is not wrapped into an internal\n        # module since the 'module/exports' names need to be bound to the real nodejs\n        # module object(this file must be included last).\n        disableModuleWrap: ['platform/nodejs_init.js', 'platform/nodejs_export.js']\n      files: [\n      # src files\n      {src: ['platform/nodejs_init.js', 'src/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_src.js'}\n      # test files\n      {src: ['platform/nodejs_init.js', 'test/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_test.js'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps back to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment. Files added to the 'disableModuleWrap' option will be\nexcluded.\n\nIf a directory is specified as dest, files will be transformed individually.\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with [node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2)\nor google chrome should just work.\n\nThis intends to provide a one-stop solution for building projects for\nweb browsers or node.js using coffeescript and/or javascript. Enjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.7","dist":{"shasum":"00d6a8e603ec8db7b5ed22f36260f128c83573ce","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.7.tgz","integrity":"sha512-T6bnPfTkKz9YHsEvCvOIxcFlWUKatvYQIQXbEF3VNyDNc4YT9fAg1zjxBoGxEZTysyZwBRlVzfFrV7w/V+DkOw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCfs2GFpLQWKetRN/qZGiE5ifyBRKwbDgOov7WjP9BP1AIhAN/pGLrU5y+Q+jR1xiWy/A2WNLUshqjXgfN1IRJj407/"}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"0.0.8":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"0.0.8","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6"},"readme":"# grunt-coffee-build\n\n> Compiles coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\nprojects just for the automatic dependency resolution and merged source map\ngeneration.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be reprocessed.\n\n### Example usage\n\nThis example shows how you can configure a project that includes third party\nlibraries and needs to have platform-specific builds (browser/node.js):\n\n```coffeescript\n# Gruntfile.coffee\ngrunt.initConfig\n  # This project should work seamless in browser and node.js. Each platform\n  # will have a single .js file containing all the code, and a single .map\n  # file that can be used to easily debug using node-inspector or any browser\n  # that supports source map debugging.\n \n  coffee_build:\n    options:\n      # default options\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n    browser_build:\n      options:\n        # Merge the third party library into the browser dist, but disable source\n        # map generation and module wrapping for it. The browser_export.js file\n        # will export the public API to the window object(it needs to be included last).\n        disableModuleWrap: ['third_party/lib.js', 'platform/browser_export.js']\n        disableSourceMap: ['third_party/lib.js']\n      files: [\n      # Src build\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_src.js'}\n      # Test build. Since sources are likely to be required by the test files,\n      # 'browser_test.js' is the only file that needs to be included in the\n      # index.html that bootstraps the tests.\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_test.js'}\n      ]\n    nodejs_build:\n      options:\n        # The node.js version doesn't need to merge the library, but cannot include it\n        # using 'require' calls in the sources shared with the browser(only require calls\n        # to relative paths are preprocessed, but 'require' will be unavailable in the\n        # browser), so we use a special node-only file (node_init.js) that is concatenated\n        # first and will require the library into the package namespace. Besides\n        # dependency initialization, this file might contain nodejs-specific code, so we\n        # won't include it in 'disableSourceMap' since we need to debug.  We also need to\n        # export the package API, so the 'nodejs_export.js' file is not wrapped into an internal\n        # module since the 'module/exports' names need to be bound to the real nodejs\n        # module object(this file must be included last).\n        disableModuleWrap: ['platform/nodejs_init.js', 'platform/nodejs_export.js']\n      files: [\n      # src files\n      {src: ['platform/nodejs_init.js', 'src/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_src.js'}\n      # test files\n      {src: ['platform/nodejs_init.js', 'test/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_test.js'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps back to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment. Files added to the 'disableModuleWrap' option will be\nexcluded.\n\nIf a directory is specified as dest, files will be transformed individually.\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with [node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2)\nor google chrome should just work.\n\nThis intends to provide a one-stop solution for building projects for\nweb browsers or node.js using coffeescript and/or javascript. Enjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@0.0.8","dist":{"shasum":"86ef805dac49d31546b26e53ac28d70974b1c2e1","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-0.0.8.tgz","integrity":"sha512-d1iOKdE1KTcsOmXZVbHcr+U9/UU0wJXdEyVz+v7pesRjxERREGVD0zRzBwX5KpInoFQJmFh7wV4lKRHbk7vJ2Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCpkjKwfd0lUjtSXRTlc6BhtJSpjvu+a62F3FRUJU2ddgIgHpyB90IK9A8COfN2B5Mynom1zKrOBML4g7xvfhEA+LM="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.0.1":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"1.0.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12"},"readme":"# grunt-coffee-build\n\n> Compiles coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\nprojects just for the automatic dependency resolution and merged source map\ngeneration.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nThe task integrates nicely with grunt-contrib-watch, as it will keep an\nin-memory cache of the compiled files and their modification date, so only\nmodified files will be reprocessed.\n\n### Example usage\n\nThis example shows how you can configure a project that includes third party\nlibraries and needs to have platform-specific builds (browser/node.js):\n\n```coffeescript\n# Gruntfile.coffee\ngrunt.initConfig\n  # This project should work seamless in browser and node.js. Each platform\n  # will have a single .js file containing all the code, and a single .map\n  # file that can be used to easily debug using node-inspector or any browser\n  # that supports source map debugging.\n \n  coffee_build:\n    options:\n      # default options\n      wrap: true # wrap the result into an anonymous function\n      sourceMap: true # generate source maps\n    browser_build:\n      options:\n        # Merge the third party library into the browser dist, but disable source\n        # map generation and module wrapping for it. The browser_export.js file\n        # will export the public API to the window object(it needs to be included last).\n        disableModuleWrap: ['third_party/lib.js', 'platform/browser_export.js']\n        disableSourceMap: ['third_party/lib.js']\n      files: [\n      # Src build\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_src.js'}\n      # Test build. Since sources are likely to be required by the test files,\n      # 'browser_test.js' is the only file that needs to be included in the\n      # index.html that bootstraps the tests.\n      {src: ['third_party/lib.js', 'src/**/*.coffee', 'platform/browser_export.js'], dest: './dist/browser_test.js'}\n      ]\n    nodejs_build:\n      options:\n        # The node.js version doesn't need to merge the library, but cannot include it\n        # using 'require' calls in the sources shared with the browser(only require calls\n        # to relative paths are preprocessed, but 'require' will be unavailable in the\n        # browser), so we use a special node-only file (node_init.js) that is concatenated\n        # first and will require the library into the package namespace. Besides\n        # dependency initialization, this file might contain nodejs-specific code, so we\n        # won't include it in 'disableSourceMap' since we need to debug.  We also need to\n        # export the package API, so the 'nodejs_export.js' file is not wrapped into an internal\n        # module since the 'module/exports' names need to be bound to the real nodejs\n        # module object(this file must be included last).\n        disableModuleWrap: ['platform/nodejs_init.js', 'platform/nodejs_export.js']\n      files: [\n      # src files\n      {src: ['platform/nodejs_init.js', 'src/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_src.js'}\n      # test files\n      {src: ['platform/nodejs_init.js', 'test/**/*.coffee', 'platform/nodejs_export.js'], dest: './dist/nodejs_test.js'}\n      ]\n```\n\nAs the above example shows, when a filename is passed to 'dest', the task will\nconcatenate all files, generating a source map that maps back to the original files.\n\nBy default each merged file is wrapped into a module function that simulates a\ncommonjs environment. Files added to the 'disableModuleWrap' option will be\nexcluded.\n\nIf a directory is specified as dest, files will be transformed individually.\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with [node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2)\nor google chrome should just work.\n\nThis intends to provide a one-stop solution for building projects for\nweb browsers or node.js using coffeescript and/or javascript. Enjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.0.1","dist":{"shasum":"b38230d69fcb1067fd3f6c5aefe5c8870ad198b9","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.0.1.tgz","integrity":"sha512-Xqm5dkvfpNWWsF2GLQN+OZi7fZKVjgW2l3vcGWS2LbabFgb7ET0EgI44LUCUrPYfkcWIVy+yBydWJwCCGqO8eQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCnbyMl+StCGuZubH7ocKWK81rr2NqjYS6OO/vKDSQbMQIgespeHjxHTMH97rHFGEADKEhRWXrNyez4skGR+HqyI2g="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.1.1":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"1.1.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12"},"readme":"# grunt-coffee-build\n\n> Compiles hybrid coffeescript/javscript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load) \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\n### Example usage\n\nThis example shows a real project([vm.js](https://github.com/tarruda/vm.js))\nthat runs on browser or node.js. It depends on the 'esprima' parser, so\nthird party library handling is also illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        moduleId: 'Vm'\n        # it is necessary to specify a main file which exports the\n        # module public API, just like one normally does in a package.json\n        # file \n        main: 'src/index.coffee'\n        src: 'src/**/*.coffee'\n      browser:\n        # this target will build everything to a single umd module.\n        # it is meant for javascript environments without a module loader\n        # like web browsers, but it should work anywhere.\n        options:\n          # if you depend on a third party library of a specific version\n          # and are targeting web browsers without a module loader,\n          # bundle the library in the 'includedDeps' options and it will be\n          # run in a fake global object/context so it can coexists with\n          # other versions of the library already loaded.\n          # As an altenative you can just load the third party library\n          # separately.\n          # \n          # In this particular case everything works because esprima uses the\n          # same name for the node.js module and the browser global object(it\n          # is also wrapped in umd). \n          # \n          # In most cases this should work as long as the library is consistent\n          # regarding its global object alias and commonjs module name\n          includedDeps: 'node_modules/esprima/esprima.js'\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # this target will build a bundle containing the code plus\n        # automated tests. no need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs_test:\n        # while the above target could also be reused, this is preferred\n        # when you dont need to re-run browser tests everytime,\n        # as only modified files will ever need to be recompiled since\n        # files are being compiled individually. (when merging compilation\n        # will only be cached in memory, so it works better with\n        # grunt-contrib-watch and nospawn: true)\n        options:\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # if the destination doesnt end with '.js' it will be considered\n          # a directory build\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.1.1","dist":{"shasum":"af53a3e3625e1c34c384534a427adb730735508b","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.1.1.tgz","integrity":"sha512-4MZFaIh3CFSJaF4nVu22V/Nn289fAIgvYZ8099vTTSVdEgiVeB49z1HlBhmYhTXfrGbJTn5qApQ93tL5QT2o3w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDyKrUL5kPFq9BJ7GBF5rP6lhSguFMSHvZ7z1Aj1MFRYAIgEGmUMEh4gJv4N+Zl8C5sFgT4mRQvqBWiBftWO0BUBGc="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.2.1":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"1.2.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12"},"readme":"# grunt-coffee-build\n\n> Compiles hybrid coffeescript/javscript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load) \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\n### Example usage\n\nThis example shows a real project([vm.js](https://github.com/tarruda/vm.js))\nthat runs on browser or node.js. It depends on the 'esprima' parser, so\nthird party library handling is also illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        moduleId: 'Vm'\n        # it is necessary to specify a main file which exports the\n        # module public API, just like one normally does in a package.json\n        # file \n        main: 'src/index.coffee'\n        src: 'src/**/*.coffee'\n      browser:\n        # this target will build everything to a single umd module.\n        # it is meant for javascript environments without a module loader\n        # like web browsers, but it should work anywhere.\n        options:\n          # if you depend on a third party library of a specific version\n          # and are targeting web browsers without a module loader,\n          # bundle the library in the 'includedDeps' options and it will be\n          # run in a fake global object/context so it can coexists with\n          # other versions of the library already loaded.\n          # As an altenative you can just load the third party library\n          # separately.\n          # \n          # In this particular case everything works because esprima uses the\n          # same name for the node.js module and the browser global object(it\n          # is also wrapped in umd). \n          # \n          # In most cases this should work as long as the library is consistent\n          # regarding its global object alias and commonjs module name\n          includedDeps: 'node_modules/esprima/esprima.js'\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # this target will build a bundle containing the code plus\n        # automated tests. no need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs_test:\n        # while the above target could also be reused, this is preferred\n        # when you dont need to re-run browser tests everytime,\n        # as only modified files will ever need to be recompiled since\n        # files are being compiled individually. (when merging compilation\n        # will only be cached in memory, so it works better with\n        # grunt-contrib-watch and nospawn: true)\n        options:\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # if the destination doesnt end with '.js' it will be considered\n          # a directory build\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without runtime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.2.1","dist":{"shasum":"439bc208ea17c96d9322a99aa729e1e26fd3a86b","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.2.1.tgz","integrity":"sha512-24twl2eS/IvvkvmifnVxRWIZxtZTayy8HqSqFp9J13QrsbKn6y5wdiXynqgsbE/TEPSI93LRxB8k415e08aS4A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD1XRNH2LajSAkdngDXXUeNeLxIuk1LLYsrzooI3qR6cwIhAPvaSe3BOM/RJtJmM0X/fMmAWOYm0vl7iUwzhivmcbkj"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.3.1":{"name":"grunt-coffee-build","description":"Compiles Coffeescript files, optionally merging and generating source maps.","version":"1.3.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12"},"readme":"# grunt-coffee-build\n\n> Compiles hybrid coffeescript/javscript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load) \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime. Instead, it will\nparse all require calls for relative paths, concatenate files in dependency\norder while wrapping each file into a commonjs-like module. All require\ncalls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # It is necessary to specify a main file which exports the package\n        # public API, just like one normally does in a package.json file.\n        # If this is not provided it will be extracted from the package.json \n        # file\n        main: 'src/index.js'\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm', 'vm.js']\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If you depend on a third party library(maybe a specific version)\n          # or are targeting web browsers without a module loader\n          # it is possible bundle the library with the rest of the code\n          # by specifying its path in the 'includedDeps' options. Bundled\n          # libraries run in a fake global object/context/window so it\n          # can coexist with other versions of the library already loaded.\n          #\n          # As an altenative you can just load the library separately.\n          #\n          # In either case, requiring the library should just work as long\n          # as it uses its package name(the string you pass to the 'require'\n          # function) as a global alias. Esprima meets this condition.\n          #\n          # If the library uses a different global alias it is still possible\n          # to use it by specifying a map of alias -> global property \n          # in the 'depAliases' option\n          #\n          # For example if esprima exported its API to the global property\n          # 'ESPRIMA' then the 'require(\"esprima\")' calls would not work\n          # out-of-box. The following option can be added to browser-specific\n          # builds to fix the problem:\n          # depAliases: {esprima: 'ESPRIMA'};\n          includedDeps: 'node_modules/esprima/esprima.js'\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for two reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #      with the 'nospawn' option set.\n        #   - It integrates better with browserify\n        options:\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # if the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks.\n\nThe source maps generated by this task work flawless(at least in my tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\n Enjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.3.1","dist":{"shasum":"9cad2cf0d83f4714fa37d63dbbd613c5e43bca05","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.3.1.tgz","integrity":"sha512-jyvIkLgevppqr9X58FBrG+3GzSdpLlKyUO4/mzZ+HrnkUS2tfPmoa7Gm1K9t1Feyvzt7UD9m7SRQ8yMD+49Qiw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCL219vT0O3/rc/ht3P+5X6XcxnGj2L9TIRiN2ip3HGeAIhALkUpydvX6/iKhR2FlXO1ncKcDd81H8/xBa2wYokM892"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.1":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.1","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', expose: 'angular'}\n          # ]\n          # then require('angular') will work.\n          # \n          # Its possible to provide an alias to the exposed global property.\n          # Eg:\n          # include: [\n          #   {path: './vendor/angular/angular.js', expose: 'angular',\n          #    alias:'angular.js'}\n          # ]\n          # then require('angular.js') should work too\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm(the same version is used for browser and node.js).\n          #\n          # It is also possible to require libraries loaded normally by\n          # the browser by just invoking require('{global alias}'). For\n          # example, if jquery was loaded from another file require('jQuery')\n          # or require('$') should work.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #      with the 'nospawn' option set.\n        #   - It integrates better with browserify\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.1","dist":{"shasum":"578cf2c2de4388f427637dcac98e3f7d17e2521c","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.1.tgz","integrity":"sha512-Y2v/KhLyeAqVbRrbk6nbpyu+v5kuM+1trUCb81cKi7JsOps07TCs1Lc+PiEeF6+ptsLD69li84PvpjlwQVW8Xg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD/mYtK4VVui5FhmZGyKQlOK48+KudP1FUIynIF32tznwIga17/qwxO3/iYxCL2PCIoDwyEf9eztgpeT67ZXnjOXaM="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.2":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.2","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.2","dist":{"shasum":"bb64f1c9460141e197725688defb312079e3b484","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.2.tgz","integrity":"sha512-cEzhUjKSDuptsDvr4Z4UWKyZ8PUcLw4Usg07Wgx/tchh+3Wfz07sRg3EYaHRQOnew6HqRpb3FShwtBJz3K22Pg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDEyGjQHVtfZV0PuiR2gFtwVv87obj2zJ9WcWAwD2j24wIgX0vyUBYdVagdG0kFzdt9ho/6Q041gjXJpg7XBNKVylY="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.3":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.3","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.3","dist":{"shasum":"1791dcbcd4b85b58c2282ee4e9187ba95f159b22","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.3.tgz","integrity":"sha512-CmerA6lG6L5UXuEQQjTwKwQh/W7lzpSefya3eqflfZDFShRFGWYyQOkO0hxPERkFzWlg6Fb8i0kvxf9H95Wecw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIB3WNCPCECgR4Wv8cctUAkPCrdJetoorFcJbOLVCO267AiEA6TQAm4CxX016tFVx6bGRA0KaGuthBbzoxl1Xu/klVak="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.4":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.4","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.4","dist":{"shasum":"0dd5fef30cdc1c507d9d6f764e118ffaf937aeec","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.4.tgz","integrity":"sha512-rCasP1Jlart1YHeVDA2SiKZZSNWvfHZ1tjgmvmbTwJ6vbgkiQHM/9PlazmF42ELuNdDusXzErELJ8gKADbBUzw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDZncuH+AXOEjMJWILORpFqG2e57xIHN/P3F1XFHRUh2AiEAqnw1y10OJB+YNf5w9g1kkww7uVsgnc+k24BzUs+NP4Q="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.5":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.5","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Example usage\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.5","dist":{"shasum":"fc4ef5203843a8edd33629b6ff0cf11e737e8eb8","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.5.tgz","integrity":"sha512-5qUnk0I5XfymnXw0H4gqjEzWM6a7HJk1WPAUeQYbR8OQg7/vv+nggktj02oGEgl9TfE2A5GlMR0WsPMMtOZ5xg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD6xiRpIioyJrIK6pBPkZCT0VyF9W3eTwdlvTu3uXHF0wIgARy8UWWZUTxNVQZw+M2PnCuqS01N7KAOfrO6zppZfms="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.6":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.6","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nUnlike other solutions that normalize commonjs projects to work in web\nbrowsers, this one won't bundle a small commonjs runtime(unless the browserify\noption is set). Instead, it will parse all require calls for relative paths,\nconcatenate files in dependency order while wrapping each file into a\ncommonjs-like module.  All require calls are replaced by a module identifier\ngenerated from the file path (This is how google-traceur compiler handles\nimports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run. This mode of operation also integrates nicely with\ngrunt-contrib-watch, as it will keep an in-memory cache of the compiled files\nand their modification date, so only modified files will be reprocessed.\n\nWhen compiling to a directory(normal commonjs target) each file modification\ntimestamp will be saved, so only modified files are recompiled(even across\ngrunt restarts).\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option.\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.6","dist":{"shasum":"a2c40c7a896242dd7a3d06848b4c82c0675c019c","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.6.tgz","integrity":"sha512-TxLEQ9nq13w+QxcsLlbQrCrw45Hp9q5IIDyYbBAOaK6SiF2BdGa2CYmAfa9aQRGGXY6hRPku26t5QfSwftXh4A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD/VmJDC3ZEIxzqdJLyJg/TMSmZeUssI6Px8QWErcMmYQIgI2h8gd8oM1ZisgnRhDi+a1i9wV+ZeU5fXC6TGFLzTsY="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.7":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.7","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nThe task will parse all require calls for relative paths, concatenate files in\ndependency order while wrapping each file into a commonjs-like module.  All\nrequire calls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run.\n\nThe task will also cache individual file builds, so only modified files will\nneed to be reprocessed again.\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option. Browserify builds will\nalso be cached, but only in memory(useful with grunt-contrib-watch).\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.7","dist":{"shasum":"13bdc633bb0079edb7e31b71c45e100bee89f053","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.7.tgz","integrity":"sha512-9DxfUCQlxjsrczeKCcZxXUSQZSG8nz2nkSJtzus7fXZjLKBVHBEGK8+M0mACluKl+sfgbISkGGP9gykp+r3rxQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC2FWl8scTeUVK7mV0fMb65i6mMZ0kbQ9JR0OkAMx/enQIhAM2MNsikWNgZRicRBSWcAFZeBhqwrufuI5ZznkAoITVZ"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.8":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.8","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nThe task will parse all require calls for relative paths, concatenate files in\ndependency order while wrapping each file into a commonjs-like module.  All\nrequire calls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run.\n\nThe task will also cache individual file builds, so only modified files will\nneed to be reprocessed again.\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option. Browserify builds will\nalso be cached, but only in memory(useful with grunt-contrib-watch).\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.8","dist":{"shasum":"1eadf8dae3af7f12c6f6d9a5afc058f5afb9ff0b","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.8.tgz","integrity":"sha512-511LC8+6h5lGRy4hqGZLalZCYyu7q6Gf0vGqfw/N9dI2jVgd/3VtlbHPIAMzdD/MQyGzIMMWJxqHjsk2hMocnA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCsXyXvErU97hJXGXC5bstMTpPS4Vk3WvJ8WCLqxBhJJQIhAL0ZFV6C4A2ZmS6bo4J+CQ/aCmdVGex7XUuG2FzOJG+6"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.9":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.9","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nThe task will parse all require calls for relative paths, concatenate files in\ndependency order while wrapping each file into a commonjs-like module.  All\nrequire calls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run.\n\nThe task will also cache individual file builds, so only modified files will\nneed to be reprocessed again.\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option. Browserify builds will\nalso be cached, but only in memory(useful with grunt-contrib-watch).\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.9","dist":{"shasum":"7d51f3274b13c7b8b362caa491345eefcd8d6fe2","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.9.tgz","integrity":"sha512-lrXp6+NHvRkele1+bJyO4LNEtqLD++nON131yYXtQ7nDWKRYq8lHVsox8LiQsKN8uj24RWUYcDLjRsoF9GvE4w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFqC8Gj/lanH55Fn1GVlsoL0m7L5NeNF2T1tIP9IsWzgIhAMb3BBd6pNeISEVGVHeJRTITDtHf7ArcWnp+xcLPJhLp"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.11":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.11","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### The fastest way of getting started with this task:\n```shell\nnpm install -g grunt-init  # if you dont have\ngit clone git://github.com/tarruda/grunt-init-umd-commonjs-coffee ~/.grunt-init/umd-commonjs-coffee\nmkdir project_name\ncd project_name\ngrunt-init umd-commonjs-coffee # answer questions\nnpm install # install dev dependencies\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nThe task will parse all require calls for relative paths, concatenate files in\ndependency order while wrapping each file into a commonjs-like module.  All\nrequire calls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run.\n\nThe task will also cache individual file builds, so only modified files will\nneed to be reprocessed again.\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option. Browserify builds will\nalso be cached, but only in memory(useful with grunt-contrib-watch).\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.11","dist":{"shasum":"b488b93de50f95dbeee69d811d4fba4e8374b495","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.11.tgz","integrity":"sha512-NyH0i8coUO7If1BOsBFH1y5aSoyYU/h7Sf3BU0Pc7c/rjbrwjzgf50m0fYd1Bo6JNpj7595c4s/Ki38y33zY4g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA4YX7sTILqEUAdCkCPhi1xwuShPBSGebZyINbxHMo4SAiAOyMVL/nLuRz2C/ThkdU1SuYW1CkaDeIxw7FnZ/5tRCg=="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]},"1.4.12":{"name":"grunt-coffee-build","description":"Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally browserifying dependencies.","version":"1.4.12","homepage":"https://github.com/tarruda/grunt-coffee-build","author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"},"bugs":{"url":"https://github.com/tarruda/grunt-coffee-build/issues"},"licenses":[{"type":"MIT","url":"https://github.com/tarruda/grunt-coffee-build/blob/master/LICENSE-MIT"}],"main":"Gruntfile.coffee","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-clean":"~0.4.0","grunt":"~0.4.1","source-map-support":"~0.2.1","grunt-release":"~0.5.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin","commonjs","build","grunt","browserify"],"dependencies":{"source-map":"~0.1.27","coffee-script":"~1.6.3","uglify-js":"~2.3.6","handlebars":"~1.0.12","lexical-scope":"0.0.14","browserify":"~2.29.1"},"readme":"# grunt-coffee-build\n\n> Builds hybrid coffeescript/javascript commonjs projects to run anywhere transparently(amd, commonjs or plain browser load), generating combined source maps and optionally [browserifying](https://github.com/substack/node-browserify) dependencies. \n\n## Getting Started\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### The fastest way of getting started with this task:\n```shell\nnpm install -g grunt-init  # if you dont have\ngit clone git://github.com/tarruda/grunt-init-umd-commonjs-coffee ~/.grunt-init/umd-commonjs-coffee\nmkdir project_name\ncd project_name\ngrunt-init umd-commonjs-coffee # answer questions\nnpm install # install dev dependencies\n```\n\n### Overview\n\nThis task will take care of compiling, merging and generating source maps for\nyour .coffee/.js files. If merging, the resulting source map will contain\ninformation about each individual file so they can be debugged separately.\n\nWhile the name is 'coffee-build', this task may be used in javascript-only\ncommonjs projects just for the automatic dependency resolution and merged\nsource map generation.\n\nThe task will parse all require calls for relative paths, concatenate files in\ndependency order while wrapping each file into a commonjs-like module.  All\nrequire calls are replaced by a module identifier generated from the file path\n(This is how google-traceur compiler handles imports when merging files)\n\nWhen compiling the project to a single file, the task will wrap everything into\n[umd](https://github.com/umdjs/umd), and the result runs anywhere a umd module\nwould run.\n\nThe task will also cache individual file builds, so only modified files will\nneed to be reprocessed again.\n\nNode/npm modules will be bundled if the browserify option is set and external\nlibraries may be included using the 'include' option. Browserify builds will\nalso be cached, but only in memory(useful with grunt-contrib-watch).\n\n### Sample configuration\n\nThis is an example adapted from a real project\n([vm.js](https://github.com/tarruda/vm.js)) that runs on browser or node.js.\nIt depends on the 'esprima' parser, so third party library handling is also\n illustrated:\n\n```coffeescript\n# Gruntfile.coffee\n  coffee_build:\n      options: # options shared across all targets:\n        # When building to a file, it is necessary to specify a main file which\n        # will export the package public API, just like one normally does in a\n        # package.json file. If this is not provided it will be extracted\n        # from the package.json file\n        main: 'src/index.js'\n        # Source files to include. For single-file builds this should not be\n        # necessary, as the task will recursively add files required by\n        # the main file.\n        src: 'src/**/*.coffee'\n        # This package exports a constructor function(aliased to Vm), but\n        # its possible to provide additional aliases \n        globalAliases: ['Vm']\n        # If provided, 'moduleId' will be used define in amd environments\n        moduleId: 'vm.js'\n      browser:\n        # This target will build everything to a single umd module. It is\n        # meant for javascript environments without a module loader like\n        # web browsers, but it should also work in commonjs or amd\n        # environments.\n        options:\n          # If the project depends on libraries not available in npm it is\n          # possible to bundle it with the 'include' option.\n          #\n          # For example, to include angular.js the following may be used:\n          # include: [\n          #   {path: './vendor/angular/angular.js', alias: 'angular'}\n          # ]\n          # then require('angular') will work.\n          #\n          # For libraries that export directly to the browser global object,\n          # require('{global property}') will work. For example, if jquery\n          # was loaded from another file then require('jQuery') or\n          # require('$') would work. Its also possible to provide an alias\n          # that will work with require.\n          # Eg:\n          # include: [\n          #   {path: './vendor/old_lib.js', exported: 'GLOBAL_PROPERTY',\n          #    alias:'old-lib'}\n          # ]\n          # then require('old-lib') will resolve to object exported to\n          # to the global object.\n          #\n          # The 'include' option should work regardless of browserify but\n          # ignore/external options will be passed directly to browserify\n          # (both are ignored if browserify is false) \n          #\n          # In this example the only dependency is 'esprima' which will\n          # be bundled automatically as the browser version is available\n          # through npm and browserify is enabled by default.\n          dest: 'build/browser/vm.js'\n      browser_test:\n        # This target will bundle the code plus automated tests into\n        # a single js file. No need to add the files in the 'src' directory\n        # since the tests will require the source files\n        options:\n          src: 'test/**/*.coffee'\n          dest: 'build/browser/test.js'\n      nodejs:\n        # While the browser target could also be reused on node.js, \n        # it is better to have a node.js-specific target(with a directory\n        # 'dest') for the following reasons:\n        #   - Node.js already provides a commonjs runtime, so theres no\n        #     need to concatenate the files together.\n        #   - Only modified files will need to be recompiled since each\n        #     compiled file is cached individually on disk with a modification\n        #     timestamp. When building to a single file the processed\n        #     output will only be cached in memory, so it only works\n        #     effectively when the 'grunt-contrib-watch' task is being used\n        #     with the 'nospawn' option set.\n        #   - When building to a single file the task will perform\n        #     additional tasks such as parsing 'require' calls recursively.\n        #   - It integrates better with browserify(only the 'top-level'\n        #     project should invoke browserify)\n        options:\n          browserify: false # This is not required as directory builds\n                            # work exactly like normal coffeescript\n                            # compilation(javascript files are just copied).\n          src: ['src/**/*.coffee', 'test/**/*.coffee']\n          # If the destination doesnt end with '.js' it will be considered\n          # a directory build and files will be compiled/copied individually\n          dest: 'build/nodejs'\n```\n\n### Comments\n\nThe main reason I wrote this task is because I couldn't get any existing grunt\ntask to do what I wanted: Provide me with a single javascript file/source map\nthat maps(correctly) to the original source files and that lets me easily\nintegrate javascript/coffeescript with automatic dependency resolution, while\nletting me handle platform-specific particularities without having to write\nruntime hacks or verbose configuration.\n\nThe combined source maps generated by this task work flawless(at least in my\n tests).\nDebugging with\n[node-inspector](https://github.com/node-inspector/node-inspector)(0.3.2) or\ngoogle chrome should just work.\n\nThis intends to provide a one-stop solution for building commonjs \nprojects for web browsers or node.js using coffeescript and/or javascript.\nEnjoy!\n","readmeFilename":"README.md","_id":"grunt-coffee-build@1.4.12","dist":{"shasum":"03ec9d0ea9cbab61de0e4270125ef82baaeefbbd","tarball":"https://registry.npmjs.org/grunt-coffee-build/-/grunt-coffee-build-1.4.12.tgz","integrity":"sha512-sJRLklgc/fRKMPbrIj3lodkm8B5obBR15DoDsCI7UQhAmAAZ9i91v3igDccn3CS0w3JIAyWh2oGQXvOR5NMtTA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICDpVpnc/zefjxGXRiszrbJolqodQnoghhzeQm1CvcNOAiAc31mO6LH1ro1CCk3jUifYXPEDkBwscepMrDtcTNN1cg=="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"tarruda","email":"tpadilha84@gmail.com"},"maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}]}},"readme":"# grunt-coffee-build\n\n> Compiles Coffeescript files, optionally merging and generating source maps.\n\n## Getting Started\nThis plugin requires Grunt `~0.4.1`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install grunt-coffee-build --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-coffee-build');\n```\n\n### Usage Examples\n\n```coffeescript\ngrunt.initConfig\n  clean:\n    tests: ['build']\n\n  coffee_build:\n    options:\n      wrap: true\n      sourceMap: true\n      disableModuleWrap: ['index.coffee']\n    file:\n      cwd: 'test'\n      src: '**/*.coffee'\n      dest: 'build/build.js'\n    directory:\n      ext: '.js'\n      expand: true\n      flatten: false\n      cwd: 'test'\n      src: '**/*.coffee'\n      dest: './build/all'\n```\n\nWhen passing a filename to 'dest', the task will merge all files, parsing\n'require' calls to take dependency order into consideration. It will also\nreplace require calls with automatically generated identifiers representing the\nmodules(using the file path) so it can be used without commonjs.\n\nSince when combining every file is wrapped, the disableModuleWrap option can be\nused to override this behavior for certain files.\n\nWhen passing a directory to 'dest', it will compile each source file\nindividually.\n","maintainers":[{"name":"tarruda","email":"tpadilha84@gmail.com"}],"time":{"modified":"2022-06-18T14:39:09.151Z","created":"2013-08-09T21:37:12.175Z","0.0.1":"2013-08-09T21:37:17.362Z","0.0.2":"2013-08-10T03:02:30.104Z","0.0.3":"2013-08-10T03:06:48.226Z","0.0.4":"2013-08-10T04:20:42.271Z","0.0.5":"2013-08-10T11:52:46.436Z","0.0.6":"2013-08-10T12:40:42.930Z","0.0.7":"2013-09-03T16:49:00.347Z","0.0.8":"2013-09-08T13:13:04.824Z","1.0.1":"2013-09-09T15:48:27.798Z","1.1.1":"2013-09-09T18:03:00.564Z","1.2.1":"2013-09-09T18:31:51.150Z","1.3.1":"2013-09-09T22:40:22.065Z","1.4.1":"2013-09-10T15:43:55.960Z","1.4.2":"2013-09-10T16:49:07.192Z","1.4.3":"2013-09-10T16:56:23.962Z","1.4.4":"2013-09-10T17:03:46.655Z","1.4.5":"2013-09-10T19:10:13.020Z","1.4.6":"2013-09-13T19:48:19.179Z","1.4.7":"2013-09-17T12:55:01.101Z","1.4.8":"2013-09-17T13:12:17.400Z","1.4.9":"2013-09-18T00:20:15.824Z","1.4.11":"2013-09-25T13:47:51.338Z","1.4.12":"2013-09-25T17:43:12.541Z"},"author":{"name":"Thiago de Arruda","email":"tpadilha84@gmail.com"},"repository":{"type":"git","url":"git://github.com/tarruda/grunt-coffee-build.git"}}