Introducing Socket Firewall: Free, Proactive Protection for Your Software Supply Chain.Learn More
Socket
Book a DemoInstallSign in
Socket

minijinja-js

Package Overview
Dependencies
Maintainers
1
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

minijinja-js

JavaScript bindings for minijinja

latest
Source
npmnpm
Version
2.12.0
Version published
Maintainers
1
Created
Source

MiniJinja for JavaScript: a powerful template engine

License

minijinja-js is an experimental binding of MiniJinja to JavaScript. It has somewhat limited functionality compared to the Rust version. These bindings use wasm-bindgen.

You might want to use MiniJinja instead of Jinja2 when the full feature set of Jinja2 is not required and you want to have the same rendering experience of a data set between Rust, Python and JavaScript.

This exposes a bunch of MiniJinja via wasm to the browser, but not all of it.

This package can be useful if you have MiniJinja templates that you want to evaluate as a sandbox in a browser for a user or on the backend. Given the overheads that this creates size and performance wise, it would not be wise to use this for actual template rendering in the browser.

Example

Render a template from a string:

import { Environment } from "minijinja-js";

const env = new Environment();
env.debug = true;
const result = env.renderStr('Hello {{ name }}!', { name: 'World' });
console.log(result);

Render a template registered to the engine:

import { Environment } from "minijinja-js";

const env = new Environment();
env.addTemplate('index.html', 'Hello {{ name }}!');
const result = env.renderTemplate('index.html', { name: 'World' });
console.log(result);

Evaluate an expression:

import { Environment } from "minijinja-js";

const env = new Environment();
const result = env.evalExpr('1 + 1', {});
console.log(result);

Web Usage

If you want to use minijinja-js from the browser instead of node, you will need to use slightly different imports and call init explicitly:

import init, { Environment } from "minijinja-js/dist/web";
await init();

Known Limitations

There are various limitations with the binding today, some of which can be fixed, others probably not so much. You might run into the following:

  • Access of the template engine state from JavaScript is not possible.
  • You cannot register a custom auto escape callback or a finalizer
  • If the engine panics, the WASM runtime corrupts.

Sponsor

If you like the project and find it useful you can become a sponsor.

Keywords

jinja2

FAQs

Package last updated on 24 Aug 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts