-
Notifications
You must be signed in to change notification settings - Fork 0
Home
FlowLike Typst Nodes is a WASM node package for turning Typst source or stored Typst projects into PDF and SVG files. It can also turn model-generated Markdown into safe Typst body content and apply reusable Typst template functions to document bodies and workflow data.
- Using Templates explains the template mental model and includes a complete copyable example.
- Node Reference lists every node and its important pins.
-
Project Files and Packages explains
source_folder, relative paths, assets, and Typst Universe packages. - Markdown to Typst covers model-generated document bodies and static charts.
- Development and Publishing covers local tests, WASM builds, and the release artifact.
For plain Typst source, add Typst Source to PDF and connect:
| Pin | Value |
|---|---|
source |
= Hello from FlowLike |
output_file |
A writable PDF FlowPath
|
source_folder |
Optional project folder for imports and assets |
Run the node. It writes the PDF to output_file, returns that same FlowPath,
and returns a compile report with page and warning counts.
For a reusable layout plus variable data, use Typst Source with Template to
PDF or Typst File with Template to PDF. The template node imports a
function from template_file, passes the top-level keys from template_data
as named arguments, and supplies the source/body as the function's final
content argument.
The package consistently offers two input styles:
| Input style | Body comes from | Best for |
|---|---|---|
| Source | A source string pin |
Generated or formatted Typst text inside a workflow |
| File | A stored .typ source_file
|
Multi-file projects, maintained documents, and assets |
Each compile style is available for PDF, SVG, or PDF + SVG. The combined nodes compile once and write both outputs; their PDF and SVG paths must be different.
File and folder pins use FlowLike FlowPath objects, not path strings. Select a
file/folder in FlowLike or connect a node that produces a FlowPath.
The Wiki tracks the behavior of the current repository. For the implementation and issue tracker, see the GitHub repository.