Most likely, this would turn into a hard dependency on node. Moreover, It would entail a departure from being able to run compiled Jade in any JavaScript environment because now we would have a hard dependency on some way to read from the file system. Thus, the feature would be used by only part of the community and might have to live behind some config flag. My first big beef with it is that it would mean a feature disparity between server-side and client-side jade. I'll outline my reasons as well as yet another alternative for you to use. Luckily, all of these are supported with squido and you can find our more here.Similar to the other voices, my pondering also yields that we shouldn't have this. Generates something like this: Hello, World! Hello, World! Pug rocks!! Pug (formally Jade) is quite a different syntax to the other template engines and allows for shorthand and indentation syntax quite like yaml. Similar to Handlebars, EJS is close to HTML which makes it easier to learn, read and debug if you are familiar with the HTML syntax.

ĮJS is quite similar to Handlebars but has more of a Javascript feel with a variable delimiter. This helps if you are familiar with HTML and simply want to extend by looping data, conditional rendering, formatting etc. Some see the benefit of Handlebars is how closely it looks like HTML. Handlebars is based on the Mustache syntax using as the general variable delimiter.

Some template engines look quite like HTML like Handlebars and EJS whereas others are vastly different and are indentation based like Pug. Some of the benefits is the ability to insert variables/data, loop data to create HTML, conditional rendering and other clever rendering rules and formatting. Templating engines are essentially a way to generate HTML.

Pug template conditional