fix: stop node namespace prefix parameter ordering in readStopNodeData

[iruizsalinas]

Purpose / Goal

Fix incorrect parameter ordering in readStopNodeData that breaks stop node tracking when the tag has a namespace prefix.

Type

• Bug Fix

readStopNodeData calls readTagExp(xmlData, i, '>') at line 760, but '>' ends up in the removeNSPrefix parameter instead of closingChar. Since it's truthy, namespace prefixes get stripped from opening tags inside the stop node, while closing tags keep them. This throws off openTagCount because opens and closes no longer match.

const parser = new XMLParser({ stopNodes: ["root.ns:code"] });
const result = parser.parse(
  "<root><ns:code>safe <ns:code>nested</ns:code> still raw</ns:code></root>"
);
// result.root["ns:code"] should be "safe <ns:code>nested</ns:code> still raw"
// but instead the stop node exits early at the inner </ns:code>

The fix is changing readTagExp(xmlData, i, '>') to readTagExp(xmlData, i, false) since closingChar already defaults to ">".

[amitguptagwl]

Thanks for your effort and time. Let me test it with some tests and then I'll check the PR. Probably on coming monday