Fatal error on startup - Githubissues

ghost commented 6 years ago

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
stacks-cli@0.1.42 /usr/local/lib/node_modules/stacks-cli
├── babel-runtime@6.26.0
├── cfonts@1.1.3
├── chalk@2.3.0
├── cli-table2@0.2.0
├── inquirer@4.0.0
├── meow@3.7.0
├── opn@5.1.0
├── ora@1.3.0
└── wappalyzer@5.2.0

mitigation: if I downgrade to wappalyzer 5.1.6 it works.

karli2000 commented 6 years ago

Same error with node 9.2.0 x64 on Windows 10

kodekracker commented 6 years ago

same error with node v7.10.0 on Ubuntu Linux 16.04

sbmthakur commented 6 years ago

I faced the same issue with node v8.7.0. The suggested mitigation worked for me. Seems like this is a compatibility issue with wappalyzer@5.2.0.

midgethoen commented 6 years ago

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

gchokov commented 6 years ago

Same here.

fr0stxm commented 6 years ago

Same here running on Mac OS 10.12.6

➜ node -v v7.8.0

uniacid commented 6 years ago

Same here on OSX 10.13.1 / Node v8.9.1

LaurensN commented 6 years ago

Same for OSX 10.12.6 / Node v7.5.0

zezic commented 6 years ago

Same on Ubuntu 16.04 / Node v8.2.1

drpgdigital commented 6 years ago

Same for OSX 10.12.16 / Node v8.9.1

karli2000 commented 6 years ago

I think by now we know it is not related to any Node version or OS :) As @sbmthakur said, it looks like it is wappalyzer@5.2.0

WeiChiaChang commented 6 years ago

Hello all, thanks for all of your time and patience at first 🙏, just like @sbmthakur and @karli2000 said, it seems have some conflict with wappalyzer@5.2.0 this version, so I just downgraded it to @5.1.6 and released stacks-cli@0.1.44 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.

LaurensN commented 6 years ago

Nice work @WeiChiaChang, fixed over here 👍

WeiChiaChang / stacks-cli

Fatal error on startup #5