xslt 1.6.1

dotnet tool install --global xslt --version 1.6.1
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local xslt --version 1.6.1
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=xslt&version=1.6.1
                    
nuke :add-package xslt --version 1.6.1
                    

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
1.6.1 38 8/4/2026
1.6.0 56 7/31/2026
1.5.0 64 7/27/2026
1.4.25 64 7/17/2026
1.4.24 61 7/14/2026
1.4.23 83 7/12/2026
1.4.22 75 7/10/2026
1.4.21 69 7/9/2026
1.4.20 59 7/9/2026
1.4.19 72 7/9/2026
1.4.18 65 7/8/2026
1.4.17 71 7/7/2026
1.4.16 78 6/30/2026
1.4.15 80 6/25/2026
1.4.14 85 6/22/2026
1.4.13 81 6/21/2026
1.4.12 83 6/19/2026
1.4.11 87 6/18/2026
1.4.10 87 6/17/2026
1.4.9 80 6/17/2026
Loading failed

### Fixes

- **A typed global `xsl:variable`/`xsl:param` with an optional type (`as="xs:T?"` / `as="xs:T*"`) whose sequence-constructor body executes but produces nothing now binds the empty sequence, not the empty string.** A body such as `<xsl:if test="…">` that does not fire, or `<xsl:for-each select="()">`, produced no content; for a type that permits the empty sequence the value must be `()`. The engine bound `""`, so a later value comparison atomized the variable as `xs:string` and raised a spurious `XPTY0004` (e.g. `$v lt 65536`). Both the eager and the lazily-initialized global-binding paths are corrected; the local-variable path already behaved correctly. Reported by Martin Honnen (XSpec `version-utils.xsl` `x:saxon-version`, which is empty for a non-Saxon processor). Requires the companion PhoenixmlDb.XQuery release for full XPath 3.1 §3.7.1 empty-operand comparison semantics, but this fix alone resolves the reported error.

- **A single-step `node()` kind-test pattern with a predicate (e.g. `match="node()[self::x]"`) now evaluates the predicate instead of matching on node kind alone.** The engine short-circuited on node kind for `node()`, silently dropping any predicate, so `node()[pred]` behaved like bare `node()` — matching nodes the predicate should reject and, at higher priority, pre-empting more specific template rules. Now mirrors the (already-correct) `root()` pattern handling. Reported by Martin Honnen (XSpec `gather-specs.xsl`, `match="node()[x:is-user-content(.)]"`). The sibling `document-node()[pred]` / `document-node(element(E))[pred]` forms had the same predicate-dropping short-circuit and are fixed alongside it. No effect on bare `node()`/`document-node()` or on `element()`/`attribute()`/name-test patterns.

### Packaging

- Exception stack traces from shipped assemblies no longer embed the absolute build-machine path (a `PathMap` maps the repo root to a repo-relative prefix, so a frame reads `phoenixmldb-xslt/src/…` instead of a local filesystem path). Line numbers are preserved. Release builds only.