Dr. Ralf S. Engelschall

I've developed a companion Node module XMLHttpRequest-Cookie (see https://npmjs.org/package/xmlhttprequest-cookie) which wraps round this Node XMLHttpRequest module and adds full and automatic Cookie support.

Yes, I agree. But without a real parser this cannot be achieved easily. For a later version I'll check whether we can use an HTML Parser which generates an AST...

Currently it does not know anything about .wasm files? How should they be handled during inlining? What is the mechanism to inline .wasm files? How are they referenced at all...

The SIGTERM indicates that your OS terminates the prince executable for whatever reasons. Perhaps some resources are exhausted or perhaps an update of your system now causes the shared library...

That's not an issue with "prince", but an issue with Node itself. See the line: ``` node:507) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS...

Well, it means that "prince" is not in $PATH and that node-prince was also unable to determine that NixOS is a Linux environment. So, either you have to install PrinceXML...

I've tried it out: I've created a package.json with a dependency to "prince" and then have run... ``` npm --loglevel=silly i --foreground-scripts ``` ...(with NPM 10.2.3) and the "install" script...

That's not such easy, as the URLs for downloading are heavily depending on the current available operating systems and PrinceXML versions. As a workaround, you can always just install your...

Well, for determining the current version a version.json file could be just placed onto their website. There is no need to publish a whole NPM package. But the main issue...

Sorry, can you be more specific? What "args filter"? When I execute "npm shrinkwrap" followed by "npm ci" I see that he "install" script is executed just fine: ``` $...