Keep your XSLT running when browsers drop it

Why now

Chrome and other browsers are removing native XSLT (Chrome's announcement):

• Chrome 143 (December 2025): XSLTProcessor and <?xml-stylesheet type="text/xsl"?> are deprecated, with warnings in the console
• Chrome 158 (17 November 2026): XSLT stops working in stable Chrome, except for sites in the origin trial and browsers under the enterprise policy
• Chrome 176 (17 August 2027): the origin trial and the enterprise policy end; XSLT is off everywhere
• Firefox and WebKit support the removal but have not announced dates

This library ensures your XSLT-based applications continue to work regardless of browser support.

Used bySchema Resume, Job Tailor and others: see References.

Find out what breaks

One command scans a project for the XSLT it runs in the browser: pages that call XSLTProcessor, XML documents rendered with <?xml-stylesheet?>, and the stylesheets themselves. Nothing leaves your machine.

npx xslt-migrate-check .

Found 5 XSLTProcessor usages in 2 files
Found 12 XSL stylesheets (10 × XSLT 1.0, 1 × XSLT 2.0, 1 × XSLT 3.0)
Found 3 XML documents rendered with <?xml-stylesheet?>
Chrome compatibility risk: HIGH
Suggested migration: @tradik/xslt-processor

It ends with the one line that fixes each kind of page: a <script> tag for pages that use XSLTProcessor, and the same tag inside an XML document for <?xml-stylesheet?>. Add --fail-on high in a pipeline. The migration how-to walks through every step; the reference lists what it looks for.

Install

npm install @tradik/xslt-processor
# or
yarn add @tradik/xslt-processor
pnpm add @tradik/xslt-processor
bun add @tradik/xslt-processor

Every change is installed and smoke-tested in CI with npm, Yarn 1, Yarn 4 (Plug'n'Play), pnpm and bun (npm run test:package-managers). The XSLT 2.0/3.0 engine installs the same way (yarn add @tradik/xslt3 and so on), and the migration checker runs without installing: npx xslt-migrate-check ., pnpm dlx xslt-migrate-check . or bunx xslt-migrate-check ..

The library itself has no dependencies. The xslt command line tool also needs jsdom (an optional peer dependency, >=25), see CLI Usage.

Quick start: Browser via CDN (Recommended)

Use a CDN for the easiest browser integration - no build step required:

<!-- jsDelivr (recommended) -->
<script src="https://cdn.jsdelivr.net/npm/@tradik/xslt-processor@1/dist/xslt-processor.browser.min.js"></script>

<!-- or unpkg -->
<script src="https://unpkg.com/@tradik/xslt-processor@1/dist/xslt-processor.browser.min.js"></script>

<script>
  // XSLTProcessor is the native one, or this polyfill when native XSLT is unavailable
  const processor = new XSLTProcessor();

  // Load and transform XML
  const parser = new DOMParser();
  const xslt = parser.parseFromString(xsltString, 'application/xml');
  const xml = parser.parseFromString(xmlString, 'application/xml');

  processor.importStylesheet(xslt);
  const result = processor.transformToFragment(xml, document);
  document.getElementById('output').appendChild(result);
</script>

The bundle defines the global XsltProcessorLib (all module exports) and calls installGlobal(): window.XSLTProcessor is replaced only when the browser has no working native implementation. To always use this implementation, call XsltProcessorLib.installGlobal(true) or use new XsltProcessorLib.XSLTProcessor().

CDN URLs:

Tip: Use @1 for the latest 1.x version, or an exact version such as @1.1.3 for pinning.

ES modules, CommonJS, Node.js and the xslt command line tool are covered in Getting started.