Status

[bpstrngr]

I've managed to revive this switching to node V8 and editing the used socket.io version to require the EventEmitter (although i was looking for another extension i used 2 years ago which had a quick-commands bar and just looked differently, but it disappeared from the planet somehow).

I also ran the "sudo devtools-terminal --install --id=mdkaidkdlmfilafmhllmgabjdbliaahk" to support the native massaging api as suggested in the opening panel's "important announcement" before finding people mentioning how to fix an "empty screen" by logging in to localhost as a remote connection which also had to be done afterwards.

All i saw the --install option do is create an empty folder under /etc/opt:

.  ..

So I'm confused if this is even required still? I'm using chrome os, and it's the only thing in /etc/opt/chrome, so i doubt it's even the right place for was supposed to be placed there, and only the next step of logging in seemed to actually do something anyway.

Also: what do you think is the latest nodejs version that the backend can compile with? I only tried down to V14 and that meets node-gyp errors on install already.

I'd definitely be interested in maintaining this (or the other extension i failed to find), so i would take further pointers about what should be fixed here. Up/down arrows and ctrl-r doesn't seem to work, is that a new phenomenon?

[eternal191]

Have you tried to enable the chrome terminal using this method?
https://remysharp.com/2017/02/10/browser-terminals

[bpstrngr]

@eternal191 that experiment has not been available in devtools for a while.