🥮 mooncakes.io

/

crater-webdriver-bidi

crater-webdriver-bidi

WebDriver BiDi adapter module for crater browser integration

moon add mizchi/crater-webdriver-bidi@0.19.0

Author

Version

0.19.0

License

Apache-2.0

Repository

github.com/mizchi/crater

Last updated

last month

Downloads

28

Dependencies

README

#crater-webdriver-bidi

WebDriver BiDi adapter module for Crater.

This module contains the BiDi server, protocol adapter, and font-enabled launcher used by Playwright and WPT WebDriver integration.

#
ApiError

using @mizchi/crater-webdriver-bidi/contract { type ApiError }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
ApiMethod

using @mizchi/crater-webdriver-bidi/contract { type ApiMethod }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
BidiServer

using @mizchi/crater-webdriver-bidi/webdriver { type BidiServer }

BiDi server state

#
BidiServerConfig

using @mizchi/crater-webdriver-bidi/webdriver { type BidiServerConfig }

BiDi server configuration

#
Capabilities

using @mizchi/crater-webdriver-bidi/contract { type Capabilities }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
ErrorCode

using @mizchi/crater-webdriver-bidi/contract { type ErrorCode }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
PageLoadStrategy

using @mizchi/crater-webdriver-bidi/contract { type PageLoadStrategy }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
ProxyConfig

using @mizchi/crater-webdriver-bidi/contract { type ProxyConfig }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
Rect

using @mizchi/crater-webdriver-bidi/contract { type Rect }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
RpcErrorCode

using @mizchi/crater-webdriver-bidi/rpc { type RpcErrorCode }

Standard JSON-RPC error codes

#
RpcId

using @mizchi/crater-webdriver-bidi/rpc { type RpcId }

JSON-RPC request ID (can be string or number)

#
RpcRequest

using @mizchi/crater-webdriver-bidi/rpc { type RpcRequest }

JSON-RPC request

#
RpcResponse

using @mizchi/crater-webdriver-bidi/rpc { type RpcResponse }

JSON-RPC response

#
Selector

using @mizchi/crater-webdriver-bidi/contract { type Selector }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
Session

using @mizchi/crater-webdriver-bidi/contract { type Session }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
SessionManager

using @mizchi/crater-webdriver-bidi/server { type SessionManager }

Session manager

#
SessionState

using @mizchi/crater-webdriver-bidi/server { type SessionState }

Session state

#
Timeouts

using @mizchi/crater-webdriver-bidi/contract { type Timeouts }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
Viewport

using @mizchi/crater-webdriver-bidi/contract { type Viewport }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WebDriverCommand

using @mizchi/crater-webdriver-bidi/contract { type WebDriverCommand }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WebDriverError

using @mizchi/crater-webdriver-bidi/contract { type WebDriverError }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WebDriverRequest

using @mizchi/crater-webdriver-bidi/contract { type WebDriverRequest }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WebDriverResponse

using @mizchi/crater-webdriver-bidi/contract { type WebDriverResponse }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WebDriverValue

using @mizchi/crater-webdriver-bidi/contract { type WebDriverValue }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
WindowRect

using @mizchi/crater-webdriver-bidi/contract { type WindowRect }

Top-level public API surface for mizchi/crater-webdriver-bidi.

Re-exports come straight from the source packages (contract / rpc / server) rather than the broad webdriver implementation facade, so downstream consumers see a single hop to the real definition. The implementation package is still used for the transport (BidiServer*).

#
parse_method

fn parse_method(method_name : String) -> @mizchi/crater-webdriver-bidi/contract.ApiMethod
ApiMethod?

Source Files

top.mbt

Install

moon add mizchi/crater-webdriver-bidi@0.19.0

WebDriver BiDi adapter module for crater browser integration

0.19.0

Apache-2.0

github.com/mizchi/crater

Updated last month

28 downloads

Dependencies

Powered by MoonBit

Site source Report issue Packages Build queue Skills Statistics

© 2026 mooncakes.io