Does not work in OSX

[msanand]

Hi,

'devtools-terminal' worked perfectly fine until the move to Native Messaging API. Since then, I've never been able to get it working. I've installed and re-installed everything following the instructions, but all I see when I open terminal is the announcement and instructions to install it.
I really loved having devtools-terminal as it greatly enhanced my dev productivity. Please let me know if I'm missing something or how I can get it working again.

Thanks,
Anand

[petethepig]

Is it Chrome or Chromium? What OS do you use?

[msanand]

Hi Pete,
I use chrome 38.0.2125.111

[msanand]

Chrome 38.0.2125.122 on OS X 10.9.5

[stephanebachelier]

I confirm this does not work on 39.0.2171.13 on OS X 10.9.5

[fungl164]

This works on Yosemite + Chrome - Version 39.0.2171.95 ( see http://stackoverflow.com/a/24981514 )

$ mkdir /tmp/pty.js
$ git clone https://github.com/chjj/pty.js.git /tmp/pty.js
$ vi /tmp/pty.js/src/unix/pty.cc

replace line 39: #include <util.h> with #include "/usr/include/util.h"

$ npm install -g /tmp/pty.js
$ npm install -g devtools-terminal
$ sudo devtools-terminal --install --id=leakmhneaibbdapdoienlkifomjceknl

[msanand]

Thanks for the details, @fungl164 . I tried following the instructions, but I get an error when installing '/tmp/pty.js' from the local directory. Any ideas how I can fix this?

Error details:
npm ERR! addLocal Could not install /tmp/tpy.js
npm ERR! Error: ENOENT, stat '/tmp/tpy.js'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Darwin 13.4.0
npm ERR! cwd /private/tmp/pty.js
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! path /tmp/tpy.js
npm ERR! code ENOENT
npm ERR! errno 34

[fungl164]

@msanand I just noticed something peculiar in /tmp/tpy.js vs /tmp/pty.js.

I suspect it's a simple typo on the command. Give this a try npm install -g /tmp/pty.js

[brschwar]

I am using OSX: 10.10.1, Chrome: 40.0.2214.91, Node: 0.10.35

I am able to install devtools terminal. Note: pty.js now seems to be pointing to the correct path:
chjj/pty.js@61acd15

I can run devtools-terminal after installing globally and adding the ID (which now gives me a "Chrome Native Messaging host application installed successfully"):
$ devtools-terminal
info - socket.io started

However, I still see the welcome screen with the Native Messaging API messaging instead of a prompt. Is anyone else still getting that Announcement screen?

[tonyjessup]

thx @fungl164 this totally fixed the install. works great running chrome 40.0 on osx 10.10.1

[brschwar]

Got this to work, finally. I assume there may have been an issue accessing the tool's default 8080 port from the browser to the socket server. I'll keep an eye on it, but otherwise, the plugin works like a charm.

[DannyMoerkerke]

I followed @msanand's steps but unfortunately it's still not working for me on OSX 10.10.2, Chrome 41.0.2272.101.
I remember I had it working before but I recently switched to io.js, installed with NVM. Could that be an issue?

[Devric]

my devtool-terminal server is up, and it seems like it can establish an io handshake every time i try to connect

  http://localhost:8080     admin    

it will than create a new auth id

   info  - handshake authorized sSgiOUPtbrvttxIH4C4I 

but the chrome terminal just says connection failed

[chadbailey59]

Having the same problem. @brschwar , did you do anything special to get it to work?

[brschwar]

@chadbailey59

I was able to get it working following the directions on this blog:
http://blog.dfilimonov.com/2013/09/12/devtools-terminal.html

Please note that you will need to install devtools-terminal globally:

 sudo npm install -g devtools-terminal

Then run devtools-terminal which kicks off a socket.io connection.

Next, access the terminal tab from the developer tools and ignore the NPAPI announcement. That's what got me at first - that announcement doesn't go away, instead click on the '...' preferences menu and login to a Remote Connection with the credentials: http://localhost:8080 with a password of admin.

That worked for me - I could then use that panel in the same manner as I was able to before the Native Messaging update. Possible issues may come up if the default port of 8080 is already in use.

[chadbailey59]

Got it. I had sort-of figured that out yesterday, but was hoping I wouldn't have to log in each time. That seriously hampers the usability for me. :(