{"_id":"frontfax","_rev":"121-a120dc196baa0ecdf2daaaa1be5d983a","name":"frontfax","description":"Development environment for frontend developers at Fairfax Media.","dist-tags":{"latest":"0.2.1"},"versions":{"0.0.1":{"name":"frontfax","version":"0.0.1","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","coffee-script":"1.4.0","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","http-proxy":"0.8.7","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"readme":"Frontfax\n=======\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax` (TODO: It hasn't been released to NPM yet.\n3. Create a project `frontfax project:new myproject`\n4. Install the dependencies `cd myproject && npm i`\n5. Start the server `npm start`\n6. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.1","dist":{"shasum":"1acbf05c8c4e42f7b05b018dc344836180cc0981","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.1.tgz","integrity":"sha512-V5xTauLOe9i687iD4RPvKze8POsCNYnrZbwqA4yehN8rTJEZDbDOT1f1/QTIYo91fs177pMGJ/te1cjmbZOVfA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHlipUAtKrF31coLUQJt0HevO3SAFw2Ukcm4iv/Ea2nHAiEAmlpcQEAAicEFy4qHhX8BrhMuKYolK2gOMieLaW25+3A="}]},"_npmVersion":"1.1.71","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.2":{"name":"frontfax","version":"0.0.2","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","http-proxy":"0.8.7","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n=======\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n3. Create a project `frontfax project:new myproject`\n4. Install the dependencies `cd myproject && npm i`\n5. Start the server `npm start`\n6. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.2","dist":{"shasum":"f7fe0e17f89cbc5ec9ac579835a35e347e4be208","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.2.tgz","integrity":"sha512-9/syl78pc+ORy46QHqa9ReUe8ngtTGfJeSXJ+GpOZD3HLE67o57Kekl8hIQT9tC+bn7QgEog5424OxTf7QgEBQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC6saPqUKPOxfUrdXMsnOl826eEZD1QXbonw8aftVzdFAIhAK4Dsz/bHiqVTl3pKvUTbq7bSwZN1IQYMesjfC5kdAIo"}]},"_npmVersion":"1.1.71","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.3":{"name":"frontfax","version":"0.0.3","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","http-proxy":"0.8.7","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.3","dist":{"shasum":"50094e1a773428d15e3a3ac1f86af1364b30c3b2","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.3.tgz","integrity":"sha512-ffXWz07wJtropCZByFLT4sJ5Qghe4Os8Ia0eGWdA1VuW0us0hb7o5TxTVcRFGyd/vScHZ3pw+uJXD6xiBrmduQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCMAhrYy56j6v+yegiTnnbR/JFBjFvc/YPw/dK2CLFrDwIhAKxOg+JOi2Io3Ku1w3EFjp0BH6G0HRJBR2fEAIVFZZsj"}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.4":{"name":"frontfax","version":"0.0.4","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","http-proxy":"0.8.7","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.4","dist":{"shasum":"70112179102ebf9806f05ef706b2f4c33b5a3e07","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.4.tgz","integrity":"sha512-EUTk8jgOCJShns412q0UJSxkWXLmbmxZ7zgg9QScCmcbRFDy1NFasWC6+n1UVPxFmEBqfCpwk93tzphN3H+M+w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDOxyXD6DRSyRXnrNsL8/stwMMoIYJsM9c8WwyV/DhLGwIgSndDdq2tjBPsfywjnlM3f3XWi8yNOWC4/xbfGhkU61s="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.5":{"name":"frontfax","version":"0.0.5","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.5","dist":{"shasum":"e3fdf7627e82469cc84c15595e747e0c9e61ad83","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.5.tgz","integrity":"sha512-IlkiKL/yatN4aBcoMGUL/LglhSV5n/3BeVOSczHStt+z+orN/wIrqSwoJxVvXhedOqk6SBIG3qa8rRZHdMtEoQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHFln1Kt8ovHkkKxGOy5kaeP2p90pVkkOJm0MpRQL7tGAiAvVwXUVztaqRbrV4kEZZtm/ZNvsvrFuhZ3VQlKaRVNew=="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.6":{"name":"frontfax","version":"0.0.6","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.6","dist":{"shasum":"3423eba20f333f6862d4a52c0465d2c976cff5b9","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.6.tgz","integrity":"sha512-5on5b3egWXvgEvn1PoappxaqPq1EXRuuXdq8Umixvn2qHZoCpCYQAxQAOofgSvhXEEdVYiC5w3/giM/1TCdPfg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAEtxu6x1WldmR53qek5KF+qAwZtqw9QWDNFF9+L5DHbAiEAheMQS23KgJ0Q7Nr5MOHDVLaG8ECzzf8L3jeyK5zgYe8="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.7":{"name":"frontfax","version":"0.0.7","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax project:new myproject`\n2. Install the dependencies `cd myproject && npm i`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.7","dist":{"shasum":"399fe4ffe58561833aa3518fe66703259bbf5eb4","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.7.tgz","integrity":"sha512-DDwrNQCQLn+HN4V2rDUaJ9UGs3kbk3SacE0VqWMa1S+u9CG2fM2L3/ugcRr+hHxvBSkfROcquZJUs3UU1FXuNQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDC4+twZ7yA2bK/qjnGDiYSfz3qX0msmBF/Xr5aReIqoAiBqRGLovrFZgJiXWWDz0PUld0TAuaHfTK2PjIE9E+NY8g=="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.8":{"name":"frontfax","version":"0.0.8","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax project:new myproject`\n2. Install the dependencies `cd myproject && npm i`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.8","dist":{"shasum":"e25a0b423082a4d248f551edeffd15bdadfb711b","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.8.tgz","integrity":"sha512-kNl/UxWzxS4bwhFYegVEGYAx7IG3yddNhRU0syPUILsxgjhBCy0BkE0xKGoel271pkX+aEQ6xrvhcW0+chLL7g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIH0ZCbl1blkfQprQCkOjjV6ZfHHiYB34+2cJTz2LEyABAiEApQPvLSfqhycAUwBTC4sVJrFjI0gUsCW+4X54TTDtpPo="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.10":{"name":"frontfax","version":"0.0.10","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax project:new myproject`\n2. Install the dependencies `cd myproject && npm i`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.10","dist":{"shasum":"59bc23286dbfd37007db98b34b41ca43a18ee6ab","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.10.tgz","integrity":"sha512-UBTEQZakYLTpSsH+ZQszH3SXZvsEHwrWDFDlib6TRVcHDVNpT4ENKpH3zPXneqcVcdXekX6KPMFKWXsVb51v8g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCQf/tG33He0L64DF+lrduKau2g+DFnDMXEOi6EWTTmkAIgatpy5CVqgQWzqi3XnWNHxwNpEDxnHQ2IMZMN1GKlwdQ="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.11":{"name":"frontfax","version":"0.0.11","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"build/bin/frontfax.js"},"scripts":{"prepublish":"cake build"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.11","dist":{"shasum":"0b05dc606fa31db3501ef4c2ab682d2d2b5e7d97","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.11.tgz","integrity":"sha512-TlJ23UnGYpl00UVfDBN5KD3P8sJ5Qy3bvUVDsada1+ltEiZUlNYNEaDvNIDDoqdZIVM6IX9iFGZYNcqUE1u0Fw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBcqwN58A/XlPYP6Plaa/FkhqAegI9U1Sz15gaDI44i8AiEA1OL9Tc6iiDb+N9AjJnyn4hXvguEobZaMbyX5Dnj24mY="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.12":{"name":"frontfax","version":"0.0.12","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.12","dist":{"shasum":"02b16b4ff3b11205c01a412afdbb210f15b59079","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.12.tgz","integrity":"sha512-tZmv7/ihmVpKu9MqhZ8N7EJSVpzyMkjCDxeyTEMD5/IRn8TBOOtPQj3FwR/POM+DaeqDVoFi1Bvh/2GmAR3BlA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFp8goVDGCc7+lIARL7iS0srhuZuvJGZXTSgDPHUVjTrAiA/H4MbLAXZuNzJAc1V8P/XQvjWDPbES2csvHdtZOfD2A=="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.13":{"name":"frontfax","version":"0.0.13","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax project:new myproject`\n2. Install the dependencies `cd myproject && npm i`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.13","dist":{"shasum":"1dc514ca7459da2d022f47da5771c3413f8915fb","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.13.tgz","integrity":"sha512-0YEbwN0nWzCPLlvACk41Pda9kp9JQGy8sHO0TNF2XS9ww/tKgYVt/kdaoA4Y3KRcbk6qEr3zKmHDYYdENV9JEw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDj/85NMBXVM6Hl2bgowaj95lRJA0+I45+Olxh4c9FqAQIgDWJ/UWZ/AdKhGgpzW+ky+KA6eubw2IM2qywBl3v4fLY="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.14":{"name":"frontfax","version":"0.0.14","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax project:new myproject`\n2. Install the dependencies `cd myproject && npm i`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.0.14","dist":{"shasum":"55928a28777aa16f67f1499ad58900191c19cf50","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.14.tgz","integrity":"sha512-LggV9/upd/4phVowvVjtnZOEReVuX3mXCoTh72t6IXSj3HNLo5COIippr2VU993sGvKcvM/dVQdKfBgpQMZpYw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCJWJFYEVB9LOhv6/5+NJoSoSyhq5f4a7ozzyKReYGOBgIhAJpLS71VEVdov/COsj8jU7Vp8bZMnPD7+qkd5TUYGvn/"}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.15":{"name":"frontfax","version":"0.0.15","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","highlight.js":"7.3.0","less":"1.3.3","marked":"0.2.7","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","stalker":"0.0.20","uglify-js":"2.2.3","walk":"2.2.1","jade":"~0.28.1"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.15","dist":{"shasum":"9b2b783dfcfdbca05faebde12f14ef4c724b63be","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.15.tgz","integrity":"sha512-0PLveLVmZrcKiDpaVJgDcsBnjcWjNIaTxtd7BlPRnX6foJ2YnmQiBG+PaOFeiZ4v+jv3RdiVi/URYJpaIQB0mQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCfxtw/Nj7wk82vtkq6Cej0XGi0SCCO/JdCOXP9OY6sRQIgBV6W6PIE5lONO8hJlvWoPuR/XQp7JhVUhzX36qGAbc0="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.16":{"name":"frontfax","version":"0.0.16","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","grunt":"~0.3.17","grunt-contrib-uglify":"~0.1.0","grunt-contrib-less":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.16","dist":{"shasum":"d973abff567123fc9d7e6754028054105954a9d2","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.16.tgz","integrity":"sha512-GnAH4jBd411rQqlGAZW05sejkFrxnlnTt6t3mnzRFEKBX/GCwO1B+oc0+6DXh6WB+W6NT8Py87y0+yDlK1DHMw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDRbTVZGfgvQaXZwI1B5cWukxzLCdRWCbFS+X/UTdFvQQIgFwb/4xEBamRMhPthG2sxy5CVUi5rS8VqWaYZjdLRcFk="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.18":{"name":"frontfax","version":"0.0.18","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","grunt":"~0.3.17","grunt-contrib-uglify":"~0.1.0","grunt-contrib-less":"~0.3.2","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.18","dist":{"shasum":"efacf2809888867c2c8284c8226d6a7f192210f5","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.18.tgz","integrity":"sha512-SSfIBjz+jlj5AacHYz2ixClCBwF/UXZKXiqyB51hrXPA925gXOPve3BIF4qDMa+lHyP4P/7oKN7modUmP4Dwrw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDR8sigU4FNBKtt2eza9cdNe5aoYfUPB9ohb2Fj1gwUVQIgXz2jbKc1LF9NKxGfv8BSb4w6hSKyrdWtA726oVjA3j4="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.19":{"name":"frontfax","version":"0.0.19","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","grunt":"~0.3.17","grunt-contrib-uglify":"~0.1.0","grunt-contrib-less":"~0.3.2","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax project:new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.19","dist":{"shasum":"561e4ed2587415d2bd9b94f0dfe2fbf4f437d551","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.19.tgz","integrity":"sha512-n94HT4Cf/7WdJFzoG/ZOKUWGU6SeNGMtHZnLfqkWRsUrv442QqpB4Ro5SF+65/aD7UaNZXcRDvJhXeiMtABhPw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFioJ5LeRM9on80kudlfdbZX3yBz7ZnDOKc413+FN3n7AiEAqlMimNj5jRpEsuwLXm2IXTw2VObUTWNCK6GFV/9USRk="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.20":{"name":"frontfax","version":"0.0.20","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","grunt":"~0.3.17","grunt-contrib-uglify":"~0.1.0","grunt-contrib-less":"~0.3.2","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.20","dist":{"shasum":"cf0891b907c5e2a1cf9c714d501d38a80ee0848e","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.20.tgz","integrity":"sha512-4xvb2+hqHhCOgcBYuhluZMS5eqC8kFw8yYYWKATo+9MaLrhRsyxS9jAb/CONr+S/4UBIXuec5GFRDjHyIai4EQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC3LqmM3JQldyMMwZf3wautZR3OgbLdNN7oeiuknfz/bgIgAoah0ilDJA5u7PNZ5ehRutVOvL3xMHwMD185u5Xos6A="}]},"_from":".","_npmVersion":"1.2.2","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.21":{"name":"frontfax","version":"0.0.21","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","grunt":"~0.3.17","grunt-contrib-uglify":"~0.1.0","grunt-contrib-less":"~0.3.2","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.21","dist":{"shasum":"6b3d5d17f2268dea4e5f0207d0af28ffe9c25903","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.21.tgz","integrity":"sha512-4aLb39uDyrQvxrc7EiBNZa/+Tm77613Q8n3iWDnDkJMHmmODQMeo5bUQvYefor1xg9xnlflPJZHP/WS2HNbWww==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEmkdrzEYk4KMMS3AWcgIW1cbEiO8dIlrckfxaoI6OgOAiBjz8fd5TEHetpQDB9fJk1OGkzH4C03GbBf9G/n2IqohQ=="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.22":{"name":"frontfax","version":"0.0.22","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","jade":"~0.28.1","coffeecup":"~0.3.19","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.22","dist":{"shasum":"919b4423404b9b12f9bb281d7f417a33b831cfe1","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.22.tgz","integrity":"sha512-NQHjpsuCdbXaRwwKX/tmad0FMhpBY/mCeuouBKO6ybavCmbebi4b1vRZ+qFH2agb0+wxwTPPiLeMdIBPXUrzNQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCmcINHcFngnJRF7Nq5a6QWwYZjXAiQoaCSxCagJrXrQQIgfTTMk/nv92Pu79MRzEIFJjKG8OMNffbvy8M+Y1CcDxA="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.23":{"name":"frontfax","version":"0.0.23","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.23","dist":{"shasum":"f83457059952ed8165f746a8fd0c94f8866dc7d3","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.23.tgz","integrity":"sha512-uBikyO0lfvTcJULzDpZLMnomiavfeLHU79tJ89EYKXdY0u7Fi4+OPnOTxzI2AAbklUHSBT/o5olQq4Z5R1yJLw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBR/z1bESoy8kemg4e2ka2YwBCawI5xOpfmyJRsLlMkIAiEA1lWjFP8PQQU6/f+D1B6IYIpTB9F6brhVMEhtjei8ulY="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.24":{"name":"frontfax","version":"0.0.24","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.24","dist":{"shasum":"7e173c40abccf9b7c639e221d14dccf037b14edc","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.24.tgz","integrity":"sha512-7gW5Mke5fL5Jw4gJr7niTVNtzOgN08JcdqoZPd5a9y6h1aAqQBW0EOZ3dZw622YsFLsd75jSBThKUioFmP4Llw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCAkPAaTu/Mqf1LAMVDK5DjFvqcb2uh/LDx30UFS9nmfAIgeHPJvAloAsL14m/ojVrwSmMs7bUPGLxRxUzlyoOJbxk="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"directories":{}},"0.0.25":{"name":"frontfax","version":"0.0.25","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Install the dependencies `cd myproject && npm i`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.25","dist":{"shasum":"fdf39dbba2a91cf543b49d3ea3eff0711d00584c","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.25.tgz","integrity":"sha512-2sE8eILVtNCOMic3e22wNPXlIPGUYaCtXtPWoHAhPjE1j3WIIBwTCg8cMZNoE1YgfeskOF/cQPiWtx2DAu4jqg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDIHp8PoXaYTvcbZJrNBqPeHMoVpfKVYs+PUkWrzdnw8wIgSVorwJ7hCLHML6yE5UUkQ63Vod1RGMIXQ5BY0rW96XE="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.26":{"name":"frontfax","version":"0.0.26","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.26","dist":{"shasum":"fd94c03c9572604255ff4d01326fc93a98000089","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.26.tgz","integrity":"sha512-AXOoHSY54INNCFWV8Cvw0yyV+uBHXBQipu5lYGcLFYJ0OKpK5Jb0/hMFQ+G4Ho4IZngPfgHyXIXjKhkUB4cjpw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHxqGGaYEg6pmkxnBVlkU6vCEeaGZ6det8zmU2uBMUcfAiEAlAh5oRc6nnHUfaHcQdTMjT9kyx08p1w3j0GyK3Ml2zU="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.27":{"name":"frontfax","version":"0.0.27","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax `[sudo] npm i -g frontfax`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.27","dist":{"shasum":"8eb04a10e657e9de3780e43e9cdd663b758ffda7","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.27.tgz","integrity":"sha512-tZnOPiVbcWQQBsyGP+k9CGNVy7w6eFijdjylDOwKortW5xnK+ctlyz4PpAot3HrLeSCmsvACEOhnrA3eI3NOIw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGkMHo+EcrUTfvYLxJov+AuWgVJKJQTbn6z6SiDGlfPkAiBF6NyA8VszwyjyKn5Ot/VovsYhjKdzMNYldxckvei6Ng=="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.28":{"name":"frontfax","version":"0.0.28","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.28","dist":{"shasum":"720bff5a09d535688d41b58e42453a6b15c2bd54","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.28.tgz","integrity":"sha512-BkwTIz4yQeIEIWCLgwR0/Em+fQIrkJ33Li5NkKpq96y9C+Sc48aOJfv2I1ibbWFcoCYpaXRBFi+SuSj/QFrpeg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAvI+e2Xzv8jtJ8QfP0jqkxg6FSx6RiThT9BzzZBuQHDAiEArDerC4vwWHIwwF+EYMygMSzDr0F5g2aHEJ4cWatasbI="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.29":{"name":"frontfax","version":"0.0.29","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.29","dist":{"shasum":"389b7c55aa419a71b386ed44465756e504e4171b","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.29.tgz","integrity":"sha512-qxrCE6JshhOJ+dltsXpBFgzyAc4SD4OdGWbJLsZMGO5pnkkmQRHFJ8mmtP/z6khggkoo039T6EMYk2jOSAn7Zg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDXnBItV6k0YUebWrpwBjOY+vRHQUzcffHys1vHSQ7ksAiEA2J/2XiODRpKE5xnOYzJ3134UvjxC7NMWSRotwsSxWZs="}]},"_from":".","_npmVersion":"1.2.10","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.30":{"name":"frontfax","version":"0.0.30","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.30","dist":{"shasum":"e6d5108b2e1453cf795d5f60d5c5bc14f65d58d8","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.30.tgz","integrity":"sha512-HN3wE77IWP+LLE6X04G0pMbC85mz8TKdiV61TjyWKuviYTIKrtnQYMXtggWmtJKeRdGyUrrQ1nZLnoksYtXzYQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCyT6SBUz7DHMpcjq9FcTlhDJPJ1cuQ01MZwX/oue+lLgIhAKenSxV2JdrG+p9VZrx3Kxk6EoWiaVB81TlNRZFr9tGY"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.31":{"name":"frontfax","version":"0.0.31","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.31","dist":{"shasum":"329ba4dae022cc506f2fcdacdecdca9d2175d724","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.31.tgz","integrity":"sha512-y4dJSCtxH8lEYWG9gvfy/lde/8sQACcZYvWJpS1L5G7DbRtt0ONhz4Kpa+4+X0GpXgB9ptav+FPZg3TRLNfoJA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCdoGyyXG6yVwzx3bh4+yrpJSQ8dmy6ux33Bm0I0k9MEwIhAKEw+7z/tSBhbmM2iUTcWXnVhM9itbVSk93tkK1nYSTQ"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.32":{"name":"frontfax","version":"0.0.32","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.32","dist":{"shasum":"91e5f455259ff9915930540f4b54b300a5620f2d","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.32.tgz","integrity":"sha512-xgwljsv7lGbnixi7N8FkjTFBwj23LghDuD+6nnBIBbPXb/vK5nlVdCqdF9TzRVIbxNxa0upXvBMk8ctsaeRmPg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDpb8rmXfanenw23BXtraJ434ZFF3cOtmIYhYfRuETmFwIhAKK2b+0mgWdiFF4DpPz6uFWxs85oBWsoFQoo0l889/mw"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.33":{"name":"frontfax","version":"0.0.33","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.33","dist":{"shasum":"6e76b612e60aa6c4cffbb59b41651b7d17e2a7b2","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.33.tgz","integrity":"sha512-vyNeO7p9V95SdML4qkPfUOgJcmv1i7/+KfIqE9lwf1jSvLR7fSFtepQ8fGrKQXGvQS06C3LonlRbu2TAD016wA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDdwBU0VusqJE9JjhbSXzzP1L22tfLNx4JKTigd2NSG+QIgX3qTMug17IUSLg4H1VZAZeYGn4aaNLDwVyHVx9z/pHE="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.0.34":{"name":"frontfax","version":"0.0.34","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.0.34","dist":{"shasum":"3c082fa5112b187595bb647af7c3570e8f07cc51","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.0.34.tgz","integrity":"sha512-8KKw8t9DljvJucG+UH0QzWKebikG5O0EDvKJg1+GOJjY7EIcRxrOCVEknrL7tDiddkAcb71ECbErHWdU7xvWSQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCWwAvaDTcVtYUFaNRDkeSZT0jIOdsoFPuQzZVQCH+g9AIhAKDNzrO0QjvkIDyTDbO0O5OHGwdqcZ4LM81SZdPCKTeS"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.1.0":{"name":"frontfax","version":"0.1.0","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\r\n========\r\n\r\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\r\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\r\n\r\nCreating a Project\r\n------------------\r\n\r\n1. Create a project `frontfax new myproject`\r\n2. Change in to the project's directory `cd myproject`\r\n3. Start the server `npm start`\r\n4. Then [view the server](http://localhost:5000)\r\n\r\nYour Workspace\r\n--------------\r\n\r\n\t- myproject\r\n\t\t- assets\r\n\t\t\t- css\r\n\t\t\t- images\r\n\t\t\t- js\r\n\t\t\t\t- src\r\n\t\t\t- less\r\n\t\t- static\r\n\r\nThis is the process in which frontfax handles each HTTP request:\r\n\r\n1. Receives a request (for example /images/logo.png).\r\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\r\n3. Proxies the request to the configured proxy server and returns the result.\r\n\r\n### Proxying\r\n\r\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\r\n\r\n```js\r\n{\r\n\t...\r\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\r\n\t...\r\n}\r\n```\r\n\r\n### URL Configuration\r\n\r\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\r\n\r\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\r\n\r\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \r\n\r\n### LESS\r\n\r\nTo install LESS support run the following command in your project directory `frontfax add --less`.\r\n\r\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\r\n\r\nThe advantages are of writing you CSS as LESS are:\r\n\r\n- Pre-processing functionality\r\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\r\n- You can compile a selection of files in to one.\r\n\r\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\r\n\r\nHere's an example. Try to split your work in to many easy to read files.\r\n\r\n```less\r\n/* assets/header.less */\r\n\r\n.header {\r\n\t.nav {\r\n\t\t/* nav styles */\r\n\t}\r\n\r\n\t.logo {\r\n\t\t/* logo styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/article.less */\r\n\r\n.article {\r\n\t.picture {\r\n\t\t/* picture styles */\r\n\t}\r\n\r\n\t.teaser {\r\n\t\t/* teaser styles */\r\n\t}\r\n}\r\n```\r\n\r\n```less\r\n/* assets/main.less */\r\n\r\n@import 'header';\r\n@import 'article';\r\n```\r\n\r\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\r\n\r\n```css\r\n/* build/main.css */\r\n\r\n.header .nav {\r\n\t/* nav styles */\r\n}\r\n.header .logo {\r\n\t/* logo styles */\r\n}\r\n.article .picture {\r\n\t/* picture styles */\r\n}\r\n.article .teaser {\r\n\t/* teaser styles */\r\n}\r\n```\r\n\r\n### JS Combine\r\n\r\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\r\n\r\n### Templating\r\n\r\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\r\n\r\n#### [Jade](http://jade-lang.com/)\r\n\r\n1. Install jade `npm i jade`\r\n2. Use the jade extension (`.jade`) when editing your templates\r\n\r\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\r\n\r\n1. Install coffee cup `npm i coffeecup`\r\n2. Use the coffee extension (`.coffee`) when editing your templates\r\n\r\n#### [Swig](http://paularmstrong.github.com/swig/)\r\n\r\n1. Install consolidate and swig `npm i consolidate swig`\r\n2. All html files will now be parsed with swig.\r\n\r\nBugs\r\n----\r\n\r\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\r\n\r\n","readmeFilename":"README.md","_id":"frontfax@0.1.0","dist":{"shasum":"9afedb801c5d47446723b3d1c8060ed73a8e5b46","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.1.0.tgz","integrity":"sha512-fHlz8u/k6EV8QVWYYpdEbs/rq4yn3X/0dB5XbITh3UEAg65EyR55DCOMf7yLvTSSkeD93sPjyToJUV36yEHzag==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIERMatzyk8J4NJg/wVDgE+02A6ZtEeon+v7Bs0kZr4hKAiByPKyvj6WIFfNHIpllFbbC+xJ/6UvzDtfrgTgxT9Z/5w=="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.2.0":{"name":"frontfax","version":"0.2.0","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax new myproject`\n2. Change in to the project's directory `cd myproject`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t\t- src\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### Proxying\n\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\n\n```js\n{\n\t...\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\n\t...\n}\n```\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \n\n### Response replacement\n\nSometimes you may need to automatically change the content from the response. For example, you may wish to change a URL from `http://assets.mysite.com` to `/images`. This can be by configuring the \"replacements\" in the `config/default.json` file. Here's that example:\n\n```js\n{\n\t\"base\": false,\n\t\"proxy\": \"http://www.mysite.com\", // this URL will automatically get replaced with \"\"\n\t\"replacements\": {\n\t\t\"http://assets.mysite.com\": \"/images\"\n\t}\n}\n```\n\nAs of v0.2.0, you can also use regular expressions by adding your replacements to a `$RegExp` object:\n\n```js\n{\n\t\"base\": false,\n\t\"proxy\": \"http://www.mysite.com\",\n\t\"replacements\": {\n\t\t\"http://assets.mysite.com\": \"/images\",\n\t\t$RegExp: {\n\t\t\t\"http://s1\\\\.wp\\\\.com/\\\\?custom-css=(\\\\d+)[^\"]*\": \"/stylesheets/custom-$1.css\"\n\t\t}\n\t}\n}\n```\n\nThe regular expression needs to be passed as a string. Hence why you see the double backquotes.\n\n### LESS\n\nTo install LESS support run the following command in your project directory `frontfax add --less`.\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\n\n### Templating\n\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\n\n#### [Jade](http://jade-lang.com/)\n\n1. Install jade `npm i jade`\n2. Use the jade extension (`.jade`) when editing your templates\n\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\n\n1. Install coffee cup `npm i coffeecup`\n2. Use the coffee extension (`.coffee`) when editing your templates\n\n#### [Swig](http://paularmstrong.github.com/swig/)\n\n1. Install consolidate and swig `npm i consolidate swig`\n2. All html files will now be parsed with swig.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.2.0","dist":{"shasum":"b1a8d692e41522bb599937a3da0dd5ac4034a654","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.2.0.tgz","integrity":"sha512-aiXJuAljLInjmz8cD8kjc1i7KrhMWkie6Uc8qIsgaj8G6DP9U6X0XJlsvJCdlE3V7T2Zeioj3wzQ5+PAndpmng==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICkUK/RhTCtI8fIjOOuKToI3wylXCSatNxC2qurhUvopAiBgTRvqTL8OjgRc0LqRVZ5ACtlVXWSS2yZYBK5BHnYZOw=="}]},"_from":".","_npmVersion":"1.2.23","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]},"0.2.1":{"name":"frontfax","version":"0.2.1","description":"Development environment for frontend developers at Fairfax Media.","main":"build/app/index.js","bin":{"frontfax":"bin/frontfax.js"},"scripts":{"prepublish":"coffee -b -c -o build src","dev":"coffee -b -c -w -o build src"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"},"dependencies":{"async":"0.1.22","commander":"1.1.1","config":"0.4.18","express":"3.0.6","less":"1.3.3","mkdirp":"0.3.4","module-index":"3.0.2","request":"2.12.0","socket.io":"~0.9.13","gaze":"~0.3.2","bytes":"~0.2.0","colors":"~0.6.0-1","child-proc":"0.0.1"},"devDependencies":{"coffee-script":"1.4.0","consolidate":"~0.8.0","swig":"~0.13.5","jade":"~0.28.1","coffeecup":"~0.3.19"},"readme":"Frontfax\n========\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax, Grunt and Foreman `[sudo] npm i -g frontfax grunt-cli foreman`\n\nCreating a Project\n------------------\n\n1. Create a project `frontfax new myproject`\n2. Change in to the project's directory `cd myproject`\n3. Start the server `npm start`\n4. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t\t- src\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### Proxying\n\nThe greatest feature of Frontfax is it's ability to target a proxy server for files that don't exist on your computer. To configure the proxy target open `config/default.json` and change the `proxy` option:\n\n```js\n{\n\t...\n\t\"proxy\": \"http://www.the.site.im.working.on.com\"\n\t...\n}\n```\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `[image|css|js].paths` urls. \n\n### Response replacement\n\nSometimes you may need to automatically change the content from the response. For example, you may wish to change a URL from `http://assets.mysite.com` to `/images`. This can be by configuring the \"replacements\" in the `config/default.json` file. Here's that example:\n\n```js\n{\n\t\"base\": false,\n\t\"proxy\": \"http://www.mysite.com\", // this URL will automatically get replaced with \"\"\n\t\"replacements\": {\n\t\t\"http://assets.mysite.com\": \"/images\"\n\t}\n}\n```\n\nAs of v0.2.0, you can also use regular expressions by adding your replacements to a `$RegExp` object:\n\n```js\n{\n\t\"base\": false,\n\t\"proxy\": \"http://www.mysite.com\",\n\t\"replacements\": {\n\t\t\"http://assets.mysite.com\": \"/images\",\n\t\t$RegExp: {\n\t\t\t\"http://s1\\\\.wp\\\\.com/\\\\?custom-css=(\\\\d+)[^\\\"]*\": \"/stylesheets/custom-$1.css\"\n\t\t}\n\t}\n}\n```\n\nThe regular expression needs to be passed as a string. Hence why you see the double backquotes.\n\n### LESS\n\nTo install LESS support run the following command in your project directory `frontfax add --less`.\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined from assets/js/src/*.js into assets/js/main.js.\n\n### Templating\n\nWhile working on your static files in the `static` directory, you can also use a variety of templating languages.\n\n#### [Jade](http://jade-lang.com/)\n\n1. Install jade `npm i jade`\n2. Use the jade extension (`.jade`) when editing your templates\n\n#### [Coffee-Cup](https://github.com/gradus/coffeecup)\n\n1. Install coffee cup `npm i coffeecup`\n2. Use the coffee extension (`.coffee`) when editing your templates\n\n#### [Swig](http://paularmstrong.github.com/swig/)\n\n1. Install consolidate and swig `npm i consolidate swig`\n2. All html files will now be parsed with swig.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","readmeFilename":"README.md","_id":"frontfax@0.2.1","dist":{"shasum":"f714c138026e64c0cf8b217d1ba273ba63bcd032","tarball":"https://registry.npmjs.org/frontfax/-/frontfax-0.2.1.tgz","integrity":"sha512-Nxa/JJRN5xJkD4LQUALzmTeSlslhfbl9qViL7VONDUrFDzfL/oqcXL16uHJzdGWFPtzt2Hw5fvFQYu5eEkrjCw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA0pMdPz/tYAB0q52CjgHY5GATMfGC9n8hSA7bw8NbS+AiBxezp7WOkYuQ+svEZvGeUGud9D3eb9g75AIDZA5DPJCw=="}]},"_from":".","_npmVersion":"1.2.23","_npmUser":{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"},"maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}]}},"readme":"Frontfax\n=======\n\nSets up a development environment for frontend developers that can't access the source code. Recently, at the last couple of places that I've been working, it's been somewhat impossible to access the source code of the working project, and therefore, I've been downloading the source via the web, working on it and then posting it back to backend developers to insert in to the project. This is somewhat annoying, so I've developed **Frontfax**.\n\nInstallation\n------------\n\n1. Install [node](http://nodejs.org) and [npm](https://npmjs.org)\n2. Install Frontfax `[sudo] npm i -g frontfax` (TODO: It hasn't been released to NPM yet.\n3. Create a project `frontfax project:new myproject`\n4. Install the dependencies `cd myproject && npm i`\n5. Start the server `npm start`\n6. Then [view the server](http://localhost:5000)\n\nYour Workspace\n--------------\n\n\t- myproject\n\t\t- assets\n\t\t\t- css\n\t\t\t- images\n\t\t\t- js\n\t\t\t- less\n\t\t- static\n\nThis is the process in which frontfax handles each HTTP request:\n\n1. Receives a request (for example /images/logo.png).\n2. Tries to find it in your workspace (assets/images/logo.png). If found the file is returned and the process stops here.\n3. Proxies the request to the configured proxy server and returns the result.\n\n### URL Configuration\n\nThe images, js, css URLs are can configured, but these files will always be accessed from you assets directory.\n\nThe `static` directory is the last place the server looks before proxying the request. This is good for HTML files. You do not need to configure the URL for this as it will consider the root to be accessible from the static directory.\n\nTo change the URLs open the `config/default.json` file and edit the `assets.image|css|js` urls. \n\n### LESS\n\nWhile you're working on any less files they will automatically be converted in to css and placed in the css directory.\n\nThe advantages are of writing you CSS as LESS are:\n\n- Pre-processing functionality\n- Syntax is the same as CSS, so even if you don't want to use LESS's functionality you can just write plain CSS.\n- You can compile a selection of files in to one.\n\nWhen writing your less files, it is recommended to have one \"main\" file that includes all the requirements. This means that only one file needs to be uploaded to the production server after development.\n\nHere's an example. Try to split your work in to many easy to read files.\n\n```less\n/* assets/header.less */\n\n.header {\n\t.nav {\n\t\t/* nav styles */\n\t}\n\n\t.logo {\n\t\t/* logo styles */\n\t}\n}\n```\n\n```less\n/* assets/article.less */\n\n.article {\n\t.picture {\n\t\t/* picture styles */\n\t}\n\n\t.teaser {\n\t\t/* teaser styles */\n\t}\n}\n```\n\n```less\n/* assets/main.less */\n\n@import 'header';\n@import 'article';\n```\n\nNow you can point to one CSS file (`/my/configured/css/path/main.css`) and have all your CSS returned:\n\n```css\n/* build/main.css */\n\n.header .nav {\n\t/* nav styles */\n}\n.header .logo {\n\t/* logo styles */\n}\n.article .picture {\n\t/* picture styles */\n}\n.article .teaser {\n\t/* teaser styles */\n}\n```\n\n### JS Combine\n\nWhile you're working on any js files they will automatically be combined into assets/js/main.js.\n\nBugs\n----\n\nReport all bugs in the [Bitucket issue list](https://bitbucket.org/johngeorgewright/frontfax/issues).\n\n","maintainers":[{"name":"johngeorgewright","email":"johngeorge.wright@gmail.com"}],"time":{"modified":"2022-06-18T03:46:56.664Z","created":"2013-01-21T00:03:28.936Z","0.0.1":"2013-01-21T00:03:32.427Z","0.0.2":"2013-01-21T04:48:24.528Z","0.0.3":"2013-01-23T23:31:10.855Z","0.0.4":"2013-01-24T04:04:39.598Z","0.0.5":"2013-01-24T23:35:14.584Z","0.0.6":"2013-01-28T22:03:10.066Z","0.0.7":"2013-01-29T10:02:09.844Z","0.0.8":"2013-01-30T09:13:20.429Z","0.0.9":"2013-01-31T22:32:07.885Z","0.0.10":"2013-02-02T01:30:36.240Z","0.0.11":"2013-02-03T01:56:38.084Z","0.0.12":"2013-02-03T02:04:33.561Z","0.0.13":"2013-02-04T11:23:43.892Z","0.0.14":"2013-02-04T11:32:50.492Z","0.0.15":"2013-02-04T23:02:24.560Z","0.0.16":"2013-02-06T03:12:00.882Z","0.0.17":"2013-02-06T23:08:43.845Z","0.0.18":"2013-02-07T03:24:11.556Z","0.0.19":"2013-02-07T23:56:15.560Z","0.0.20":"2013-02-08T00:59:16.338Z","0.0.21":"2013-02-09T02:32:02.076Z","0.0.22":"2013-02-13T00:12:27.284Z","0.0.23":"2013-02-14T05:23:29.619Z","0.0.24":"2013-02-14T22:56:32.023Z","0.0.25":"2013-02-18T05:22:58.159Z","0.0.26":"2013-02-22T05:59:51.997Z","0.0.27":"2013-02-26T02:02:23.490Z","0.0.28":"2013-02-26T05:28:33.166Z","0.0.29":"2013-03-03T23:40:53.370Z","0.0.30":"2013-03-14T23:08:12.582Z","0.0.31":"2013-03-20T23:54:11.734Z","0.0.32":"2013-04-04T00:40:20.492Z","0.0.33":"2013-04-04T01:20:29.862Z","0.0.34":"2013-04-07T23:39:12.008Z","0.1.0":"2013-04-29T02:14:49.404Z","0.2.0":"2013-05-26T17:05:51.480Z","0.2.1":"2013-05-27T16:09:14.622Z"},"author":{"name":"John Wright","email":"john.wright@fairfaxmedia.com.au"}}