Development
Scripts (package root)
Section titled “Scripts (package root)”| Command | Purpose |
|---|---|
npm run build | Release native addon + generated JS/TS |
npm run build:debug | Debug native build |
npm test | Node tests: __test__/*.test.mjs, JSON conformance, parity vs nunjucks (build first) |
npm run test:rust | Rust integration tests (native/crates/runjucks-core/tests/) |
npm run test:rust:green | Smaller subset of Rust tests |
npm run test:conformance:rust / test:conformance:node | JSON goldens (subset of npm test) |
Layout
Section titled “Layout”- Node package —
package.json,index.js,index.d.ts,__test__/, generated*.node native/— Cargo workspace (Cargo.toml,crates/runjucks-core/,crates/runjucks-napi/, fixtures undernative/fixtures/)
The runjucks_core crate documents the engine publicly; browse it on the docs site (Rust crate (rustdoc)) or with cargo doc -p runjucks_core.
Optional harness
Section titled “Optional harness”For notes on running a Nunjucks-style Mocha harness against renderString, see test-shim/README.md in the repo.
Parity backlog
Section titled “Parity backlog”A detailed, maintainer-oriented checklist of behavior vs Nunjucks lives in NUNJUCKS_PARITY.md in the repository. End users should rely on Template language, JavaScript API, and Limitations instead.