Skip to content
pubscout

webkit_inspection_protocol

1.2.1, released 3 years ago by google.dev

A client for the Chrome DevTools Protocol to talk to debuggers.

$ flutter pub add webkit_inspection_protocol
Source repository

What it does

The package acts as a client for the Chrome DevTools Protocol (previously Webkit Inspection Protocol). It is used to communicate with and control Chrome DevTools-based debuggers.

AI-written summary of version 1.2.1, based on the package's README and metadata. Report an inaccuracy

Use it when

  • You need to build tooling that talks to Chrome DevTools-based debuggers.
  • You want to programmatically interact with browser tabs and debugging domains like Runtime or Debugger.

Skip it when

  • You are building standard application features unrelated to browser debugging.
  • You need an official Google-supported product.

Strengths

  • Provides direct client support for the Chrome DevTools Protocol.
  • Supports retry mechanisms and custom error handling for connections.

Weaknesses

  • Not an official Google product.
  • Documentation outside of the basic protocol reference is minimal.

Setup

Kind
Pure Dart
Effort
Low
Code generation
No
Direct dependencies
1

Not documented

Alternatives

Packages that do the same job and could replace webkit_inspection_protocol.

  • thunder

    Flutter debug overlay for real-time inspection of HTTP requests and WebSockets.

  • lsp_server

    Dart implementation of the Language Server Protocol for building LSP servers.

  • interceptly

    Client-agnostic network and WebSocket inspector for Flutter with overlay UI, replay, and MCP export

  • peek

    In-app network inspector for Flutter to view and debug requests, responses, and failures.

Works with

Packages commonly used together with webkit_inspection_protocol: ones it builds on, ones built on it, and its own family.