troygoode/connect-assets-jade

Expose your jade views in the browser using connect-assets.

connect-assets-jade's Issues

jade files do not served with md5 in production mode

Javascript errors from compiled Jade templates

Using connect-assets-jade now results in an error for the compiled jade template in the following function:

function rethrow(err, filename, lineno){
  if (!filename) throw err;

  var context = 3
    , str = require('fs').readFileSync(filename, 'utf8')
    , lines = str.split('\n')
    , start = Math.max(lineno - context, 0)
    , end = Math.min(lines.length, lineno + context);

  // Error context
  var context = lines.slice(start, end).map(function(line, i){
    var curr = i + start + 1;
    return (curr == lineno ? '  > ' : '    ')
      + curr
      + '| '
      + line;
  }).join('\n');

  // Alter exception message
  err.path = filename;
  err.message = (filename || 'Jade') + ':' + lineno
    + '\n' + context + '\n\n' + err.message;
  throw err;
}

Chrome's javascript console has the following error:
Uncaught ReferenceError: require is not defined

It looks like the Jade isn't compiling for client-side use, since it is using node commands (require).

Please let me know if you need any additional information.

Edit: This only happens when I set debug:true. Problem is resolved as long as I don't have debugging enabled.

Is there an option to compile jade without client runtime code

I prefer to include jade client runtime code only once and not for every template.
Is there on option for this?