Tiny opiniated web framework for node that relies heavily on fs.
$ npm install -g fsjs
fsjs watches the current application's entry point directory for changes, and requires all files ending with '.js'
$ lsedit.jsapp.js$ cat app.jsrequire('fsjs')(8000)$ node app.js
It handles urls like '/edit/master' by calling edit.js's exported method
The default callback writes the data to res, stringifying it if it is an object. You can pass your own callback if you like (in your main file, say app.js):
You can also pass names for arguments in the url before the module name:
They are passed as properties of this to your module, so '/arpith/fsjs/edit/master/README.md' can be handled by edit.js:
var callback = argumentsargumentslength-1console.logthisuser// arpithconsole.logthisrepo// fsjsconsole.logbranch// masterconsole.logfile// README.mdcallback'done'
It also handles smaller urls (say '/arpith/edit') as expected:
Finally, this also has the request and response that http.createServer passes:
console.logthisrequesturl// /arpith/fsjs/edit/master/readme.mdconsole.logthisresponsestatusCode// 200
The MIT License (MIT)
Copyright (c) 2013 Arpith Siromoney firstname.lastname@example.org
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.