I'm getting Error: Cannot find module '../../www.biopax.org/release/biopax-level3.owl'. I think that the library inconsistently handles every XSD with a targetNamespace that ends in #. For the .js and .d.ts file names, the library replaces # with _, but for the module name, it just removes the #, replacing it with nothing. I added a sample test case in this pull request, and you can try it by disabling this workaround.
Here's what's happening in the test case. I run cxsd on this XSD file. That file imports another XSD file with this targetNamespace that ends in #. When I run cxsd, I get module ./xmlns/pathvisio.org/GPML/2013a, as imported here, and that module has dependency var bp = require('../../www.biopax.org/release/biopax-level3.owl'); (without _), but cxsd creates files with the names ./xmlns/www.biopax.org/release/biopax-level3.owl_.js and ./xmlns/www.biopax.org/release/biopax-level3.owl_.d.ts (with _).
The preinstall and postinstall steps in package.json were needed just to get the versions of cget and cxml that the develop branch of cxsd depends on (they haven't been published to npm yet).
csxd and cxml look pretty cool!
I'm getting
Error: Cannot find module '../../www.biopax.org/release/biopax-level3.owl'. I think that the library inconsistently handles every XSD with atargetNamespacethat ends in#. For the.jsand.d.tsfile names, the library replaces#with_, but for the module name, it just removes the#, replacing it with nothing. I added a sample test case in this pull request, and you can try it by disabling this workaround.Here's what's happening in the test case. I run cxsd on this XSD file. That file imports another XSD file with this
targetNamespacethat ends in#. When I run cxsd, I get module./xmlns/pathvisio.org/GPML/2013a, as imported here, and that module has dependencyvar bp = require('../../www.biopax.org/release/biopax-level3.owl');(without_), but cxsd creates files with the names./xmlns/www.biopax.org/release/biopax-level3.owl_.jsand./xmlns/www.biopax.org/release/biopax-level3.owl_.d.ts(with_).The
preinstallandpostinstallsteps in package.json were needed just to get the versions of cget and cxml that the develop branch of cxsd depends on (they haven't been published to npm yet).