Cannot read properties of undefined (reading 'lIndex') when parsing template

[mcat95]

Environment

• Version of docxtemplater : 3.31.3
• Used docxtemplater-modules : None needed
• Runner : NodeJS

How to reproduce my problem :

My template is the following: template.zip

With the following js file :

const fs = require('fs');
const PizZip = require('pizzip');
const Docxtemplater = require('docxtemplater');

const content = fs
    .readFileSync(__dirname + "/template.zip", "binary");

const zip = new PizZip(content);
const doc = new Docxtemplater(zip, {
  modules: [],
  delimiters: { start: "{{", end: "}}" },
})
console.log('Good');
//Execution does not reach this point, since it fails to parse the document

I would expect it to :

• not fail. The error message is:

TypeError: Cannot read properties of undefined (reading 'lIndex')
    at /home/marco/Walcu/pedefeprinter/docxtemplater/js/modules/loop.js:331:42
    at Array.some (<anonymous>)
    at LoopModule.postparse (/home/marco/Walcu/pedefeprinter/docxtemplater/js/modules/loop.js:322:15)
    at /home/marco/Walcu/pedefeprinter/docxtemplater/js/parser.js:226:24
    at Array.reduce (<anonymous>)
    at _postparse (/home/marco/Walcu/pedefeprinter/docxtemplater/js/parser.js:225:22)
    at postparse (/home/marco/Walcu/pedefeprinter/docxtemplater/js/parser.js:228:20)
    at /home/marco/Walcu/pedefeprinter/docxtemplater/js/modules/expand-pair-trait.js:268:30
    at Array.reduce (<anonymous>)
    at Object.postparse (/home/marco/Walcu/pedefeprinter/docxtemplater/js/modules/expand-pair-trait.js:248:32)

I noticed that this issue didn't appear in 3.30.0, and bisected the repo to found that the commit which introduced the bug was bccf18b

[edi9999]

Thanks for reporting a detailed issue.

I will take a look and publish a fix within a few hours.

[edi9999]

I've just fixed the issue in version v3.31.5

[edi9999]

The template just contained

{{#ice}}{{/}}

I'm not sure if you are expecting to get anything from this output, but I don't see what you wanted to achieve with this template ?

[mcat95]

Thanks for the quick fix, we really appreciate it!

About the template, I tried to simplified the template as much as I could to make the issue easier to understand. The original template was using the scope to set a variable without printing it to the document, doing something like this:

{{#var2=var1+5}}{{/}}

[edi9999]

Ok, I understand.

Please note that it is also possible to simply write the following in your template and avoid producing the results :

{var2=var1+5}

See this doc : https://docxtemplater.com/docs/angular-parse/#assignments

var expressions = require("angular-expressions");
var assign = require("lodash/assign");

function angularParser(tag) {
    tag = tag
        .replace(/^\.$/, "this")
        .replace(/(’|‘)/g, "'")
        .replace(/(“|”)/g, '"');
    const expr = expressions.compile(tag);
    // isAngularAssignment will be true if your tag contains a `=`, for example
    // when you write the following in your template:
    // {full_name = first_name + last_name}
    // In that case, it makes sense to return an empty string so
    // that the tag does not write something to the generated document.
    const isAngularAssignment =
        expr.ast.body[0] &&
        expr.ast.body[0].expression.type ===
            "AssignmentExpression";

    return {
        get(scope, context) {
            let obj = {};
            const scopeList = context.scopeList;
            const num = context.num;
            for (let i = 0, len = num + 1; i < len; i++) {
                obj = assign(obj, scopeList[i]);
            }
            const result = expr(scope, obj);
            if (isAngularAssignment) {
                return "";
            }
            return result;
        },
    };
}
new Docxtemplater(zip, { parser: angularParser });

[kevit-sagar-nakum]

Hey There,
I am facing the same issue, when you guys will publish this fix on NPM, any ETA for it?
Thanks in advance!!!

[edi9999]

Hello @kevit-sagar-nakum ,

the issue was already published.

However, I mixed up my versions in this thread and also in the CHANGELOG.md

The fix was already published in version 3.31.4