vtop: SyntaxError crash

Hi, I’m getting a SyntaxError crash when running vtop, the error message is as follows:

evalmachine.<anonymous>:2
vtop@0.5.7 | MIT | deps: 10 | versions: 47
^

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:74:7)
    at createScript (vm.js:246:10)
    at Object.runInNewContext (vm.js:291:10)
    at safeEval (/usr/lib/node_modules/vtop/node_modules/safe-eval/index.js:13:6)
    at /usr/lib/node_modules/vtop/upgrade.js:25:24
    at ChildProcess.exithandler (child_process.js:273:7)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:947:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:236:5)

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 30
Comments: 15 (5 by maintainers)

Commits related to this issue

upgrade.js: fix parsing npm info output Closes #121. — committed to williamboman/vtop by williamboman 6 years ago
upgrade.js: fix parsing npm info output Closes #121. — committed to williamboman/vtop by williamboman 6 years ago

Most upvoted comments

🤔…

Anyways, for now I’ve published vtop-node10 which includes #123 and thus support for node@10/npm@6. To install:

$ npm uninstall -g vtop
$ npm install -g vtop-node10
$ vtop

williamboman on May 30, 2018

I’m having the same issue on latest version of macOS 10.13.4, Node.js 10.0.0 and npm 6.0.0.

vinkla on May 7, 2018

This is caused by breaking changes in npm@6 CLI API.

williamboman on May 1, 2018

That worked, thanks!

On Wed, May 30, 2018 at 9:46 AM William Boman notifications@github.com wrote:

🤔…

Anyways, for now I’ve published vtop-node10 which includes #123 https://github.com/MrRio/vtop/pull/123 and thus support for node@10 /npm@6. To install:

$ npm uninstall -g vtop $ npm install -g vtop-node10 $ vtop

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MrRio/vtop/issues/121#issuecomment-393167816, or mute the thread https://github.com/notifications/unsubscribe-auth/ACX2oHMDgs43WKX3xqvm1c-6ICBsln6tks5t3qK8gaJpZM4TsKMD .

tvanantwerp on May 30, 2018

I’m having the same issue in 0.6.1

smukkejohan on Feb 13, 2020

screen shot 2018-06-25 at 9 34 16 am

~Still failing for me.~

I ran my “update everything” script and now it’s working so… update… I have no idea why it’s working now but it is.

jsatk on Jun 25, 2018

This is now fixed in v0.6.0. Thanks for your patience! 😃

MrRio on Jun 23, 2018

Nope, no proxies set up. Never had any issues before with accessing npm or anything else. It’s a small company and I’m the IT manager here, and I try to keep things simple for myself because I don’t have anyone else to help if things break…

On Wed, May 30, 2018 at 9:29 AM William Boman notifications@github.com wrote:

Are you behind a corporate web proxy then? It is not uncommon that corp proxies block npm traffic.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MrRio/vtop/issues/121#issuecomment-393161564, or mute the thread https://github.com/notifications/unsubscribe-auth/ACX2oArVgFT2vYtXt-xVKJL3w4-tKa-wks5t3p6lgaJpZM4TsKMD .

tvanantwerp on May 30, 2018