xslt 1.6.6
See the version list below for details.
dotnet tool install --global xslt --version 1.6.6
dotnet new tool-manifest
dotnet tool install --local xslt --version 1.6.6
#tool dotnet:?package=xslt&version=1.6.6
nuke :add-package xslt --version 1.6.6
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.7 | 46 | 8/24/2026 |
| 1.6.6 | 55 | 8/23/2026 |
| 1.6.5 | 53 | 8/22/2026 |
| 1.6.4 | 82 | 8/16/2026 |
| 1.6.3 | 66 | 8/14/2026 |
| 1.6.2 | 57 | 8/13/2026 |
| 1.6.1 | 71 | 8/4/2026 |
| 1.6.0 | 73 | 7/31/2026 |
| 1.5.0 | 74 | 7/27/2026 |
| 1.4.25 | 77 | 7/17/2026 |
| 1.4.24 | 72 | 7/14/2026 |
| 1.4.23 | 90 | 7/12/2026 |
| 1.4.22 | 83 | 7/10/2026 |
| 1.4.21 | 75 | 7/9/2026 |
| 1.4.20 | 65 | 7/9/2026 |
| 1.4.19 | 80 | 7/9/2026 |
| 1.4.18 | 71 | 7/8/2026 |
| 1.4.17 | 77 | 7/7/2026 |
| 1.4.16 | 83 | 6/30/2026 |
| 1.4.15 | 87 | 6/25/2026 |
Two engine fixes, both found by running the XSpec suite rather than the conformance corpora,
and both in the same family: a name or a namespace that is correct in the source but absent by
the time the engine looks for it.
Together they moved XSpec from 36 suites completing to 39, and from 160 assertions actually
executed to 190. Twenty-one suites advanced a stage; none regressed.
### A typed body's captured output keeps its namespace declarations
A template or variable with an `as=` type captures its body by serializing it and reparsing the
text. The wrapper's namespace declarations were built from the LIVE output scopes — but the
reparse happens after the body has finished and those scopes have popped. A prefix used inside
the captured chunk could therefore be missing from the wrapper, the reparse failed with
`'x' is an undeclared prefix`, and the failure was swallowed: the chunk came back as a plain
string. The typed template then reported
XTTE0505: type String does not match declared type Element
which names a type mismatch and never mentions namespaces. That distance between cause and
symptom is why seven hand-written reproductions all passed — each constructed its elements
INSIDE the capture, where the serializer emits the declarations. It only breaks when elements
are COPIED in, carrying a prefix but not its binding.
The wrapper is now backstopped with the stylesheet's own prefix bindings, which are in scope
for anything the stylesheet could have constructed.
### `key()` resolves a prefixed name across module boundaries
`key('ns:name', …)` failed with `XTDE1260` ("key has not been defined") when the calling module
bound the prefix to a different URI than the module that declared the key — a normal situation
in a multi-module stylesheet, and the shape XSpec generates. Resolution now falls back to an
unambiguous match on the local name when the qualified lookup misses, which is a fallback and
not a relaxation: it applies only when exactly one declared key has that local name.
This cleared all 27 XSpec suites that were stopping on `XTDE1260`.
### Notes
`PhoenixmlDb.Core` is republished at 1.6.6 unchanged under the uniform-version policy. The real
changes at this number are here and in `PhoenixmlDb.XQuery` (`fn:partition`, the `fn` lambda
shorthand, and `fn:parse-html` reporting `FODC0006` instead of returning its input escaped).
Also in this release, but affecting the test harness rather than the engine: the QT3 runner now
reads the corpus's `<module>` declarations, so `import module` resolves. QT3 module-resolution
errors went 188 -> 40 and the pass rate 92.57% -> 92.76%.