chrome-remote-interface | Chrome Debugging Protocol interface for Node.js | Code Inspection library

by cyrus-and JavaScript Version: 0.32.2 License: MIT

X-Ray Key Features Code Snippets(2)Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | chrome-remote-interface Summary

chrome-remote-interface is a JavaScript library typically used in Code Quality, Code Inspection, Nodejs applications. chrome-remote-interface has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can install using 'npm i ox-chrome-remote-interface' or download it from GitHub, npm.

Chrome Debugging Protocol interface for Node.js

Support

Quality

Security

License

Reuse

Support

chrome-remote-interface has a medium active ecosystem.

It has 3994 star(s) with 329 fork(s). There are 80 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 461 have been closed. On average issues are closed in 35 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chrome-remote-interface is 0.32.2

Quality

chrome-remote-interface has 0 bugs and 0 code smells.

Security

chrome-remote-interface has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chrome-remote-interface code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chrome-remote-interface is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

chrome-remote-interface releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed chrome-remote-interface and discovered the below as its top functions. This is intended to give you an instant insight into chrome-remote-interface implemented functionality, and help decide if they suit your requirements.

Inspects the LDAP command .
Performs an external request to the external transport .
Wraps functions in a promise
Add commands to domain
Loads the history file
Decorate an event .
Provides a wrapper in CDP
Fetch remote protocol
Decorate the provided object with parameters
new API

Get all kandi verified functions for this library.

chrome-remote-interface Key Features

No Key Features are available at this moment for chrome-remote-interface.

chrome-remote-interface Examples and Code Snippets

Examples

JavaScript

Lines of Code : 79

License : Permissive (MIT)

Copy

const CRI = require('chrome-remote-interface')
const { RemoteChromeWARCWriter, RemoteChromeCapturer } = require('node-warc')

;(async () => {
  const client = await CRI()
  await Promise.all([
    client.Page.enable(),
    client.Network.enable(),

Is there a way to open html in a browser in node

JavaScript

Lines of Code : 51

License : Strong Copyleft (CC BY-SA 4.0)

Copy

function scrape_content() {
    const http = require('https')

    const options = {
        hostname: 'stackoverflow.com',
        port: 443,
        path: '/questions/71363220/is-there-a-way-to-open-html-in-a-browser-in-node',
        me

Community Discussions

Trending Discussions on chrome-remote-interface

Get response of a API request made using chrome-remote-interface

chrome-remote-interface socket hang up

NodeJS - Error: connect ECONNREFUSED 127.0.0.1:port (chrome-remote-interface)

Capture requests (XHR, JS, CSS) from embedded iframes using devtool protocol

QUESTION

Get response of a API request made using chrome-remote-interface

Asked 2022-Jan-31 at 13:14

I want to get the response data for the particular API call using chrome-remote-interface. I am not sure how to print the response. I am able to get the APIs that are being called using the demo code available in their GitHub repo.

Mentioned a screenshot that I need from Chrome DevTools.

...

ANSWER

Answered 2022-Jan-31 at 13:14

You can use Network.getResponseBody to fetch the body of the response you want. See this minimal example (I changed the target URL because the one you used wasn't immediately fetched, at least for me):

Source https://stackoverflow.com/questions/70926015

QUESTION

chrome-remote-interface socket hang up

Asked 2021-Jun-28 at 18:21

I try to remote debug a WebView on android.

I already goth the process ID with this command adb shell grep -a webview_devtools_remote /proc/net/unixc
Then i made a port forwarding with this command forward tcp:9483 localabstract:webview_devtools_remote_
When i access http://localhost:9483 in my browser i get a link to chrome://inspect -> it is working

But when i try to connect with the chrome-remote-interface package i get a stocket hang up error

This is the code i tyred

...

ANSWER

Answered 2021-Jun-28 at 18:21

setting this option solves the problem local: true

Source https://stackoverflow.com/questions/68160250

QUESTION

NodeJS - Error: connect ECONNREFUSED 127.0.0.1:port (chrome-remote-interface)

Asked 2020-Nov-11 at 16:53

I made a script using chrome-launcher and chrome-remote-interface to save a webpage to pdf using Chrome.

It works without any issue on my Windows machine, but when I try it on CentOS 7, I obtain the following error and I can't figure out why. Both use Chrome v86.

On Windows I use NodeJS v12.18.4 On Linux I tried both v15.1 and v12.19

SELinux status: disabled

I tried to check if other applications were using the port in the error and there weren't any.

...

ANSWER

Answered 2020-Nov-11 at 16:53

I tried to use the launchChrome() function by itself and found that it was the issue. After some research I found the solution. I had to add '--no-sandbox' in the chromeLauncher.launch flags.

Here the fully working code:

Source https://stackoverflow.com/questions/64788142

QUESTION

Capture requests (XHR, JS, CSS) from embedded iframes using devtool protocol

Asked 2020-Aug-19 at 12:49

For the context, I am developing a synthetic monitoring tool using Nodejs and puppeteer. For each step of a defined scenario, I capture a screenshot, a waterfall and performance metrics.

My problem is on the waterfall, I previously used puppeter-har but this package is not able to capture request outside of a navigation. Therefore I use this piece of code to capture all interesting requests :

...

ANSWER

Answered 2020-Aug-19 at 12:49

I was looking on the wrong side all this time. The chrome network events are correctly captured, as I would have seen earlier if I checked the "events" variable earlier. The problem comes from the "chrome-har" package that I use on :

Source https://stackoverflow.com/questions/63357370

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chrome-remote-interface

Install globally (-g) to just use the bundled client.
An instance of either Chrome itself or another implementation needs to be running on a known port in order to use this module (defaults to localhost:9222).

Support

In both the REPL and the regular API every object of the protocol is decorated with the meta information found within the descriptor. In addition The category field is added, which determines if the member is a command, an event or a type.

Find more information at: