Skip to content

[Playground block] Use playground.wordpress.net as a remote #381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamziel merged 2 commits into from
Jul 22, 2025
Merged

[Playground block] Use playground.wordpress.net as a remote #381

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bc862d4
[WordPress Playground plugin Use playground.wordpress.net as a remote
adamziel Jul 14, 2025
24317e9
Merge branch 'trunk' into use-playground-wordpres-net-as-remote
adamziel Jul 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions packages/wordpress-playground-block/src/components/playground-preview/index.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,12 +248,7 @@ function PlaygroundPreview({

const configuration = {
iframe: iframeRef.current,
// wasm.wordpress.net is alias for playground.wordpress.net at the moment.
// @TODO: Use playground.wordpress.net once the service worker
// is updated. The current one tries to serve the remote.html
// file from a /wp-6.4/ path when this block is used on
// playground.wordpress.net, and that returns a 404.html.
remoteUrl: 'https://wasm.wordpress.net/remote.html',
remoteUrl: 'https://playground.wordpress.net/remote.html',
} as any;
if (finalBlueprint) {
configuration['blueprint'] = finalBlueprint;
Expand Down