Inquiry Regarding xpath export Removal

[jhonatan30]

Hello xml-crypto team,

I'm currently updating my project from version 3 to version 6 of the library and noticed that the documentation includes the following example:

var select = require("xml-crypto").xpath;

However, in version 6, the xpath member looks like is not available in the package's exports. Is this correct?

If XPath functionality is still needed, should developers use an external package (e.g., xpath) instead?

Any guidance on the recommended approach for working with XPath in conjunction with xml-crypto in this version would be greatly appreciated.

Thank you.

[srd90]

However, in version 6, the xpath member looks like is not available in the package's exports. Is this correct?

Seems to be correct:

• 3.2.1

  xml-crypto/package.json

  Line 44 in 92bbddf

  "xpath": "0.0.32"

  
  

  xml-crypto/index.js

  Lines 1 to 10 in 92bbddf

  	var select = require("xpath").select;
  	module.exports = require("./lib/signed-xml");
  	module.exports.C14nCanonicalization = require("./lib/c14n-canonicalization").C14nCanonicalization;
  	module.exports.C14nCanonicalizationWithComments = require("./lib/c14n-canonicalization").C14nCanonicalizationWithComments;
  	module.exports.ExclusiveCanonicalization = require("./lib/exclusive-canonicalization").ExclusiveCanonicalization;
  	module.exports.ExclusiveCanonicalizationWithComments = require("./lib/exclusive-canonicalization").ExclusiveCanonicalizationWithComments;
  	module.exports.xpath = function (node, xpath) {
  	return select(xpath, node);
  	};

• 6.0.1

  xml-crypto/src/index.ts

  Lines 1 to 3 in d80e5b7

  	export { SignedXml } from "./signed-xml";
  	export * from "./utils";
  	export * from "./types";

  utils: https://github.com/node-saml/xml-crypto/blob/d80e5b77ade2f72225a2f324d5b54d20f4f4e396/src/utils.ts

  types: https://github.com/node-saml/xml-crypto/blob/d80e5b77ade2f72225a2f324d5b54d20f4f4e396/src/types.ts

---

If XPath functionality is still needed, should developers use an external package (e.g., xpath) instead?

Any guidance on the recommended approach for working with XPath in conjunction with xml-crypto in this version would be greatly appreciated.

Dunno if this qualifies "any guidance" requirement:

@node-saml/node-saml 5.0.1 which was developed by same organization as https://github.com/node-saml/xml-crypto/ seems to be using external xpath to find Signature node(s):

https://github.com/node-saml/node-saml/blob/668cbb67b74f810e80bd090d9c7804a1fdb7b80b/package.json#L68

https://github.com/node-saml/node-saml/blob/668cbb67b74f810e80bd090d9c7804a1fdb7b80b/src/xml.ts#L7

https://github.com/node-saml/node-saml/blob/668cbb67b74f810e80bd090d9c7804a1fdb7b80b/src/xml.ts#L80

to be used for validating SAML signature(s) with SignedXML from xml-crypto 6.0.1

https://github.com/node-saml/node-saml/blob/668cbb67b74f810e80bd090d9c7804a1fdb7b80b/package.json#L64