Skip to content
Branch: master
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time

NPM Version NPM Downloads Node.js Version Build Status


API documentation is available atSaxon Node API


An exploration of binding Saxon/C (XSLT 2.0/3.0, XQuery 1.0/3.0, Schema Validation 1.0/1.1 and XPath 2.0/3.0). Professional and enterprise features can be accessed with your license from Saxonica.

Notes on Recent Releases

  • Note: release v0.3.0 Upgraded to 1.2.0 API. Work in progress to mirror the 3.0 xslt methods

Notes on older Releases

  • Note: release v0.2.3 Upgraded to 1.1.2 API.

  • Note: release v0.2.2 Upgraded to 1.1.0 API.

npm install --build-from-source --saxonc_home=<YOUR_SAXONC_HOME>
  • Note: release v0.2.2 is for Saxon/C 1.1.0. For mac two native files need replaced. Where you have Saxon-HEC1.1.0 installed:
      rm `pwd`/../Saxonica/Saxon-HEC1.1.0/Saxon.C.API/SaxonCGlue.h;
      wget --directory-prefix=`pwd`/../Saxonica/Saxon-HEC1.1.0/Saxon.C.API;
      rm `pwd`/../Saxonica/Saxon-HEC1.1.0/Saxon.C.API/SaxonCProcessor.c;
      wget --directory-prefix=`pwd`/../Saxonica/Saxon-HEC1.1.0/Saxon.C.API;
  • Note: release v0.2.1 is linux and mac and pending windows version of Saxon/C 1.0.2

  • Note: release v0.2.0 is linux only pending the release of mac and windows versions of Saxon/C 1.0.1

  • Note: release v0.1.1 is built with nodejs v4.2.x [v4.2.x has Buffer acting like Uint8Array and currently is indistinguishable on the native side yet seems to work for this project]. If you want v0.12.x compatibility stay with v0.0.5. npm will continue with nodejs v4.2.x line and any fixes or features needed by prior versions will be from github branches.

To tell it where the Saxon/C is set the environment variable SAXONC_HOME to path:

export SAXONC_HOME=/home/user/Software/Saxonica/SaxonHEC1.2.0


linux-x64,linux-ia32, darwin-x64 and win32-ia32(no saxon-c 1.0.2 yet).

npm install --fallback-to-build

will first try to find a compatible native prebuilt. If it works you won't need development tools and compilers.

####Building (only if needed; contact me if there is a particular prebuild you would use) If a compatible prebuilt is not found, a number of environment variables are needed. For the build phase, as with integrating Saxon/C interface code in c/c++ applications the jni.h is needed. Set JAVA_HOME and the binding.gyp locates the jni.h from there. Only the headers are used; that comes wth Saxon/C is loaded from it's home folder. The depends on $SAXONC_HOME/rt during runtime and it needs library paths $SAXONC_HOME:$SAXONC_HOME/rt/lib/amd64/jetvm:$SAXONC_HOME/rt/lib/amd64. rt is the runtime that Saxon/C provides. To run it needs the harmony switch and at least nodejs v4.2.x. Make sure there isn't a java path to jvm in front of the Excelsior JET tool in rt folder:

node --harmony saxon-node.js /home/user/testing-grounds/BCL/analyze.xml /home/user/NetBeansProjects/OOBackbone/stylesheets/divconIsSpecies.xsl

Yet this isn't the purpose to run xslt as this small app. The intention is the calling of the API from your applications.

####To test

mocha --harmony --require should
You can’t perform that action at this time.