webview-ui

What problem does it solve?

Pulp's WebView UI layer requires careful coordination between native hosts, embedded or development assets, and a JavaScript bridge; this Skill reduces the friction of iterating, validating, and packaging those WebView-driven panels and tools so developers can prove functionality without misconfiguring the platform or bundler.

Core Features & Use Cases

• Loading modes: guidance for simple inline HTML, embedded bundled assets for offline distribution, and directory-backed dev assets for rapid iteration.
• Bridge contract & runtime: documents the window.pulp messaging patterns, native message handlers, asynchronous JS evaluation, and AssetManager usage to register embedded resources.
• Monaco integration: prescribes an ESM bundling workflow, worker file handling, and how to point Monaco worker URLs so editor features and CSS load correctly.
• Platform notes & validation: explains the PULP_BUILD_WEBVIEW opt-in, platform-specific requirements for macOS, Windows, and Linux, and focused test/build targets for validation.
• Use case: quickly iterate a Monaco-based in-app editor during development using directory-backed assets, then produce an embedded, offline-ready bundle for shipping.

Quick Start

Build the WebView test target with PULP_BUILD_WEBVIEW=ON, run the focused pulp-test-webview test, and inspect the native host bridge messages to confirm the page reaches editor ready.