Better reporting for js syntax errors

Big hack, but if we could catch the syntax errors, we could apply a real lineno to the stack trace. At least this exposes the contents of the line
pugjs · Jul 3, 2010 · 0fa6466 · 0fa6466
1 parent cd67780
commit 0fa6466
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 3 deletions.
diff --git a/examples/users.jade b/examples/users.jade
@@ -7,4 +7,4 @@ users
           - user.roles.forEach(function(role){
             role= role
           - })
-  - })
+  - })
diff --git a/lib/jade.js b/lib/jade.js
@@ -679,8 +679,14 @@ exports.render = function(str, options){
     }
 
     // Generate function
-    var fn = Function('locals, attrs, escape, _', 'with (locals) {' + js + '}');
-
+    try {
+        var fn = Function('locals, attrs, escape, _', 'with (locals) {' + js + '}');
+    } catch (err) {
+        // TODO: re-catch and apply real lineno
+        process.compile(js, filename || 'Jade');
+        return;
+    }
+
     try {
         var _ = { lineno: 1 };
         return fn.call(options.scope,