node_xslt
node_xslt copied to clipboard
bsuh
Cannot install on Windows XP
I' ve just installed node.js v0.8.6. After that I open a cmd.exe and I write: npm install node_xslt I'got the following errors:
npm http GET https://registry.npmjs.org/node_xslt npm http 304 https://registry.npmjs.org/node_xslt
[email protected] preinstall C:\Proyectos\nodetest\node_modules\node_xslt node-waf distclean || (exit 0); node-waf configure build
No se esperaba node-waf en este momento.
npm ERR! [email protected] preinstall: node-waf distclean || (exit 0); node-waf c onfigure build
npm ERR! cmd "/c" "node-waf distclean || (exit 0); node-waf configure build" f
ailed with 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is most likely a problem with the node_xslt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf distclean || (exit 0); node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls node_xslt
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 5.1.2600 npm ERR! command "C:\Archivos de programa\nodejs\node.exe" "C:\Archivos de programa\nodejs\node_modules\npm\bin\npm-cli.js" "install" "node_xslt" npm ERR! cwd C:\Proyectos\nodetest npm ERR! node -v v0.8.6 npm ERR! npm -v 1.1.48 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! C:\Proyectos\nodetest\npm-debug.log npm ERR! not ok code 0
I think it has something to do with the fact that node.js v0.8.6 now uses the gyp build system instead of node-waf? Or this module only works under linux?
Thanks in advance!
Under Ubuntu 12.04 with node -v v0.8.8 and npm -v 1.1.59 I could install it without any problem, so it's not because of node-waf.
@bsuh You reopened this because you're looking at adding Windows support (saw the Debian dependencies)?
I don't work on this project any more. I closed it, because there was no way to fix it at the time. Then I reopened it on second thought, because it is a valid issue.
To be clear, are you considering moving the dependencies to use node-gyp or did you just reopen as a placeholder? I'm in a position that I'd entertain paying for a good xslt engine for node.js The only viable one I've found so far is VERY touchy and requires Java installed so I can't run it as a pure Node.js app, but would have to use a container.
I recommend checking this one out (not sure about Windows and even less sure about Windows XP...): https://github.com/albanm/node-libxslt. Works on latest NodeJS too.
