You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a new Playground page documenting the console script editor, the CDP_WS_URL connection variable, the preinstalled CDP clients, and the run limits
Link to it from Getting started, where it sits alongside the HTTP API and MCP as another way to use the cloud
Note on Puppeteer and Playwright that the playground exposes CDP_WS_URL instead of LPD_TOKEN
State on Limits and billing that browser hours and concurrency apply to every session, however it was opened
Note
This branch is stacked on #75 (complete-cloud-section), which is not merged yet. The base of this PR is complete-cloud-section rather than main, so the diff shows only the playground commits. It needs to be retargeted to main once #75 lands, which GitHub does automatically if the complete-cloud-section branch is deleted on merge.
Preview. The marketing site pins apps/docs as a submodule, so each PR gets its own preview branch there:
The playground Settings panel shows node:24.18-bookworm-slim (webapp, src/components/pages/playground/scripts/PlaygroundScriptSidebar.tsx:13). That is only the build stage of the runtime image, blade/docker/Dockerfile.runtime:3. Scripts run on the final stage, gcr.io/distroless/nodejs22-debian12:nonroot (line 15), whose entrypoint is that image's own node binary (line 34). Only node_modules is copied out of the build stage (line 30). The image label agrees: io.lightpanda.blade.node.version="22" (line 18).
It looks like this came from blade 65abc4d ("chore: update node to lts 24.18"), which bumped the build stage from node:22-bookworm-slim to 24.18 and left the final stage and the label on 22. So the runtime is still Node 22 while the UI advertises 24.
I left the Node version out of the page until this is settled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CDP_WS_URLconnection variable, the preinstalled CDP clients, and the run limitsCDP_WS_URLinstead ofLPD_TOKENNote
This branch is stacked on #75 (
complete-cloud-section), which is not merged yet. The base of this PR iscomplete-cloud-sectionrather thanmain, so the diff shows only the playground commits. It needs to be retargeted tomainonce #75 lands, which GitHub does automatically if thecomplete-cloud-sectionbranch is deleted on merge.Preview. The marketing site pins
apps/docsas a submodule, so each PR gets its own preview branch there:docs-playgroundplaygroundcomplete-cloud-sectioncomplete-cloud-sectionBecause the branches are stacked, the
docs-playgroundpreview necessarily includes the #75 changes as well.