1999 / seamless-node-debug

Seamless node debug with chromium extension

seamless-node-debug

Seamless node debug with chromium extension

Develop

$ # clone repo
$ git clone [email protected]:kino/seamless-node-debug.git
$ cd seamless-node-debug
$ nvm use # in case you're osx user
$ npm install

How-to (live example)

1. Add seamless-node-debug to devDependencies of your app.
2. Clone this project and install chromium extension from "extension" directory to your browser.
3. Send new URLs to Unix socket {os.tmpdir}/seamless-node-debug.sock and browser tab with devtools inspector will be replaced with it immediately.
4. Profit (Вигода)!

How does it all work

This repo consists of three parts: chromium extension, native host app and example of node.js script which communicates to Unix socket. Native host app is started by browser when first extension starts listening to events from this app.

Chromium extension

Chromium extension id is lfmolhfcmmgnacfibfpbemchjmcekkii. Extension listens to native host app which is started by Chromium. Native host app emits new devtools URL to stdout.

Native host app

Python native messaging app which is started by Chromium. It emits new devtools URL to stdout and listens to messages from unix socket.

Example of node.js script

Run it like this: node host/example-send.js chrome-devtools://devtools/remote/... where second argument is URL of devtools tab. It will be transmitted to chromium extension through native host app.

seamless-node-debug's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.