Mustache VS handlebars.js

Mustache is used mainly for mobile and web applications, it has a very big community as its the most popular JavaScript template engine means that if you face any error on Mustache then its solutions are easily available and along with that it is Open source its Github repository name is https://github.com/Mustache/Mustache

Please don’t do this. Use a templating system like mustache https://github.com/mustache/mustache. It’s easier for your users and doesn’t expose the entire system to them. I generally use this in conjunction with markdown.

I recently had to generate multiple configuration files for Apache httpd server. My first choice was Apache Module mod_macro, however, it has too many limitations. My second choice was to use mustache templates and I was super excited that it is also available in bash! Everything seems great until I attempted to use arrays, and it did not work. Most likely because it was implemented for Bash 3.x which is 10 years old. I did not want to mess with my environment by adding or switching to older version of Bash. Because Scala is my weapon of choice, I decided for my third attempt, to try solving this problem using Scala and Twirl templating engine. I know it might seem like an overkill, however, my previous choices have failed me, so I wanted my next attempt to be the final one! 😎

If you have a bit of Nodejs SSR background, you would already be accustomed to templating libraries like Pug, Handlebars, EJS, etc. If you’re from a PHP background you would be familiar with the Blade templating engine. These templating libraries basically help you render dynamic data from the backend on the frontend. They also help you generate markup with loops based on conditions.

It’s time to create our code template. To do this, we use handlebars js, which allows us to create templates at a basic level. We create a folder called templates in the project home directory and add our template files inside.

Templating engine: SSGs rely on templating engines to define the structure of web pages. These engines enable developers to create reusable templates and incorporate dynamic content. Popular templating engines include Liquid, Handlebars, Mustache, EJS, ERB, HAML, and Slim.

Here's our first usage of the handlebars (docs) template. The .hbs extension will be removed once we run the action. Inside index.ts.hbs, add:

Id use handlerbars JS - https://handlebarsjs.com/

Node.js programming language will be used for simplicity. Handlebars template engine to separate data from the presentation. html2pdf.app to convert HTML to PDF, but as an alternative Puppeteer can be used also (you can find a complete tutorial How to convert HTML to PDF with puppeteer).

Handlebars.js site

But a valid question is: Why not use a template like Handlebars? For the use case inside Woovi, templates won't help us because we would need two core points: reuse our design system and ensure the usage of GraphQL in our payment link.

You might want to brush up on https://handlebarsjs.com/ if you want to make templates.

Once the package is set up, it will provide a MailService class that has a method named sendEmail that will receive some parameters and then send the mail. But first, we need to create the mail template and for that, we will use handlebars. It will allow us, to create HTML templates in which we can pass dynamics parameters, such as the user name or its information, and write inline CSS to style our email.