Automattic / Automattic/wp-codebox

Expose browser preview starter through Codebox browser SDK

Open
#1,502 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
16
Forks
4
Avg merge
59m
Merged PRs (30d)
131

Description

Studio Native still has to dynamically import the raw Playground client module and call startPlaygroundWeb during browser preview boot. That keeps a product consumer coupled to Playground internals instead of the Codebox public browser SDK.\n\nNeeded contract:\n- A versioned browser SDK method, e.g. window.wpCodeboxBrowser.v1.startBrowserPreview(...) or equivalent, that accepts the Codebox preview boot DTO/session boot contract and returns the browser client/session handle currently returned by startPlaygroundWeb.\n- The product should not need to read client_module_url or import @wp-playground/client directly.\n\nConsumer blocker:\n- studio-native assets/preview/codebox-client.ts cannot remove the dynamic startPlaygroundWeb import until this contract exists.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in studio-native assets/preview/codebox-client.ts and trace its dynamic startPlaygroundWeb import and use of client_module_url. Read the existing browser SDK entry points and the Codebox preview boot DTO/session boot contract. Done means a versioned browser SDK method exposes the current browser client/session handle so the consumer no longer imports @wp-playground/client directly.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.