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 Japanese translations to Blueprint Examples and Troubleshoot and debug. ([#2474](https://github.com/WordPress/wordpress-playground/pull/2474))
37
+
38
+
### Contributors
39
+
40
+
The following contributors merged PRs in this release:
41
+
42
+
@adamziel@rollybueno@shimotmk@zaerl
43
+
44
+
## [v2.0.8] (2025-08-07)
45
+
46
+
### Blueprints
47
+
48
+
- Fallback to URL-based file name when fetching remote ZIP files. ([#2470](https://github.com/WordPress/wordpress-playground/pull/2470))
49
+
50
+
### Documentation
51
+
52
+
-[Docs] Adding Resources, Web instance, and guides pages on Brazilian Portuguese. ([#2351](https://github.com/WordPress/wordpress-playground/pull/2351))
53
+
-[Docs] Enabling language switcher. ([#2465](https://github.com/WordPress/wordpress-playground/pull/2465))
54
+
55
+
### PHP WebAssembly
56
+
57
+
- Fix resolving mounted symlinks in secondary PHP instances. ([#2444](https://github.com/WordPress/wordpress-playground/pull/2444))
58
+
-[XDebug Bridge] List additional ASYNCIFY_ONLY functions to prevent `unreachable` crashes when using Devtools. ([#2454](https://github.com/WordPress/wordpress-playground/pull/2454))
59
+
60
+
### Website
61
+
62
+
-[Browser] Do not use the Buffer class in web browsers. ([#2469](https://github.com/WordPress/wordpress-playground/pull/2469))
Copy file name to clipboardExpand all lines: README.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,15 @@ Playground aims to facilitate:
14
14
15
15
- Learning WordPress Through Exploration
16
16
- Learning WordPress Development Through Writing Code
17
-
- Instant access to WordPress ecosystem
17
+
- Instant access to the WordPress ecosystem
18
18
19
19
Learn more about the [vision](https://github.com/WordPress/wordpress-playground/issues/472) and the [roadmap](https://github.com/WordPress/wordpress-playground/issues/525).
20
20
21
21
## Getting started
22
22
23
23
WordPress Playground has a [live demo](https://developer.wordpress.org/playground/demo/) available.
24
24
25
-
You can embed WordPress Playground in your project via an `<iframe>` – find out how in the [documentation](https://wordpress.github.io/wordpress-playground/). **Note the embed is experimental and may break or change without a warning.**
25
+
You can embed WordPress Playground in your project via an `<iframe>` – find out how in the [documentation](https://wordpress.github.io/wordpress-playground/). **Note the embed is experimental and may break or change without warning.**
26
26
27
27
You can connect to the Playground using the JavaScript client. Here's an example of how to do it in the browser using an `iframe` HTML element and the `startPlaygroundWeb` function from the `@wp-playground/client` package.
28
28
@@ -68,6 +68,19 @@ You can connect to the Playground using the JavaScript client. Here's an example
68
68
</script>
69
69
```
70
70
71
+
## The Playground CLI
72
+
73
+
For local development and testing, WordPress Playground offers a command-line interface (CLI) tool: [`@wp-playground/cli`](https://www.npmjs.com/package/@wp-playground/cli). This powerful tool simplifies setting up a local WordPress environment, leveraging the capabilities of WordPress Playground to create zero-setup instances. It's useful for developers, as it allows you to quickly spin up a WordPress site directly in your project directory without complex server configurations, and even switch PHP and WordPress versions with simple flags.
74
+
75
+
The best part? You can run it directly using `npx`, Node.js's package runner. To get started, navigate to your plugin or theme directory and run:
76
+
77
+
```bash
78
+
cd my-plugin-or-theme-directory
79
+
npx @wp-playground/cli server --auto-mount
80
+
```
81
+
82
+
The `--auto-mount` flag detects if your project is a plugin or theme, mounting it automatically into the virtual WordPress environment. This provides an instant, isolated WordPress instance for testing your code. For more advanced usage, including manual mounting options and blueprint integration, refer to the [Playground CLI documentation](https://github.com/WordPress/wordpress-playground/tree/trunk/packages/playground/cli#readme).
83
+
71
84
## WordPress Playground Tools
72
85
73
86
WordPress [Playground Tools](https://github.com/WordPress/playground-tools) are independent applications built on top of WordPress Playground. They are located in a different repository: [WordPress/playground-tools](https://github.com/WordPress/playground-tools).
@@ -76,7 +89,6 @@ These tools include:
76
89
77
90
-[Interactive Code Block for Gutenberg](https://github.com/WordPress/playground-tools/tree/trunk/packages/interactive-code-block/#readme)
78
91
-[WordPress Playground for Visual Studio Code](https://github.com/WordPress/playground-tools/tree/trunk/packages/vscode-extension/#readme)
79
-
-[@wp-playground/cli](https://github.com/WordPress/wordpress-playground/tree/trunk/packages/playground/cli#readme) CLI local development environment.
0 commit comments