xslt-processor 4.3.1 → 4.4.0

package/README.md

@@ -62,7 +62,7 @@ const xslt = new Xslt();
 const xPath = xslt.xPath;
 ```
 
-Or ou can import it like this:
+Or you can import it like this:
 
 ```js
 import { XPath } from 'xslt-processor'
@@ -70,6 +70,8 @@ import { XPath } from 'xslt-processor'
 const xPath = new XPath();
 ```
 
+`XPath` class is an external dependency, [living in its own repository](https://github.com/DesignLiquido/xpath). 
+
 If you write pre-2015 JS code, make adjustments as needed.
 
 ### `Xslt` class options
@@ -145,76 +147,11 @@ console.log(parsed.root.users.user); // ["Alice", "Bob"]
 You can simply add a tag like this:
 
 ```html
-<script type="application/javascript" src="https://www.unpkg.com/xslt-processor@3.0.0/umd/xslt-processor.js"></script>
+<script type="application/javascript" src="https://www.unpkg.com/xslt-processor@latest/umd/xslt-processor.js"></script>
 ```
 
 All the exports will live under `globalThis.XsltProcessor` and `window.XsltProcessor`. [See a usage example here](https://github.com/DesignLiquido/xslt-processor/blob/main/interactive-tests/xslt.html). 
 
-### Breaking Changes
-
-#### Version 2
-
-Until version 2.3.1, use like the example below:
-
-```js
-import { Xslt, XmlParser } from 'xslt-processor'
-
-// xmlString: string of xml file contents
-// xsltString: string of xslt file contents
-// outXmlString: output xml string.
-const xslt = new Xslt();
-const xmlParser = new XmlParser();
-const outXmlString = xslt.xsltProcess( // Not async.
-	xmlParser.xmlParse(xmlString),
-	xmlParser.xmlParse(xsltString)
-);
-```
-
-Version 3 received `<xsl:include>` which relies on Fetch API, which is asynchronous. Version 2 doesn't support `<xsl:include>`.
-
-If using Node.js older than version v17.5.0, please use version 3.2.3, that uses `node-fetch` package. Versions 3.3.0 onward require at least Node.js version v17.5.0, since they use native `fetch()` function.
-
-#### Version 1
-
-Until version 1.2.8, use like the example below:
-
-```js
-import { Xslt, xmlParse } from 'xslt-processor'
-
-// xmlString: string of xml file contents
-// xsltString: string of xslt file contents
-// outXmlString: output xml string.
-const xslt = new Xslt();
-const outXmlString = xslt.xsltProcess(
-	xmlParse(xmlString),
-	xmlParse(xsltString)
-);
-```
-
-#### Version 0
-
-Until version 0.11.7, use like the example below:
-
-```js
-import { xsltProcess, xmlParse } from 'xslt-processor'
-
-// xmlString: string of xml file contents
-// xsltString: string of xslt file contents
-// outXmlString: output xml string.
-const outXmlString = xsltProcess(
-	xmlParse(xmlString),
-	xmlParse(xsltString)
-);
-```
-
-and to access the XPath parser:
-
-```js
-import { xpathParse } from 'xslt-processor'
-```
-
-These functions are part of `Xslt` and `XPath` classes, respectively, at version 1.x onward.
-
 ## Introduction
 
 XSLT-processor contains an implementation of XSLT in JavaScript. Because XSLT uses XPath, it also contains an implementation of XPath that can be used
@@ -312,6 +249,71 @@ Use `<xsl:preserve-space>` to preserve whitespace in specific elements, overridi
 3. `xsl:strip-space` applies to remaining matches
 4. By default (no declarations), whitespace is preserved
 
+### Breaking Changes
+
+#### Version 2
+
+Until version 2.3.1, use like the example below:
+
+```js
+import { Xslt, XmlParser } from 'xslt-processor'
+
+// xmlString: string of xml file contents
+// xsltString: string of xslt file contents
+// outXmlString: output xml string.
+const xslt = new Xslt();
+const xmlParser = new XmlParser();
+const outXmlString = xslt.xsltProcess( // Not async.
+	xmlParser.xmlParse(xmlString),
+	xmlParser.xmlParse(xsltString)
+);
+```
+
+Version 3 received `<xsl:include>` which relies on Fetch API, which is asynchronous. Version 2 doesn't support `<xsl:include>`.
+
+If using Node.js older than version v17.5.0, please use version 3.2.3, that uses `node-fetch` package. Versions 3.3.0 onward require at least Node.js version v17.5.0, since they use native `fetch()` function.
+
+#### Version 1
+
+Until version 1.2.8, use like the example below:
+
+```js
+import { Xslt, xmlParse } from 'xslt-processor'
+
+// xmlString: string of xml file contents
+// xsltString: string of xslt file contents
+// outXmlString: output xml string.
+const xslt = new Xslt();
+const outXmlString = xslt.xsltProcess(
+	xmlParse(xmlString),
+	xmlParse(xsltString)
+);
+```
+
+#### Version 0
+
+Until version 0.11.7, use like the example below:
+
+```js
+import { xsltProcess, xmlParse } from 'xslt-processor'
+
+// xmlString: string of xml file contents
+// xsltString: string of xslt file contents
+// outXmlString: output xml string.
+const outXmlString = xsltProcess(
+	xmlParse(xmlString),
+	xmlParse(xsltString)
+);
+```
+
+and to access the XPath parser:
+
+```js
+import { xpathParse } from 'xslt-processor'
+```
+
+These functions are part of `Xslt` and `XPath` classes, respectively, at version 1.x onward.
+
 ## References
 
 - XPath Specification: http://www.w3.org/TR/1999/REC-xpath-19991116

package/index.d.mts

@@ -214,6 +214,11 @@ interface XPathContext {
      * Example: { "atom": "http://www.w3.org/2005/Atom" }
      */
     namespaces?: XPathNamespaces;
+    /**
+     * XSLT version ('1.0', '2.0', '3.0') for version-specific behavior.
+     * Used by functions like json-to-xml() which are only available in XSLT 3.0+
+     */
+    xsltVersion?: string;
 }
 /**
  * Result types that can be returned from XPath evaluation.
@@ -413,6 +418,11 @@ declare class NodeConverter {
      * Create custom functions for XPath context (like key(), document(), etc.).
      */
     private createCustomFunctions;
+    /**
+     * Convert an XPathNode interface tree to actual XNode objects.
+     * This is needed to convert json-to-xml() output to XSLT-compatible nodes.
+     */
+    private convertXPathNodeToXNode;
     /**
      * Convert an XML node to a JSON string representation.
      * This is a simplified implementation of XSLT 3.0's xml-to-json().

package/index.d.ts

@@ -214,6 +214,11 @@ interface XPathContext {
      * Example: { "atom": "http://www.w3.org/2005/Atom" }
      */
     namespaces?: XPathNamespaces;
+    /**
+     * XSLT version ('1.0', '2.0', '3.0') for version-specific behavior.
+     * Used by functions like json-to-xml() which are only available in XSLT 3.0+
+     */
+    xsltVersion?: string;
 }
 /**
  * Result types that can be returned from XPath evaluation.
@@ -413,6 +418,11 @@ declare class NodeConverter {
      * Create custom functions for XPath context (like key(), document(), etc.).
      */
     private createCustomFunctions;
+    /**
+     * Convert an XPathNode interface tree to actual XNode objects.
+     * This is needed to convert json-to-xml() output to XSLT-compatible nodes.
+     */
+    private convertXPathNodeToXNode;
     /**
      * Convert an XML node to a JSON string representation.
      * This is a simplified implementation of XSLT 3.0's xml-to-json().