fontoxpath-module-loader v1.0.2

fontoxpath-module-loader

Loads XQuery modules into fontoxpath and does something with the result. Can be easily configured to load that module from disk, or from a REST endpoint, or whatever else async stuff you have.

Exposes the evaluateXPath function which is similar to fontoxpath.evaluateXPath, except that you give it the location of your "main" XQuery module and it will try to resolve any "library" XQuery modules from there.

Use

import { evaluateXPath, eva } from 'fontoxpath-module-loader';

const result = await evaluateXPath(
	// Given a target location and referrer, return the location.
	(referrer, target) => path.resolve(path.dirname(referrer), target),

	// Given a target location, return the contents of that XQuery module
	(target) => fs.readFileSync(target, 'utf8'),

	// The location of the main XQuery module
	'my-module-file.xqm'
);

Where my-module-file.xqm could contain, for example:

import module namespace foo = "https://foo.bar" at "./my-other-xquery-example.xql";

foo:do-something()

evaluateXPath()

Runs a query and returns the result to you. Is the same as fontoxpath.evaluateXPath with exception of the first three arguments:

Please revise the fontoxpath documentation for the other arguments of evaluateXPath:

Returns a node, string, boolean, number, array, object or null based on the expression in your XQuery module file.

evaluateUpdatingExpression()

Runs a query, updates the given DOM in place, and potentially also returns a result to you. Is the same as fontoxpath.evaluateUpdatingExpression with exception of the first three arguments:

Please revise the fontoxpath documentation for the other arguments of evaluateUpdatingExpression:

Will apply any updates as per your XQUF expression to the given contextNode. Additionally, your XQUF may return something which results in this function resolving to that node, string, number, similar to what evaluateXPath would return.