This is a fork of the awesome easy-template-x project with some additional bugfixes which haven't been integrated yet into the main repository.
Generate docx documents from templates, in Node or in the browser.
- Node Example
- Browser Example
- Live Demo
- Plugins
- Listing tags
- Scope resolution
- Extensions
- Template handler options
- Supported Binary Formats
- Internal API
- Philosophy
- Prior art and motivation
- Changelog
import * as fs from 'fs';
import { TemplateHandler } from 'easy-template-x';
// 1. read template file
const templateFile = fs.readFileSync('myTemplate.docx');
// 2. process the template
const data = {
posts: [
{ author: 'Alon Bar', text: 'Very important\ntext here!' },
{ author: 'Alon Bar', text: 'Forgot to mention that...' }
]
};
const handler = new TemplateHandler();
const doc = await handler.process(templateFile, data);
// 3. save output
fs.writeFileSync('myTemplate - output.docx', doc);Input:
Output:
The following example produces the same output while running in the browser. Notice that the actual template processing (step 2) is exactly the same as in the previous Node example.
import { TemplateHandler } from 'easy-template-x';
// 1. read template file
// (in this example we're loading the template by performing
// an AJAX call using the fetch API, another common way to
// get your hand on a Blob is to use an HTML File Input)
const response = await fetch('http://somewhere.com/myTemplate.docx');
const templateFile = await response.blob();
// 2. process the template
const data = {
posts: [
{ author: 'Alon Bar', text: 'Very important\ntext here!' },
{ author: 'Alon Bar', text: 'Forgot to mention that...' }
]
};
const handler = new TemplateHandler();
const doc = await handler.process(templateFile, data);
// 3. save output
saveFile('myTemplate - output.docx', doc);
function saveFile(filename, blob) {
// see: https://stackoverflow.com/questions/19327749/javascript-blob-filename-without-link
// get downloadable url from the blob
const blobUrl = URL.createObjectURL(blob);
// create temp link element
let link = document.createElement("a");
link.download = filename;
link.href = blobUrl;
// use the link to invoke a download
document.body.appendChild(link);
link.click();
// remove the link
setTimeout(() => {
link.remove();
window.URL.revokeObjectURL(blobUrl);
link = null;
}, 0);
}Checkout this live demo on CodeSandbox 😎
easy-template-x uses a plugin model to support it's various template manipulation capabilities. There are some built-in plugins and you can also write your own custom plugins if required.
These are the plugins that comes bundled with easy-template-x:
- Simple text replacement plugin.
- Loop plugin for iterating text, table rows and list rows and for simple conditions.
- Image plugin for embedding images.
- Link plugin for hyperlinks creation.
- Raw xml plugin for custom xml insertion.
The most basic plugin. Replaces a single tag with custom text. Preserves the original text style.
Input template:
Input data:
{
"First Tag": "Quis et ducimus voluptatum\nipsam id.",
"Second Tag": "Dolorem sit voluptas magni dolorem molestias."
}Output document:
Iterates text, table rows and lists.
Requires an opening tag that starts with # and a closing tag that starts with / (configurable).
Note: The closing tag does not need to have the same name as the opening tag, or a name at all. This will work {#loop}{/loop}, but also this {#loop}{/} and even this {#loop}{/something else}.
Input template:
Input data:
{
"Beers": [
{ "Brand": "Carlsberg", "Price": 1 },
{ "Brand": "Leaf Blonde", "Price": 2 },
{ "Brand": "Weihenstephan", "Price": 1.5 }
]
}Output document:
You can render content conditionally depending on a boolean value using the same syntax used for loops.
The example below shows two lines being rendered, each with different content depending on the truthy value.
Input template:
Input data:
{
lines: [
{ visible: true },
{ invisible: true }
]
}Output document:
Nested conditions are also supported, so you can nest other tags including loop tags and even other conditions in them. When doing so remember to format your data accordingly. See the example below for clarification:
Input template:
Input data:
Notice how even though name and members are nested in the template under the show condition their values are adjacent to it in the input data.
{
"teams": [
{
show: true,
name: "A-Team",
members: [
{ name: "Hannibal" },
{ name: "Face" },
{ name: "Murdock" },
{ name: "Baracus" },
]
},
{
show: false,
name: "B-Team",
members: [
{ name: "Alice" },
{ name: "Bob" },
{ name: "Charlie" },
{ name: "Dave" },
]
}
],
}Output document:
If you are looking for a yet more powerful conditional syntax see the alternative syntax section.
Embed images into the document.
Input template:
Input data:
{
"Kung Fu Hero": {
_type: "image",
source: fs.readFileSync("hero.png"),
format: MimeType.Png,
altText: "Kung Fu Hero", // Optional
width: 200,
height: 200
}
}Output document:
Inserts hyperlinks into the document.
Like text tags link tags also preserve their original style.
Input template:
Input data:
{
"easy": {
_type: 'link',
text: 'super easy', // Optional - if not specified the `target` property will be used
target: 'https://github.com/alonrbar/easy-template-x'
}
}Output document:
Add custom xml into the document to be interpreted by Word.
Tip:
You can add page breaks using this plugin and the following xml markup:
<w:br w:type="page"/>
Input template:
Input data:
{
"Dont worry be happy": {
_type: 'rawXml',
xml: '<w:sym w:font="Wingdings" w:char="F04A"/>',
replaceParagraph: false, // Optional - should the plugin replace an entire paragraph or just the tag itself
}
}Output document:
To write a plugin inherit from the TemplatePlugin class.
The base class provides two methods you can implement and a set of utilities to
make it easier to do the actual xml modification.
To better understand the internal structure of Word documents check out this excellent source.
Example plugin implementation (source):
/**
* A plugin that inserts raw xml to the document.
*/
export class RawXmlPlugin extends TemplatePlugin {
// Declare the unique "content type" this plugin handles
public readonly contentType = 'rawXml';
// Plugin logic goes here:
public simpleTagReplacements(tag: Tag, data: ScopeData): void {
// Tag.xmlTextNode always reference the actual xml text node.
// In MS Word each text node is wrapped by a <w:t> node so we retrieve that.
const wordTextNode = this.utilities.docxParser.containingTextNode(tag.xmlTextNode);
// Get the value to use from the input data.
const value = data.getScopeData() as RawXmlContent;
if (value && typeof value.xml === 'string') {
// If it contains a "xml" string property parse it and insert.
const newNode = this.utilities.xmlParser.parse(value.xml);
XmlNode.insertBefore(newNode, wordTextNode);
}
// Remove the placeholder node.
// We can be sure that only the placeholder is removed since easy-template-x
// makes sure that each tag is isolated into it's own separate <w:t> node.
XmlNode.remove(wordTextNode);
}
}The content type that this plugin expects to see is:
export interface RawXmlContent extends PluginContent {
_type: 'rawXml';
xml: string;
}You can get the list of tags in a template by calling the parseTags method as follows:
import { TemplateHandler } from 'easy-template-x';
const templateFile = fs.readFileSync('myTemplate.docx');
const handler = new TemplateHandler();
const tags = await handler.parseTags(templateFile);easy-template-x supports tag data scoping. That is, you can reference
"shallow" data from within deeper in the hierarchy similarly to how you can
reference an outer scope variables from within a function in JavaScript. You can
leverage this property to declare "top level" data (your logo and company name
or some useful xml snippets like page breaks, etc.) to be used anywhere in the
document.
Input template:
(notice that we are using the "Company" tag inside the "Employees" loop)
Input data:
(notice that the "Company" data is declared outside the "Employees" loop, in it's so called "outer scope")
{
"Company": "Contoso Ltd.",
"Employees": [
{ "Surname": "Gates", "Given name": "William" },
{ "Surname": "Nadella", "Given name": "Satya" },
]
}Output document:
While most document manipulation can be achieved using plugins, there are some cases where a more powerful tool is required. In order to extend the document manipulation process you can specify extensions that will be run before and/or after the standard template processing.
To write an extension inherit from the TemplateExtension class.
By default no extension is loaded. Extensions and the order they run in are specified via the TemplateHandlerOptions.
const handler = new TemplateHandler({
extensions: {
afterCompilation: [
new DataBindingExtension()
]
}
});The following extensions were developed by the community.
Want to see your extension here? Submit a pull request or open an issue.
The easy-template-x-data-binding extension supports updating custom XML files inside Word documents.
This allows using easy-template-x to automatically fill Word forms that uses content controls.
You can configure the template handler behavior by passing an options object to it's constructor.
Below is the list of options along with their types and default values:
const handler = new TemplateHandler({
plugins: createDefaultPlugins(), // TemplatePlugin[]
defaultContentType: TEXT_CONTENT_TYPE, // string
containerContentType: LOOP_CONTENT_TYPE, // string
delimiters: { // Partial<Delimiters>
tagStart: "{",
tagEnd: "}",
containerTagOpen: "#",
containerTagClose: "/"
},
maxXmlDepth: 20,
extensions: { // ExtensionOptions
beforeCompilation: undefined, // TemplateExtension[]
afterCompilation: undefined // TemplateExtension[]
},
scopeDataResolver: undefined // ScopeDataResolver
})To use custom tag delimiters and container marks (used for loops and conditions) specify the delimiters option of the template handler.
For instance, to change from {#open loop} and {/close loop} to {{>>open loop}} and {{<<close loop}} do the following:
const handler = new TemplateHandler({
delimiters: {
tagStart: "{{",
tagEnd: "}}",
containerTagOpen: ">>",
containerTagClose: "<<"
},
})Custom scope data resolvers gives the developer a way to hook into easy-template-x in order to change how it interprets the tag syntax.
For instance, to use Angular-like expressions you can import easy-template-x-angular-expressions by doing the following:
import { createResolver } from "easy-template-x-angular-expressions"
const handler = new TemplateHandler({
scopeDataResolver: createResolver()
})This allows the use of advanced syntax expressions such as:
The library supports the following binary formats:
- Blob (browser)
- Buffer (node)
- ArrayBuffer (browser and node)
In addition to what's described here in the readme file the library exports many more types and functions. While you are free to use them as you see fit please note that anything not documented in the readme file is considered an internal implementation detail and may break between minor versions, use at your own risk.
This library was originally developed as part of an app for non-English speaking k-12 teachers. As such it assumes the template editors do not necessarily have technical background and certainly no programming experience.
In order to stay friendly for such potential users it keeps the template syntax as simple as possible, limiting the required knowledge to {tags} and {#loop tags}{/loop tags} alone (and can be customized to support an alternative, potentially simpler syntax, such as {>>loop tags}{<<loop tags}).
For the same reason it supports tags with whitespace and any unicode supported alphabet such as {שם התלמיד} or {اسم المعلم}.
If your template does not need to meet such requirements, especially if they are meant to be edited by developers you can adopt a more sophisticated alternative syntax.
There are already some very good templating libraries out there, most notably these two:
easy-template-x takes great inspiration from both. It aspires to take the best
out of both and to add some good of it's own. Hopefully it will serve you
well :)
The change log can be found here.