xslt 1.6.10
See the version list below for details.
dotnet tool install --global xslt --version 1.6.10
dotnet new tool-manifest
dotnet tool install --local xslt --version 1.6.10
#tool dotnet:?package=xslt&version=1.6.10
nuke :add-package xslt --version 1.6.10
xslt
Command-line XSLT 3.0/4.0 processor for .NET. Transform XML documents from the terminal using the PhoenixmlDb XSLT engine.
Installation
dotnet tool install -g xslt
Usage
# Transform XML with a stylesheet
xslt stylesheet.xsl input.xml
# Write output to a file
xslt -o result.html report.xsl data.xml
# Start from a named template (no source needed)
xslt -it main generate.xsl
# Pass parameters
xslt -p year=2026 -p title="Report" style.xsl data.xml
# Read source from stdin
cat data.xml | xslt transform.xsl
# Show timing breakdown
xslt --timing style.xsl large-input.xml
# Validate a stylesheet without running
xslt --dry-run style.xsl
# Stream large files (lower memory)
xslt --stream style.xsl large-input.xml
Features
- XSLT 3.0/4.0 — packages, streaming, maps/arrays, higher-order functions, JSON output
- Multiple output methods — XML, HTML, XHTML, text, JSON, adaptive
- Streaming — process large files without loading into memory
- xsl:result-document — generate multiple output files in one transform
- Parameters — pass values from the command line
- Timing — built-in performance profiling
- Tracing — log template matching, function calls, and built-in rules
Documentation
Full documentation at phoenixml.dev
License
Apache-2.0
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.6.12 | 43 | 8/30/2026 |
| 1.6.11 | 46 | 8/29/2026 |
| 1.6.10 | 50 | 8/27/2026 |
| 1.6.9 | 211 | 8/26/2026 |
| 1.6.8 | 45 | 8/26/2026 |
| 1.6.7 | 59 | 8/24/2026 |
| 1.6.6 | 67 | 8/23/2026 |
| 1.6.5 | 60 | 8/22/2026 |
| 1.6.4 | 87 | 8/16/2026 |
| 1.6.3 | 68 | 8/14/2026 |
| 1.6.2 | 62 | 8/13/2026 |
| 1.6.1 | 72 | 8/4/2026 |
| 1.6.0 | 73 | 7/31/2026 |
| 1.5.0 | 76 | 7/27/2026 |
| 1.4.25 | 78 | 7/17/2026 |
| 1.4.24 | 73 | 7/14/2026 |
| 1.4.23 | 93 | 7/12/2026 |
| 1.4.22 | 83 | 7/10/2026 |
| 1.4.21 | 75 | 7/9/2026 |
| 1.4.20 | 65 | 7/9/2026 |
Consumes PhoenixmlDb.XQuery 1.6.9, which carries the `format-dateTime(@untypedAttr, ...)` fix.
### Nodes from `fn:transform` kept the node but lost its tree
Reported by Martin Honnen via sxq, an XQuery implementation of Schematron. Nodes handed back
with `delivery-format='raw'` arrived stripped of their ancestors:
fn:path() was: /Q{}book[1] /Q{}book[1]
now: /Q{}books[1]/Q{}book[1] /Q{}books[1]/Q{}book[2]
Both results claimed to be the root of their own tree — and, as he noticed, reported the SAME
path, because each was. The cross-store transport carried only the node's own serialization,
and re-anchoring reparsed that into a fresh document, so a `<book>` became a one-element tree
by construction. It now carries the serialized ROOT plus a child-index chain down to the node.
A second fault, independent and not in the report: re-anchoring ran per item, so two siblings
were parsed into two separate copies of their document and would not have shared a parent.
Each distinct root is now parsed once for the whole result, so `$r[1]/.. is $r[2]/..` holds.
His diagnosis pointed at `xsl:evaluate`; that was innocent — `fn:transform` raw with a
stylesheet function that merely selects nodes reproduces it identically.
### `document-node(element(x:report))` matched nothing
Also from Martin Honnen. A name test nested inside a kind test never had its namespace
resolved, so the matcher's "this shouldn't happen" branch returned false and the template
silently matched nothing. `element(x:report)` was broken the same way and unreported.
### Errors report instead of crashing
The CLI printed a clean error line and then rethrew, so .NET appended "Unhandled exception"
and a stack trace on top, exiting 134. It now reports and exits 2. All twelve W3C error codes
that were thrown as bare `InvalidOperationException` now carry an error code and a stylesheet
location.
### Absent-focus guards removed
Four guards claimed to handle an absent focus and could not — they caught an exception type
neither context implementation throws. Making them work breaks W3C `accumulator-061` both ways
it can be attempted, so the escaping error and the sentinel are load bearing. The misleading
code is gone and the behaviour is unchanged; see BUGS.md #17 before making them live.
Xslt.Tests 1310 passed, 0 failed, 1 skipped (1289 at 1.6.9)
XSLT conformance 10237/10630 = 96.30%