Permalink
Browse files

Fixes jade compiler; implements settings.resolve_index

  • Loading branch information...
1 parent 95d1393 commit 5a57b9603932adea56a4f4c3d8c5cf3b190e1600 @dsc committed Nov 9, 2011
View
No changes.
View
@@ -0,0 +1,17 @@
+CWD = process.cwd()
+{spawn, exec} = require 'child_process'
+
+run = (args) ->
+ args = args.split() if typeof args is 'string'
+ proc = spawn 'coco', args
+ proc.stderr.on 'data', say
+ proc .on 'exit', -> process.exit it if it
+
+
+task \build 'build coco sources' ->
+ run <[ -bjc package.co ]>
+ run <[ -bc compiler.co ]>
+
+task \server 'Starts test-server for browser tests.' ->
+ server = require CWD+'test/server/server'
+
View
@@ -4,18 +4,20 @@
- Remove `yaml-python`, `CommonJS` compilers and create a `connect-compiler-extras` package for myself.
## later
-- Restructure middleware responder to use events to trigger compiler phases, remove `seq`.
- Make `setup()` a simple proxy to `CompilerMiddleware` class.
+- Restructure middleware responder to use events to trigger compiler phases, remove `seq`. State machine?
- Add post-`write()` cleanup/finally event (which fires whether successful or not).
-- GitHub site with introduction, documentation.
+- Config: `on` for attaching event handlers to compiler phases
- Replace `#token` in config Strings.
+- Allow nested `enabled` list for a more sane `cascade`
## docs
+- GitHub site with introduction, documentation.
- examples:
- simple usage
- - with plain connect
+ - with connect
- with express
- recursive compiling (CommonJS, Uglify; @wraps)
- custom compilers
Oops, something went wrong.

0 comments on commit 5a57b96

Please sign in to comment.