stacks-cli
stacks-cli copied to clipboard
WeiChiaChang
Fatal error on startup
stacks-cli version: 0.1.42
node version: 8.9.1 32bits
steps to reproduce: simply run stacks-cli after installing it with npm i -g stacks-cli
error:
/usr/local/lib/node_modules/stacks-cli/bin/cli.js:16
const wappalyzer = require('wappalyzer')(options);
TypeError: Class constructor Driver cannot be invoked without 'new'
at Object.<anonymous> (/usr/local/lib/node_modules/stacks-cli/bin/cli.js:16:41)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
installed versions of dependencies:
npm ls --depth=0
[email protected] /usr/local/lib/node_modules/stacks-cli
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]
mitigation: if I downgrade to wappalyzer 5.1.6 it works.
I faced the same issue with node v8.7.0. The suggested mitigation worked for me. Seems like this is a compatibility issue with [email protected].
same for for me:
➜ ~ stacks-cli
/usr/local/lib/node_modules/stacks-cli/bin/cli.js:16
const wappalyzer = require('wappalyzer')(options);
^
TypeError: Class constructor Driver cannot be invoked without 'new'
at Object.<anonymous> (/usr/local/lib/node_modules/stacks-cli/bin/cli.js:16:41)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
➜ ~ node -v
v8.9.1
I think by now we know it is not related to any Node version or OS :) As @sbmthakur said, it looks like it is [email protected]
Hello all, thanks for all of your time and patience at first 🙏, just like @sbmthakur and @karli2000 said, it seems have some conflict with [email protected] this version, so I just downgraded it to @5.1.6 and released [email protected] already.
Actually I didn't expect this side project can receive such a huge attentions, so if there's still some potential issues, Pull Request or opening a new issue always welcome, and I will try to figure it out in my spare time, thanks everybody again.
