Eli Babila

Hi, I'm not familiar with it, and need to check it to evaluate the effort/benefit.

Hi, Vim and node-inspect connect on port 9514. So, that might be of these reasons : - port 9514 is not available - this is the second plugin instance you...

Youre right its in the roadmap (Watches / Open/Close properties). I'm not familiar with any standard implementation for such component in (n)vim, it has to be created from scratch.

Thanks, I've also looked at these before in my research, they don't really fit unless doing some serious modifications. Note a component for displaying the variables must be dynamic -...

It could be ts, though In a glance I suspect the problem is in the session file (which stores the session between vim instances) or compatibility. Can you post your...

the session and the :version output looks ok; I'll need to run a ts setup to try this. About the second issue, repl commands were not going through the plugin...

Thanks, Yes I can confirm it is because of ts; the breakpoints are set on a js file which needs to be resolved to a ts location (probably using sourcemaps)....

hi, it seems `nodeinspect#OnNodeInspectEnter` autocmd is not called for some reason. It sets up the watches and icons upon vim startup (see last line in plugin/nodeinspect.vim). It seems the plugin/nodeinspect.vim...

Hi, I've successfully tried a one-line script as above in vim 8.2. I suspect Vim9 could be the issue, I'll try and find some time to finally update and check...