when passing a variable named 'client' in res.render, jade throws an error

[maxwellium]

reproduced this across several projects, using current jade version

also experienced by others:

http://stackoverflow.com/questions/10618427/railway-js-jade-crashes-when-a-route-to-client-is-defined#11496334

[ForbesLindesay]

Client is an option, it triggers compiling, but not rendering the template, so that you get a JavaScript function you can render on the client. Unfortunately all I can suggest is that you name the variable something else. We could possibly improve documentation in this area though.

[maxwellium]

is that an express option or jade-specific? shouldn't we separate option passing from variable passing?

[ForbesLindesay]

Most template libraries do just mix them in one big object like jade does. It's jade specific, although I imagine if people start adapting other template libraries to support compiling for client side use we'll see a lot more libraries have the same issue.

[ForbesLindesay]

In 2.0.0 we can completely remove the client option and allow you to use it just like any other local.

[maxwellium]

<3

[ForbesLindesay]

This will be looked at in 2.0.0