{"_id":"glint","_rev":"30-0d176eef87342995af56b90b222cf77e","name":"glint","dist-tags":{"latest":"0.0.25"},"versions":{"0.0.1":{"name":"glint","version":"0.0.1","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.1","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"c342bb3db487244cc00674364b5167f79cfb5cbc","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.1.tgz","integrity":"sha512-HmZhfAwaCID5scbmUAzhi3sYv00FL7rVHBIbP+2iG9FvTTeyUGCf0DOwEU1fMbFSGxaIjjBk1+Lw5lZyhHnZCA==","signatures":[{"sig":"MEQCIGS/nxxjMR/phaHY5T6Onad3Y6B820d0eW2fQUGDL/sIAiBR0PrRZS/qEtS5RQHMG8/k1QMnX6p4XMl6yr8p5T9SDQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n###Run Glint\n```javascript\n./node_modules/.bin/glint --config path/to/config/file.js\n```\nThis will create your packages, preprocess and postprocess them, save them to output directories and create manifest.json file.\nNow you have your packages ready to use. You just have to use them in your application\n\n###Using packages with express.js\n```javascript\n// file clientlibs/config.js\nmodule.exports = {\n    assetsDir: 'assets',\n    outputDir: 'output',\n    manifest: 'output/manifest.json',\n    packages: [\n        {\n            name: 'gallery',\n            final: true,\n            files: [\n                'gallery.css',\n                'jquery.js',\n                'gallery.js'\n            ]\n        }\n    ]\n};\n\n```\n\n```javascript\n// file server.js\n\nvar express = require('express');\n\n// import glint adapter for express\nvar glintForExpress = require('glint').adapters.express;\n\nvar app = express();\n// add glint to express application\napp.use(glintForExpress('output/mainfest.json'));\n\napp.get('/', function (req, res) {\n    // now you have assets variable in res.locals\n    // you can access final packages via package_name.files_category\n    var body = '<html><head>' + res.locals.assets.gallery.css + '</head><body>' + res.locals.assets.gallery.js + '</body></html>';\n    res.setHeader('Content-Type', 'text/html');\n    res.setHeader('Content-Length', body.length);\n    res.end(body);\n});\n\napp.listen(3000);\nconsole.log('Listening on port 3000');\n```\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.11":{"name":"glint","version":"0.0.11","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.11","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"308bb0ad182ee4327a1dfbfdbac9fb6c6b90ac36","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.11.tgz","integrity":"sha512-soHvYmV0+PAPkWzEhhdlUZyEqoDWLpWS0hsqMZWiqYK+EjtL8U7wc3q6VBTkUlmmu7hdtrAwN3FI6ibM8fvOeQ==","signatures":[{"sig":"MEQCIBZrLmba5RtQX9UmIIx2yBQCthWFsUNTqtEOabSNLgIBAiB1nOfTsiMuuqV5vL/fcBOn/BBMAGywBNI1bJmU+rSAmw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.12":{"name":"glint","version":"0.0.12","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.12","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"b5ac3c1bf662f8f91e2fc1238a0021408a5672f1","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.12.tgz","integrity":"sha512-uLXBulPK7JLMmJ2ieDk1oAexK/yuqcNQj39sM3EAa8CAXX6yi1IfzSz8N4vGsX9WqpsEPWx9VfzIkgCnqW8Rsw==","signatures":[{"sig":"MEUCIQDf2cKVrTN8vry8r54de93/l0XBs2I4ZmTlnrxbwO+p9QIgchO3EDZR9MhhImrBTJ0SEmwGmiMKOhbOHcPElL/VbbA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.13":{"name":"glint","version":"0.0.13","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.13","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"98ea72e77652c3ac16d95efa4848fdc1b9f96b2b","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.13.tgz","integrity":"sha512-PIvlGzVMzZhPpclJf8mfX8vt16JaEg69vw8naigwpg7AnaHn3XrgqC1BLt8KZ3t7xr7/Ro+1mV19qqBg0AoJtg==","signatures":[{"sig":"MEUCIQDcfwPJH0scX3eprsEG9/9wXD9+OqSa2+4PWRfi7q1Q2QIgeDH3/zfYp3GUJCszwuyXpkXGsz0nhKsLSyyUM5yNrIM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.20":{"name":"glint","version":"0.0.20","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.20","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"23db72bbef92150e07c8e2c604e00c7e8d57902a","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.20.tgz","integrity":"sha512-WpDyrnefyQIoYPhJ7V1Ki3hh97MA0lLnk/FiXDJPJzct0LM77F0ByBpOGOJntVAbqfNgQ2efE1fPNbbm72Zf3w==","signatures":[{"sig":"MEUCIQDqfIOnWcB4WnRG+Oz8CkL3w/yr7v0p3hn/ZhMlAoRsVQIgBt5NPkX7sYKZJPrOMNeNmaUn7P9T7MLeLp8qmzuoTY8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.21":{"name":"glint","version":"0.0.21","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.21","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"3c828f176c52d40b672d01a813194875a0aef5e6","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.21.tgz","integrity":"sha512-0N9bo50l47HAlDXiew51DaOw6C4elMe/JpkxgyzlDqZT+6WaOZ9QmC+8ZFBQFxKbMk3LKB0E1luQ17WEhiNQIg==","signatures":[{"sig":"MEUCIBB7GICcqidwm4zJ1Gl0KCvHGFazACEyi7oiWXa8500EAiEA1x0aYztlko8PpSjYzkzBSZ1nGRUS6XsvUNBlwyYFBBk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.22":{"name":"glint","version":"0.0.22","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.22","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"ff48b51303826064c08bafeeb67c35cb4866bef5","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.22.tgz","integrity":"sha512-QYRU2YY4DWE+DUOXQUGsDGcZimo/c5k7EjyJlVNtNr3tNY7lqw0++5/qGOO+yb+nZV+1OAPIkxKP6oOrb4PpjA==","signatures":[{"sig":"MEQCIC8f9U/gYUoClhkENYsmdm4gXhk5SsIPnKO/fDYOd3lUAiAu97e7mLm+pZ3QjpHErMJ9e8reOBH9+Ggjrkm+SEWVsw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\n#####For now jade, stylus and scss are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.4.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.23":{"name":"glint","version":"0.0.23","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.23","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"147bde5d511719db2496dd66d148d452b9d86fca","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.23.tgz","integrity":"sha512-Mz0iiEV/2G6OqaJDDwznzzWJ/Bbd+5rzPh1vJD8rUFEGtOzFYwDWKiYQ60U8dz+p0F7acKjlivROu0KVJWK8IQ==","signatures":[{"sig":"MEUCIQDuS0Yn4N50GX+CUeSQyabhPuYSXjPRyxF4cOoWHK4yQQIgXcwJOCxaQ9AtBnY1CN3nXQongXBzmhWSbkiEi/EF0Uk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"_from":".","readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\n#####For now jade, stylus and scss are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.10.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.2.18","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"readmeFilename":"README.md","devDependencies":{"chai":"*","mocha":"*"}},"0.0.24":{"name":"glint","version":"0.0.24","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.24","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"01d653b4d60ed82f1242c828a278ebad13ac78a9","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.24.tgz","integrity":"sha512-48CsK/bOyBT0dSgcrO8D0QeD0Vnry6sMJxQ9VY18cc2pwqpqVBBa4NvhNkL6tcJOFmTDihiHLmaq5iXsUoC0XA==","signatures":[{"sig":"MEUCIQDPY7TxI6IrDfx2HJGRt49DouCWbDU/JdwPSoaLltFWWgIgKbx7SCXYl3i2abd2cDv2ohcxAgsIraQwfn50LI+XqVM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\n#####For now jade, stylus and scss are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n```\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.10.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}},"0.0.25":{"name":"glint","version":"0.0.25","keywords":["packer","build","compress","glint","assets"],"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"_id":"glint@0.0.25","maintainers":[{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"}],"bin":{"glint":"./bin/glint"},"dist":{"shasum":"fe74ccc1c14c9edfa9c79b50cf9083b2b704eb10","tarball":"https://registry.npmjs.org/glint/-/glint-0.0.25.tgz","integrity":"sha512-gCcGGTlZTzVff7nZLFDd4zkhXTULAJ9/EQgTGvq7LeZareEm0jQhCTHNVYAuKsK3U3A2+NYg9DY4xYFwuZEzbQ==","signatures":[{"sig":"MEUCID+ZQbSg9vRspj11U07OJ9y0efl0WauPR3qc94RXLhPVAiEAs99onmwjdysEkKE0aSto8mnVKUscDxiYVBscWgtzYLQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}]},"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nCheckout examples [here](https://github.com/mateuszwozniak/glint-examples/)\n\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\n#####For now jade, stylus and scss are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n\n##Glint options\nYou can pass following options to glint\n- `-c, --config path/to/config/file.js` - specify configuration file\n- `-w, --watch` - watch for changes in files and rebuild suitable packages immediately after change\n- `-d, --dev` - use development mode - don't merge files, only preprocess them and copy to output/sources location.\n\n\n##What exactly glint does\nWhen you run glint a several things happen:\n\n1. glint collects files for packages, and builds files lists for final packages\n2. for all files glint runs preprocessors to create desired file content\n3. for all final packages glint merges files\n4. for all final packages glint runs postprocessors\n5. all files from final packages are written to following directories\n\n```javascript\n--output // <- directory you passed as outputDir in configuration file\n |\n |--build // directory that holds build (preprocessed, merged and postprocessed files)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n |\n |--sources // directory that holds preprocessed files (not merged, for development usage)\n | |--css // css files and files that were preprocessed to css files (e.g. stylus files)\n | |--js  // js files and files that were preprocessed to js files (e.g. jade)\n\n```\n\n####! This documentation is not complete so if you need any help don't hesitate to contact me (mail is inside package.json) !\n\nTBC...\n","engines":{"node":">= 0.10.0"},"scripts":{"test":"./node_modules/.bin/mocha --timeout 5000 --reporter spec test/*.js test/unit/*.js test/e2e/*.js"},"_npmUser":{"name":"mateuszwozniak","email":"kontakt@mateuszwozniak.pl"},"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"_npmVersion":"1.1.63","description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","directories":{},"dependencies":{"nib":"0.9.x","jade":"0.28.x","async":"0.2.6","stylus":"0.29.x","fs-extra":"0.5.x","clean-css":"0.10.x","commander":"1.1.x","fs.notify":"0.0.x","node-sass":"0.4.3","uglify-js":"2.2.x"},"devDependencies":{"chai":"*","mocha":"*"}}},"time":{"created":"2013-04-24T21:17:46.578Z","modified":"2025-04-11T13:00:25.724Z","0.0.1":"2013-04-24T21:17:49.758Z","0.0.11":"2013-04-25T09:46:11.876Z","0.0.12":"2013-04-25T13:06:56.617Z","0.0.13":"2013-04-25T13:21:31.246Z","0.0.20":"2013-04-25T20:43:18.027Z","0.0.21":"2013-04-25T20:48:12.774Z","0.0.22":"2013-04-26T08:25:59.088Z","0.0.23":"2013-04-26T09:31:22.857Z","0.0.24":"2013-04-26T10:58:53.077Z","0.0.25":"2013-04-30T14:54:34.133Z"},"author":{"name":"Mateusz Wozniak","email":"mateusz@wozniak.io"},"keywords":["packer","build","compress","glint","assets"],"repository":{"url":"git://github.com/mateuszwozniak/glint.git","type":"git"},"description":"Glint is an asset (css, js, whatever-you-need) management that helps you organize and manage your client side files","maintainers":[{"email":"kontakt@mateuszwozniak.pl","name":"mateuszwozniak"},{"email":"npm@joshuakgoldberg.com","name":"joshuakgoldberg"},{"email":"theprecognition+npm@gmail.com","name":"nullvoxpopuli"}],"readme":"#Glint\nGlint is an asset (css, js, whatever-you-need) management tool for your project.\nIt helps you better organize files you serve to browser, as well as process them with any processor you need, even with your own one.\n\nFor now it works with express.js but you can simply adjust it to your project and technology.\n\n##Features:\n- creating named 'packages' from your assets (e.g. jquery-ui, my-tools, etc.)\n- merging, processing, compressing files for production environment\n- generating separate files for development process\n- watching for changes and rebuilding suitable packages\n- switching between merged, compressed files and separate files with query parameter (in express.js)\n- support for jade and stylus (more in progress)\n\n##How it works:\n1. Create config file with packages (or simply files) you want to serve to your application\n2. Specify output directory in config\n3. Specify preprocessors (optional) and postprocessors (optional)\n4. Run glint\n5. Inject created packages to your project.\n\n##How to do that:\n###Installation\n```javascript\nnpm install glint\n```\n###Creating config file\n```javascript\n\nmodule.exports = {\n    /** directory with files you want to use in your project (relative path to this file) */\n    assetsDir: 'assets',\n    /** directory where processed files will be saved (relative path to this file) */\n    outputDir: 'output',\n    /** path to file with information about generated packages (relative path to this file) */\n    manifest: 'output/manifest.json',\n    /** preprocessors you want to use (explained below) */\n    preprocessors: {},\n    /** postprocessors you want to use (explained below) */\n    postprocessors: {},\n\n    /** definitions with your packages */\n    packages: [\n        {\n            /** package name - you can use it as requirement for another package */\n            name: 'core',\n            /** generate output file for this package - only packages with final set to true will be saved to output directory\n                this gives you possibility to create a bunch of small, reusable packages which will be included in final packages */\n            final: false,\n            /* list of files for this package - files paths are relative to directory passed as 'assetsDir', so in this case\n               we are using files: assets/file1.js, assets/file2.js */\n            files: [\n                'file1.js',\n                'file2.js'\n            ]\n        },\n        {\n            name: 'gallery',\n            final: true,\n            /** list of required packages - files from packages listed here will be included before files from this package */\n            require: ['templates'],\n            files: [\n                'gallery.js',\n                'gallery.css'\n            ]\n        },\n        {\n            name: 'templates',\n            final: false,\n            files: [\n                'template.jade',\n                'styles.styl'\n            ]\n        }\n    ]\n};\n```\n\n###Preprocessors\nPreprocessors are functions that will receive raw content of your files, and will generate from this content final file content (e.g. generate css files from stylus files).\nFor now jade and stylus are supported.\nDefinition looks like this:\n```javascript\nvar preprocessors = require('glint').preprocessors;\nvar stylus = preprocessors.stylus;\nvar jade = preprocessors.jade;\n\nmodule.exports = {\n    ...\n    preprocessors: {\n        /** for files with extensions 'styl' use stylus */\n        styl: stylus,\n\n        /** for files with extensions 'jade' use jade\n            you can also pass object with preprocessor as fn and options for this preprocessor */\n        jade: {\n            fn: jade,\n            options: {\n                pretty: true\n            }\n        }\n    },\n    ...\n};\n\n```\nFor now you can use only one preprocessor per file extension.\n\n###Postprocessors\nPostprocessors are functions that will receive content of your merged packages, and will generate from this content final package content (e.g. uglify/compress merged package)\nDefinition looks like this:\n```javascript\nvar postprocessors = require('glint').postprocessors;\nvar cleanCss = postprocessors['clean-css'];\nvar uglifyJs = postprocessors['uglify-js'];\n\nmodule.exports = {\n    ...\n    postprocessors: {\n        /** for css files use clean-css */\n        css: [cleanCss],\n        /** for js files use uglify-js - you can also pass options here */\n        js: [{\n            fn: uglifyJs,\n            options: {\n                unsafe: true\n            }\n        }]\n    },\n    ...\n};\n\n\n```\n\n###Run Glint\n```javascript\n./node_modules/.bin/glint --config path/to/config/file.js\n```\nThis will create your packages, preprocess and postprocess them, save them to output directories and create manifest.json file.\nNow you have your packages ready to use. You just have to use them in your application\n\n###Using packages with express.js\n```javascript\n// file clientlibs/config.js\nmodule.exports = {\n    assetsDir: 'assets',\n    outputDir: 'output',\n    manifest: 'output/manifest.json',\n    packages: [\n        {\n            name: 'gallery',\n            final: true,\n            files: [\n                'gallery.css',\n                'jquery.js',\n                'gallery.js'\n            ]\n        }\n    ]\n};\n\n```\n\n```javascript\n// file server.js\n\nvar express = require('express');\n\n// import glint adapter for express\nvar glintForExpress = require('glint').adapters.express;\n\nvar app = express();\n// add glint to express application\napp.use(glintForExpress('output/mainfest.json'));\n\napp.get('/', function (req, res) {\n    // now you have assets variable in res.locals\n    // you can access final packages via package_name.files_category\n    var body = '<html><head>' + res.locals.assets.gallery.css + '</head><body>' + res.locals.assets.gallery.js + '</body></html>';\n    res.setHeader('Content-Type', 'text/html');\n    res.setHeader('Content-Length', body.length);\n    res.end(body);\n});\n\napp.listen(3000);\nconsole.log('Listening on port 3000');\n```\n\nTBC...\n"}