Skip to content

After installing globally node-vim-inspector does not exist as a command. #4

Closed
chevex opened this Issue Feb 27, 2014 · 12 comments

5 participants

@chevex
chevex commented Feb 27, 2014

It's not a $PATH issue because I can install other modules globally (such as node-inspector) and their global commands work fine.

I also tried "vim-inspector" by itself but it still wasn't found.

@sidorares
Owner

It seems that latest version on npm is much older than latest source on github. I'll push it and update documentation if required. Thanks for posting!

@sidorares
Owner

please try with vimdebug@0.1.1

@petermoser

I'm having the same issue, it looks like the npm vim-node-debugger is still at version 0.0.1!

@sidorares
Owner

@petermoser it might be npm problem - try to install with npm install vimdebug@0.1.1

@dan-santana

I installed vimdebug@0.1.1 and still can't find any command on terminal...

  • EDIT -

Well, I found it, but when I try to set a breakpoint, it throws this:

/usr/lib/node_modules/vimdebug/node_modules/tmp/lib/tmp.js:260
throw err;
^
TypeError: Cannot read property 'dc' of undefined
at /usr/lib/node_modules/vimdebug/lib/vim-connection.js:48:9
at VimClient.eventHandlers.keyAtPos (/usr/lib/node_modules/vimdebug/node_modules/vim-netbeans/lib/vim-client.js:385:5)
at VimClient._processEvent (/usr/lib/node_modules/vimdebug/node_modules/vim-netbeans/lib/vim-client.js:298:23)
at VimClient._onMessage (/usr/lib/node_modules/vimdebug/node_modules/vim-netbeans/lib/vim-client.js:239:9)
at Array.forEach (native)
at VimClient._onData (/usr/lib/node_modules/vimdebug/node_modules/vim-netbeans/lib/vim-client.js:220:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:746:14)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:408:10)

@sidorares
Owner

just tried version from git master (works ok) and npm (broken, installed v0.0.1 for some reason). I'll update npm package, meanwhile feel free to use version from github ( you can just do npm install -g https://github.com/sidorares/node-vim-debugger/tarball/v0.1.1 )

@petermoser
@sidorares
Owner
@petermoser
@rhalff
rhalff commented Jul 3, 2014

hi, I experience the same issue:

$ npm i vimdebug -g
npm http GET https://registry.npmjs.org/vimdebug
npm http 200 https://registry.npmjs.org/vimdebug
npm http GET https://registry.npmjs.org/vimdebug/-/vimdebug-0.0.1.tgz
npm http 200 https://registry.npmjs.org/vimdebug/-/vimdebug-0.0.1.tgz
npm http GET https://registry.npmjs.org/v8-debugger/0.0.1
npm http GET https://registry.npmjs.org/vim-netbeans
npm http GET https://registry.npmjs.org/tmp/0.0.20
npm http GET https://registry.npmjs.org/source-map
npm http 304 https://registry.npmjs.org/source-map
npm http 200 https://registry.npmjs.org/tmp/0.0.20
npm http GET https://registry.npmjs.org/tmp/-/tmp-0.0.20.tgz
npm http 200 https://registry.npmjs.org/v8-debugger/0.0.1
npm http GET https://registry.npmjs.org/v8-debugger/-/v8-debugger-0.0.1.tgz
npm http 200 https://registry.npmjs.org/vim-netbeans
npm http GET https://registry.npmjs.org/vim-netbeans/-/vim-netbeans-2.0.2.tgz
npm http 200 https://registry.npmjs.org/tmp/-/tmp-0.0.20.tgz
npm http 200 https://registry.npmjs.org/v8-debugger/-/v8-debugger-0.0.1.tgz
npm http 200 https://registry.npmjs.org/vim-netbeans/-/vim-netbeans-2.0.2.tgz
npm http GET https://registry.npmjs.org/amdefine
npm http 304 https://registry.npmjs.org/amdefine
vimdebug@0.0.1 /home/rhalff/.node/lib/node_modules/vimdebug
├── vim-netbeans@2.0.2
├── v8-debugger@0.0.1
├── tmp@0.0.20
└── source-map@0.1.34 (amdefine@0.1.0)

The version being installed is 0.0.1, when I look at the npm site this is also the last known version:

https://www.npmjs.org/package/vimdebug

When I do npm info vimdebug, I get:

npm http GET https://registry.npmjs.org/vimdebug
npm http 304 https://registry.npmjs.org/vimdebug

{ name: 'vimdebug',
  description: 'vim-netbeans based debugger',
  'dist-tags': { latest: '0.0.1' },
  versions: [ '0.0.1', '0.1.1' ],
  maintainers: 'sidorares <sidorares@yandex.com>',
  time: 
   { modified: '2014-02-28T00:23:24.484Z',
     created: '2013-07-22T01:28:11.869Z',
     '0.0.1': '2013-07-22T01:28:19.454Z',
     '0.1.1': '2014-02-28T00:23:24.484Z' },

Maybe the problem is 'dist-tags': { latest: '0.0.1' } ?

Anyway, when I do npm install vimdebug@0.1.1 -g it works just fine.

@sidorares
Owner

Wow, { latest: '0.0.1' } looks very strange. It seems that most of npm publish succeeded except for tagging latest. I'll try to push my local changes and see if it fixed by next update. Thanks for investigation, likely most who tried experienced same issue. By the way - if you keen to contribute I'm happy to give publish access

@sidorares
Owner

seems to be fixed with recently published versions

@sidorares sidorares closed this Aug 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.