tsconfig-paths VS eta (η)

If you've use a re-map path in your project, you have to pass it up to tsconfig-paths like this,

There are multiple libraries available for configuring path aliases in Node.js, such as alias-hq and tsconfig-paths. However, while looking through the Node.js documentation, I discovered a way to configure path aliases without having to rely on third-party libraries. Moreover, this approach enables the use of aliases without requiring the build step.

If you're not using webpack, you can give tsconfig-paths a try.

Path mapping Very handy tsconfig-paths library allows to import modules from the filesystem without prefixing them with "./".

was just dealing with this yesterday. You need to use this package: https://github.com/dividab/tsconfig-paths

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.

Just stumbled on this: https://github.com/eta-dev/eta

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/