eta (η) VS mustache.js

ERDIA uses the ETA template engine to generate documentation. The reason for using a template engine is that it allows you to customize the documentation the way you want it. If you want to customize documentation that ERDIA generates run the following command.

Eta : a lightweight and blazing fast embedded JS templating engine that works inside Node, Deno, and the browser.

I've been using Eta: https://eta.js.org/

It doesn't do gzip or image optimization, but such features might be better suited as server middlewares separate from the template engine.

Haven’t used it yet, but Eta supports Deno: https://eta.js.org/

Eta is a very similar template engine to EJS. It's supposed to be faster, lighter, with async templates.

https://eta.js.org/

https://github.com/eta-dev/eta/

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.

I also enjoy simple templating engines. It makes it far easier to reason about a template and mentally step-through it. For existing art, there are:

DustJS which is a "logic-less" template engine (just loops and simple if-statements): https://github.com/linkedin/dustjs

and there is also mustache, which is very similar: https://mustache.github.io/

Personally, I've re-implemented DustJS in rust but its still a very alpha project: https://code.fizz.buzz/talexander/duster

Other popular templating engines include Jade, EJS, and Handlebars. Jade is a high-performance templating engine that is used for server-side rendering. EJS is a lightweight templating engine that is used for client-side and server-side rendering. Handlebars is a templating language that is based on the Mustache template language.

JSX just a templating language in this case, right? No reactivity at all? What's the benefit against using something like https://github.com/janl/mustache.js/ ?

No, it's an implementation of the already existing Mustache templates for C++.

This is one of the least-bad names because it implements a non-Boost standard and it's named after that. I've used mustache in Python so knew immediately it was a templating language.

First, I setup mustache (npm package) as the templating language (the npm package hasn’t been updated in two years, so that’s great). Mustache is really simple, it provides a few helper utilities, like replacing variables, or iterating over data,

Once the array is ready and back in place, we need to display the information from the emails, and for that we can use the template node. This node uses the mustache system, which is a logicless template engine for creating dynamic content. In other words, it generates HTML code by using tags that are replaced by code.

I would argue that way to many languages are Turing complete. Database queries shouldn't be. CSS selectors shouldn't be. Template languages shouldn't be (i.e. why mustache is superior to most other templating languages).

My bad: https://mustache.github.io/