From 24ee04a77d078a156554693ccd91be78dcf5300f Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 10:16:34 +0000 Subject: [PATCH 01/10] applying docs guidelines --- .../04-wp-playground-cli.md | 41 +++++++++---------- 1 file changed, 20 insertions(+), 21 deletions(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index f5def5f246..8c77971594 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -5,20 +5,19 @@ slug: /developers/local-development/wp-playground-cli # Playground CLI -[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) is a command-line tool that simplifies the WordPress development and testing flow. -Playground CLI supports auto-mounting a directory with a plugin, theme, or WordPress installation. But if you need flexibility, the CLI supports mounting commands to personalize your local environment. +[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) is a command-line tool that simplifies the WordPress development and testing flow. You can use Playground CLI to auto-mount a directory with a plugin, theme, or WordPress installation. If you need flexibility, you can use mounting commands to personalize your local environment. **Key features:** -- **Quick Setup**: Set up a local WordPress environment in seconds. +- **Quick setup**: Set up a local WordPress environment in seconds. - **Flexibility**: Allows for configuration to adapt to different scenarios. -- **Simple Environment**: No extra configuration, just a compatible Node version, and you are ready to use it. +- **Simple environment**: No extra configuration, just a compatible Node version, and you are ready to use it. ## Requirements The Playground CLI requires Node.js 20.18 or higher, which is the recommended Long-Term Support (LTS) version. You can download it from the [Node.js website](https://nodejs.org/en/download). -## Quickstart +## Quick start To run the Playground CLI, open a command line and use the following command: @@ -35,7 +34,7 @@ cd my-plugin-or-theme-directory npx @wp-playground/cli@latest server --auto-mount ``` -### Choosing a WordPress and PHP Version +### Choosing a WordPress and PHP version By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due to its improved performance. To specify your preferred versions, you can use the flag `--wp=` and `--php=`: @@ -43,11 +42,11 @@ By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 ``` -### Loading Blueprints +### Loading blueprints One way to take your Playground CLI development experience to the next level is to integrate with [Blueprints](/blueprints/getting-started/). For those unfamiliar with this technology, it allows developers to configure the initial state for their WordPress Playground instances. -Using the `--blueprint=` flag, developers can run a Playground with a custom initial state. We’ll use the example below to do this. +Using the `--blueprint=` flag, developers can run a Playground with a custom initial state. We'll use the example below to do this. **(my-blueprint.json)** @@ -88,7 +87,7 @@ npx @wp-playground/cli@latest server --mount-before-install=.:/wordpress/ On Windows, the path format `/host/path:/vfs/path` can cause issues. To resolve this, use the flags `--mount-dir` and `--mount-dir-before-install`. These flags let you specify host and virtual file system paths in an alternative format`"/host/path"` `"/vfs/path"`. ::: -### Understanding Data Persistence and SQLite Location +### Understanding data persistence and SQLite location By default, Playground CLI stores WordPress files and the SQLite database in **temporary directories on your operating system**: @@ -99,7 +98,7 @@ By default, Playground CLI stores WordPress files and the SQLite database in **t └── tmp/ # Temporary PHP files ``` -**Finding Your Temp Directory:** +**Finding your temp directory:** The actual location depends on your OS (these are examples or common possibilities): @@ -125,7 +124,7 @@ Mount before WP install: /wordpress -> /private/var/folders/c8/mwz12ycx4s509056kby3hk180000gn/T/node-playground-cli-site-62926--62926-yQNOdvJVIgYC/wordpress ``` -**Where is the SQLite Database Stored?** +**Where is the SQLite database stored?** The database location depends on what you mount: @@ -141,10 +140,10 @@ The database location depends on what you mount: - **Custom mounts**: Database location follows your mount configuration -**Automatic Cleanup:** +**Automatic cleanup:** Playground CLI automatically removes temp directories that are: -- Older than 2 days +- Older than two days - No longer associated with a running process **Recommendation:** To persist both your code and database when developing plugins or themes, mount the entire `wp-content` directory instead of just the plugin/theme folder. @@ -157,9 +156,9 @@ cd my-wordpress-project npx @wp-playground/cli@latest server --mount=./wp-content:/wordpress/wp-content ``` -## Command and Arguments +## Commands and arguments -Playground CLI is simple, configurable, and unopinionated. You can set it up according +The Playground CLI is simple, configurable, and unopinionated. You can set it up according to your unique WordPress setup. With the Playground CLI, you can use the following top-level commands: - **`server`**: (Default) Starts a local WordPress server. @@ -190,7 +189,7 @@ The `server` command supports the following optional arguments: - `--internal-cookie-store`: Enable internal cookie handling. When enabled, Playground will manage cookies internally using an HttpCookieStore that persists cookies across requests. When disabled, cookies are handled externally (e.g., by a browser in Node.js environments). Defaults to false. - `--xdebug`: Enable Xdebug. Defaults to false. - `--experimental-devtools`: Enable experimental browser development tools. Defaults to false. -- `--experimental-multi-worker=`: Enable experimental multi-worker support which requires a `/wordpress` directory backed by a real filesystem. Pass a positive number to specify the number of workers to use. Otherwise, defaults to the number of CPUs minus 1. +- `--experimental-multi-worker=`: Enable experimental multi-worker support which requires a `/wordpress` directory backed by a real file system. Pass a positive number to specify the number of workers to use. Otherwise, defaults to the number of CPUs minus one. :::caution With the flag `--follow-symlinks`, the following symlinks will expose files outside mounted directories to Playground and could be a security risk. @@ -204,7 +203,7 @@ With the Playground CLI, you can use the `--help` flag to get the full list of a npx @wp-playground/cli@latest --help ``` -## Programmatic Usage with JavaScript +## Programmatic usage with JavaScript The Playground CLI can also be controlled programmatically from your JavaScript/TypeScript code using the `runCLI` function. This gives you direct access to all CLI functionalities within your code, which is useful for automating end-to-end tests. Let's cover the basics of using `runCLI`. @@ -225,9 +224,9 @@ cliServer = await runCLI({ } as RunCLIArgs); ``` -To execute the code above, the developer can set their preferred method. A simple way to execute this code is to save it as a `.ts` file and run it with a tool like `tsx`. For example: `tsx my-script.ts` +To execute the code above, you can set your preferred method. A simple way to execute this code is to save it as a `.ts` file and run it with a tool like `tsx`. For example: `tsx my-script.ts` -### Setting a Blueprint +### Setting a blueprint You can provide a blueprint in two ways: either as an object literal directly passed to the `blueprint` property, or as a string containing the path to an external `.json` file. @@ -277,7 +276,7 @@ const myBlueprint: BlueprintDeclaration = { ### Mounting a plugin programmatically -It is possible to mount local directories programmatically using `runCLI`. The options `mount` and `mount-before-install` are available. The `hostPath` property expects a path to a directory on your local machine. This path should be relative to where your script is being executed. +You can mount local directories programmatically using `runCLI`. The options `mount` and `mount-before-install` are available. The `hostPath` property expects a path to a directory on your local machine. This path should be relative to where your script is being executed. ```TypeScript cliServer = await runCLI({ @@ -292,7 +291,7 @@ It is possible to mount local directories programmatically using `runCLI`. The o }); ``` -With those options we can combine mounting parts of the project with blueprints, for example: +You can combine mounting parts of the project with blueprints, for example: ```TypeScript From d31581a67c3ca427630e22a36a554bbe179eee83 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 10:38:30 +0000 Subject: [PATCH 02/10] Adding more examples for run CLI and new flags --- .../04-wp-playground-cli.md | 525 +++++++++++++++++- 1 file changed, 503 insertions(+), 22 deletions(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 8c77971594..2d6996377c 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -34,6 +34,45 @@ cd my-plugin-or-theme-directory npx @wp-playground/cli@latest server --auto-mount ``` +### Auto-mounting different project types + +The `--auto-mount` flag intelligently detects your project type and mounts it appropriately: + +**Plugin directory:** + +```bash +cd my-plugin +npx @wp-playground/cli@latest server --auto-mount +``` + +**Theme directory:** + +```bash +cd my-theme +npx @wp-playground/cli@latest server --auto-mount +``` + +**wp-content directory:** + +```bash +cd my-site/wp-content +npx @wp-playground/cli@latest server --auto-mount +``` + +**Full WordPress installation:** + +```bash +cd my-wordpress +npx @wp-playground/cli@latest server --auto-mount +``` + +**Static HTML/PHP project:** + +```bash +cd my-static-site +npx @wp-playground/cli@latest server --auto-mount +``` + ### Choosing a WordPress and PHP version By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due to its improved performance. To specify your preferred versions, you can use the flag `--wp=` and `--php=`: @@ -42,6 +81,20 @@ By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 ``` +### Setting a custom site URL + +You can configure a custom site URL for your development environment, which is useful for testing domain-specific functionality or simulating production environments: + +```bash +npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test +``` + +You can also specify a custom port: + +```bash +npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 +``` + ### Loading blueprints One way to take your Playground CLI development experience to the next level is to integrate with [Blueprints](/blueprints/getting-started/). For those unfamiliar with this technology, it allows developers to configure the initial state for their WordPress Playground instances. @@ -50,14 +103,11 @@ Using the `--blueprint=` flag, developers can run a Playgroun **(my-blueprint.json)** -```bash +```json { - "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", - "login": true, - "plugins": [ - "hello-dolly", - "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip" - ] + "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", + "login": true, + "plugins": ["hello-dolly", "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip"] } ``` @@ -75,6 +125,16 @@ Some projects have a specific structure that requires a custom configuration; fo npx @wp-playground/cli@latest server --mount=.:/wordpress/wp-content/plugins/MY-PLUGIN-DIRECTORY ``` +**Multiple mounts:** + +You can mount multiple directories at once: + +```bash +npx @wp-playground/cli@latest server \ + --mount=./my-plugin:/wordpress/wp-content/plugins/my-plugin \ + --mount=./my-theme:/wordpress/wp-content/themes/my-theme +``` + ### Mounting before WordPress installation Consider mounting your WordPress project files before the WordPress installation begins. This approach is beneficial if you want to override the Playground boot process, as it can help connect Playground with `WP-CLI`. The `--mount-before-install` flag supports this process. @@ -83,8 +143,18 @@ Consider mounting your WordPress project files before the WordPress installation npx @wp-playground/cli@latest server --mount-before-install=.:/wordpress/ ``` -:::info -On Windows, the path format `/host/path:/vfs/path` can cause issues. To resolve this, use the flags `--mount-dir` and `--mount-dir-before-install`. These flags let you specify host and virtual file system paths in an alternative format`"/host/path"` `"/vfs/path"`. +### Symlink support for monorepos + +If you're working in a monorepo or complex project structure where packages are symlinked, you can enable symlink following: + +```bash +npx @wp-playground/cli@latest server \ + --follow-symlinks \ + --mount-before-install=./packages/my-plugin:/wordpress/wp-content/plugins/my-plugin +``` + +:::caution +Using `--follow-symlinks` can expose files outside mounted directories to Playground and could be a security risk. Only use this flag when you trust the symlink targets. ::: ### Understanding data persistence and SQLite location @@ -156,6 +226,20 @@ cd my-wordpress-project npx @wp-playground/cli@latest server --mount=./wp-content:/wordpress/wp-content ``` +## Verbosity and debugging + +The CLI supports different verbosity levels to control output, for `quiet`, `normal` and `debug` mode. The default mode is `normal`. For quiet mode, run the server with no output (useful for scripts and automation): + +```bash +npx @wp-playground/cli@latest server --verbosity=quiet +``` + +Get detailed logging information for troubleshooting, with `debug` mode: + +```bash +npx @wp-playground/cli@latest server --verbosity=debug +``` + ## Commands and arguments The Playground CLI is simple, configurable, and unopinionated. You can set it up according @@ -191,8 +275,8 @@ The `server` command supports the following optional arguments: - `--experimental-devtools`: Enable experimental browser development tools. Defaults to false. - `--experimental-multi-worker=`: Enable experimental multi-worker support which requires a `/wordpress` directory backed by a real file system. Pass a positive number to specify the number of workers to use. Otherwise, defaults to the number of CPUs minus one. -:::caution -With the flag `--follow-symlinks`, the following symlinks will expose files outside mounted directories to Playground and could be a security risk. +:::info +On Windows, the path format `/host/path:/vfs/path` can cause issues. To resolve this, use the flags `--mount-dir` and `--mount-dir-before-install`. These flags let you specify host and virtual file system paths in an alternative format`"/host/path"` `"/vfs/path"`. ::: ## Need some help with the CLI? @@ -226,6 +310,65 @@ cliServer = await runCLI({ To execute the code above, you can set your preferred method. A simple way to execute this code is to save it as a `.ts` file and run it with a tool like `tsx`. For example: `tsx my-script.ts` +**Testing with specific PHP versions:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + php: '8.0', + skipWordPressSetup: true, + skipSqliteSetup: true, +}); + +// Test PHP version +await cliServer.playground.writeFile( + '/wordpress/version.php', + '' +); + +const versionUrl = new URL('/version.php', cliServer.serverUrl); +const response = await fetch(versionUrl); +const version = await response.text(); +console.log('PHP Version:', version); // Outputs: 8.0.x +``` + +### Setting a custom site URL programmatically + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'site-url': 'https://my-staging.example.com', + port: 9500 +}); + +// Verify site URL is set correctly +await cliServer.playground.writeFile( + '/wordpress/check-url.php', + '' +); + +const checkUrl = new URL('/check-url.php', cliServer.serverUrl); +const response = await fetch(checkUrl); +console.log('Site URL:', await response.text()); +``` + +### Controlling verbosity programmatically + +```TypeScript +import { runCLI } from "@wp-playground/cli"; +import { logger } from '@php-wasm/logger'; + +const cliServer = await runCLI({ + command: 'server', + verbosity: 'debug' // or 'quiet' or 'normal' +}); + +// Add custom logging +logger.debug('Custom debug message'); +``` + ### Setting a blueprint You can provide a blueprint in two ways: either as an object literal directly passed to the `blueprint` property, or as a string containing the path to an external `.json` file. @@ -279,22 +422,38 @@ const myBlueprint: BlueprintDeclaration = { You can mount local directories programmatically using `runCLI`. The options `mount` and `mount-before-install` are available. The `hostPath` property expects a path to a directory on your local machine. This path should be relative to where your script is being executed. ```TypeScript - cliServer = await runCLI({ - command: 'server', - login: true, - 'mount-before-install': [ - { - hostPath: './[my-plugin-local-path]', - vfsPath: '/wordpress/wp-content/plugins/my-plugin', - }, - ], - }); +cliServer = await runCLI({ + command: 'server', + login: true, + 'mount-before-install': [ + { + hostPath: './[my-plugin-local-path]', + vfsPath: '/wordpress/wp-content/plugins/my-plugin', + }, + ], +}); ``` -You can combine mounting parts of the project with blueprints, for example: +**Auto-mounting programmatically:** ```TypeScript +import { runCLI } from "@wp-playground/cli"; +import process from 'node:process'; + +// Change to your project directory +process.chdir('./my-plugin'); + +const cliServer = await runCLI({ + command: 'server', + autoMount: '' // Empty string triggers auto-detection +}); +``` + +### Combining mounts with blueprints + +You can combine mounting parts of the project with blueprints, for example: +```TypeScript import { runCLI, RunCLIArgs, RunCLIServer } from "@wp-playground/cli"; let cliServer: RunCLIServer; @@ -320,3 +479,325 @@ cliServer = await runCLI({ } } as RunCLIArgs); ``` + +**Multiple mounts with blueprints:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + }, + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } +}); +``` + +**Complex blueprint with multiple configurations:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + php: '8.3', + wp: 'latest', + login: true, + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + landingPage: '/wp-admin/plugins.php', + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'setSiteOptions', + options: { + blogname: 'Plugin Test Site', + permalink_structure: '/%postname%/' + } + }, + { + step: 'runPHP', + code: '' + } + ] + } +}); +``` + +### Mode selection (Blueprint v2) + +You can specify different modes when working with Blueprint v2: + +**Creating a new site:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'create-new-site', + 'mount-before-install': [ + { + hostPath: './my-new-site', + vfsPath: '/wordpress' + } + ] +}); +``` + +**Applying to an existing site:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'apply-to-existing-site', + 'mount-before-install': [ + { + hostPath: './existing-wordpress', + vfsPath: '/wordpress' + } + ], + blueprint: { + steps: [ + { + step: 'setSiteOptions', + options: { + blogname: 'Updated Site Name' + } + } + ] + } +}); +``` + +## Automated testing + +### Integration testing with Vitest + +The programmatic API is excellent for automated testing. Here's a complete example using Vitest: + +```TypeScript +import { describe, test, expect, afterEach } from 'vitest'; +import { runCLI, RunCLIServer } from "@wp-playground/cli"; + +describe('My Plugin Tests', () => { + let cliServer: RunCLIServer; + + afterEach(async () => { + if (cliServer) { + await cliServer[Symbol.asyncDispose](); + } + }); + + test('plugin activates successfully', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); + const html = await response.text(); + expect(html).toContain('My Plugin'); + }); + + test('plugin settings page loads', async () => { + cliServer = await runCLI({ + command: 'server', + login: true, // Auto-login as admin + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const settingsUrl = new URL( + '/wp-admin/options-general.php?page=my-plugin', + cliServer.serverUrl + ); + const response = await fetch(settingsUrl); + + expect(response.status).toBe(200); + }); +}); +``` + +### Testing theme customizations + +```TypeScript +test('theme displays custom header', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'installTheme', + themeData: { + resource: 'vfs', + path: '/wordpress/wp-content/themes/my-theme' + } + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + const html = await response.text(); + + expect(html).toContain('
'); +}); +``` + +### Testing a plugin with different WordPress/PHP versions + +```TypeScript +test('plugin works with WordPress 6.4 and PHP 8.0', async () => { + cliServer = await runCLI({ + command: 'server', + php: '8.0', + wp: '6.4', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); +}); +``` + +## Advanced configuration + +### Skip WordPress and SQLite setup + +When you only need to test PHP code without WordPress, you can skip the setup for faster testing: + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + skipWordPressSetup: true, + skipSqliteSetup: true, + php: '8.3' +}); + +// Write and test custom PHP scripts +await cliServer.playground.writeFile( + '/wordpress/test.php', + '' +); + +const testUrl = new URL('/test.php', cliServer.serverUrl); +const response = await fetch(testUrl); +console.log(await response.text()); // Outputs: Hello from PHP! +``` + +### Error handling + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +try { + const cliServer = await runCLI({ + command: 'server', + debug: true // Enable PHP error logging + }); + + // Your test code here + +} catch (error) { + console.error('Server failed to start:', error); +} +``` + +### Following symlinks programmatically + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + followSymlinks: true, + 'mount-before-install': [ + { + hostPath: './symlinked-directory', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ] +}); +``` + +:::caution +Using symlinks can expose files outside mounted directories. Only enable this feature when you trust the symlink targets. +::: From 0ae0525cd5aa73a7cd57675d3f0154f54aee4688 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 10:56:42 +0000 Subject: [PATCH 03/10] adding page description --- .../docs/developers/05-local-development/04-wp-playground-cli.md | 1 + 1 file changed, 1 insertion(+) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 2d6996377c..eb62a26b7b 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -1,6 +1,7 @@ --- title: Playground CLI slug: /developers/local-development/wp-playground-cli +description: A command-line tool for WordPress development and testing with quick setup, flexible configuration, and minimal dependencies. --- # Playground CLI From 2458799dd6675c7ba8996cd665c7207e01cf37d9 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 10:57:01 +0000 Subject: [PATCH 04/10] updating spanish and portuguese translation --- .../04-wp-playground-cli.md | 748 +++++++++++++++++- .../04-wp-playground-cli.md | 697 ++++++++++++++-- 2 files changed, 1340 insertions(+), 105 deletions(-) diff --git a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index 41ef16ff49..a05c8d156b 100644 --- a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -1,25 +1,43 @@ --- title: Playground CLI slug: /developers/local-development/wp-playground-cli +description: Una herramienta de línea de comandos para desarrollo y pruebas de WordPress con configuración rápida, configuración flexible y dependencias mínimas. --- + + # Playground CLI -[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) es una herramienta de línea de comandos que simplifica el flujo de desarrollo y pruebas de WordPress. -Playground CLI soporta el montaje automático de un directorio con un plugin, tema o instalación de WordPress. Pero si necesitas flexibilidad, el CLI soporta comandos de montaje para personalizar tu entorno local. + + +[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) es una herramienta de línea de comandos que simplifica el flujo de desarrollo y pruebas de WordPress. Puedes usar Playground CLI para auto-montar un directorio con un plugin, tema o instalación de WordPress. Si necesitas flexibilidad, puedes usar comandos de montaje para personalizar tu entorno local. + + **Características principales:** + + + + - **Configuración Rápida**: Configura un entorno WordPress local en segundos. - **Flexibilidad**: Permite la configuración para adaptarse a diferentes escenarios. - **Entorno Simple**: Sin configuración extra, solo una versión compatible de Node, y estás listo para usarlo. + + ## Requisitos + + El Playground CLI requiere Node.js 20.18 o superior, que es la versión recomendada de Soporte a Largo Plazo (LTS). Puedes descargarlo desde el [sitio web de Node.js](https://nodejs.org/en/download). + + ## Inicio Rápido + + Para ejecutar el Playground CLI, abre una línea de comandos y usa el siguiente comando: ```bash @@ -28,6 +46,8 @@ npx @wp-playground/cli@latest server ![Playground CLI en Acción](@site/static/img/developers/npx-wp-playground-server.gif) + + Con el comando anterior, solo obtienes una instancia fresca de WordPress para probar. La mayoría de los desarrolladores querrán probar su propio trabajo. Para probar un plugin o un tema, navega a la carpeta de tu proyecto y ejecuta el CLI con la bandera `--auto-mount`: ```bash @@ -35,61 +55,186 @@ cd my-plugin-or-theme-directory npx @wp-playground/cli@latest server --auto-mount ``` + + +### Auto-montaje de diferentes tipos de proyectos + + + +La bandera `--auto-mount` detecta inteligentemente tu tipo de proyecto y lo monta apropiadamente: + + + +**Directorio de plugin:** + +```bash +cd my-plugin +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Directorio de tema:** + +```bash +cd my-theme +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Directorio wp-content:** + +```bash +cd my-site/wp-content +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Instalación completa de WordPress:** + +```bash +cd my-wordpress +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Proyecto estático HTML/PHP:** + +```bash +cd my-static-site +npx @wp-playground/cli@latest server --auto-mount +``` + + + ### Elegir una Versión de WordPress y PHP + + Por defecto, el CLI carga la última versión estable de WordPress y PHP 8.3 debido a su rendimiento mejorado. Para especificar tus versiones preferidas, puedes usar las banderas `--wp=` y `--php=`: ```bash npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 ``` + + +### Configurar una URL de sitio personalizada + + + +Puedes configurar una URL de sitio personalizada para tu entorno de desarrollo, lo cual es útil para probar funcionalidad específica de dominio o simular entornos de producción: + +```bash +npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test +``` + + + +También puedes especificar un puerto personalizado: + +```bash +npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 +``` + + + ### Cargar Blueprints + + Una forma de llevar tu experiencia de desarrollo con Playground CLI al siguiente nivel es integrar con [Blueprints](/blueprints/getting-started/). Para aquellos que no estén familiarizados con esta tecnología, permite a los desarrolladores configurar el estado inicial para sus instancias de WordPress Playground. + + Usando la bandera `--blueprint=`, los desarrolladores pueden ejecutar un Playground con un estado inicial personalizado. Usaremos el ejemplo a continuación para hacer esto. **(my-blueprint.json)** -```bash +```json { - "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", - "login": true, - "plugins": [ - "hello-dolly", - "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip" - ] + "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", + "login": true, + "plugins": ["hello-dolly", "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip"] } ``` + + Comando CLI cargando un blueprint: ```bash npx @wp-playground/cli@latest server --blueprint=my-blueprint.json ``` + + ### Montar carpetas manualmente + + Algunos proyectos tienen una estructura específica que requiere una configuración personalizada; por ejemplo, tu repositorio contiene todos los archivos en la carpeta `/wp-content/`. Entonces en este escenario, puedes especificar al Playground CLI que montará tu proyecto desde esa carpeta usando la bandera `--mount`. ```bash npx @wp-playground/cli@latest server --mount=.:/wordpress/wp-content/plugins/MY-PLUGIN-DIRECTORY ``` + + +**Múltiples montajes:** + + + +Puedes montar múltiples directorios a la vez: + +```bash +npx @wp-playground/cli@latest server \ + --mount=./my-plugin:/wordpress/wp-content/plugins/my-plugin \ + --mount=./my-theme:/wordpress/wp-content/themes/my-theme +``` + + + ### Montar antes de la instalación de WordPress + + Considera montar tus archivos de proyecto de WordPress antes de que comience la instalación de WordPress. Este enfoque es beneficioso si quieres sobrescribir el proceso de arranque de Playground, ya que puede ayudar a conectar Playground con `WP-CLI`. La bandera `--mount-before-install` soporta este proceso. ```bash npx @wp-playground/cli@latest server --mount-before-install=.:/wordpress/ ``` -:::info -En Windows, el formato de ruta `/host/path:/vfs/path` puede causar problemas. Para resolver esto, usa las banderas `--mount-dir` y `--mount-dir-before-install`. Estas banderas te permiten especificar rutas del host y del sistema de archivos virtual en un formato alternativo `"/host/path"` `"/vfs/path"`. + + +### Soporte de enlaces simbólicos para monorepos + + + +Si estás trabajando en un monorepo o estructura de proyecto compleja donde los paquetes están enlazados simbólicamente, puedes habilitar el seguimiento de enlaces simbólicos: + +```bash +npx @wp-playground/cli@latest server \ + --follow-symlinks \ + --mount-before-install=./packages/my-plugin:/wordpress/wp-content/plugins/my-plugin +``` + +:::caution + + + +Usar `--follow-symlinks` puede exponer archivos fuera de los directorios montados a Playground y podría ser un riesgo de seguridad. Solo usa esta bandera cuando confíes en los destinos de los enlaces simbólicos. ::: + + ### Entender la Persistencia de Datos y Ubicación de SQLite + + Por defecto, Playground CLI almacena archivos de WordPress y la base de datos SQLite en **directorios temporales en tu sistema operativo**: ``` @@ -99,19 +244,30 @@ Por defecto, Playground CLI almacena archivos de WordPress y la base de datos SQ └── tmp/ # Archivos temporales PHP ``` + + **Encontrar tu Directorio Temporal:** + + La ubicación real depende de tu SO (estos son ejemplos o posibilidades comunes): + + + - **macOS/Linux**: Puede estar bajo `/tmp/` o `/private/var/folders/` (varía según el sistema) - **Windows**: `C:\Users\\AppData\Local\Temp\` + + Para ver la ruta exacta del directorio temporal que se está usando, ejecuta el CLI con la bandera `--verbosity=debug`: ```bash npx @wp-playground/cli@latest server --verbosity=debug ``` + + Esto mostrará algo como: ``` @@ -125,30 +281,56 @@ Mount before WP install: /wordpress -> /private/var/folders/c8/mwz12ycx4s509056kby3hk180000gn/T/node-playground-cli-site-62926--62926-yQNOdvJVIgYC/wordpress ``` + + **¿Dónde se Almacena la Base de Datos SQLite?** + + La ubicación de la base de datos depende de lo que montes: + + + + - **Montaje automático de wp-content o WordPress completo**: - Base de datos: `/wp-content/database/.ht.sqlite` - ✅ **Persistido localmente** en la carpeta de tu proyecto + + + + - **Montaje automático solo de plugin/tema**: - Base de datos: `/playground-/wordpress/wp-content/database/.ht.sqlite` - ⚠️ **Perdido cuando el servidor se detiene** (los directorios temporales se limpian) + + - **Montajes personalizados**: La ubicación de la base de datos sigue tu configuración de montaje + + **Limpieza Automática:** + + + Playground CLI elimina automáticamente los directorios temporales que son: -- Más antiguos de 2 días + + + +- Más antiguos de dos días - Ya no están asociados con un proceso en ejecución + + **Recomendación:** Para persistir tanto tu código como la base de datos al desarrollar plugins o temas, monta el directorio `wp-content` completo en lugar de solo la carpeta del plugin/tema. + + **Ejemplo: Montar wp-content para persistencia** ```bash @@ -157,15 +339,44 @@ cd my-wordpress-project npx @wp-playground/cli@latest server --mount=./wp-content:/wordpress/wp-content ``` + + +## Verbosidad y depuración + + + +El CLI soporta diferentes niveles de verbosidad para controlar la salida, para los modos `quiet`, `normal` y `debug`. El modo por defecto es `normal`. Para el modo silencioso, ejecuta el servidor sin salida (útil para scripts y automatización): + +```bash +npx @wp-playground/cli@latest server --verbosity=quiet +``` + + + +Obtén información de registro detallada para solucionar problemas, con el modo `debug`: + +```bash +npx @wp-playground/cli@latest server --verbosity=debug +``` + + + ## Comandos y Argumentos -Playground CLI es simple, configurable y sin opiniones. Puedes configurarlo de acuerdo -a tu configuración única de WordPress. Con el Playground CLI, puedes usar los siguientes comandos de nivel superior: + + +Playground CLI es simple, configurable y sin opiniones. Puedes configurarlo de acuerdo a tu configuración única de WordPress. Con el Playground CLI, puedes usar los siguientes comandos de nivel superior: + + + + - **`server`**: (Por defecto) Inicia un servidor WordPress local. - **`run-blueprint`**: Ejecuta un archivo Blueprint sin iniciar un servidor web. - **`build-snapshot`**: Construye una instantánea ZIP de un sitio WordPress basado en un Blueprint. + + El comando `server` soporta los siguientes argumentos opcionales: - `--port=`: El número de puerto para que el servidor escuche. Por defecto es 9400. @@ -190,27 +401,42 @@ El comando `server` soporta los siguientes argumentos opcionales: - `--internal-cookie-store`: Habilitar manejo interno de cookies. Cuando está habilitado, Playground administrará cookies internamente usando un HttpCookieStore que persiste cookies entre solicitudes. Cuando está deshabilitado, las cookies se manejan externamente (por ejemplo, por un navegador en entornos Node.js). Por defecto es false. - `--xdebug`: Habilitar Xdebug. Por defecto es false. - `--experimental-devtools`: Habilitar herramientas de desarrollo experimentales del navegador. Por defecto es false. -- `--experimental-multi-worker=`: Habilitar soporte experimental multi-worker que requiere un directorio `/wordpress` respaldado por un sistema de archivos real. Pasa un número positivo para especificar el número de workers a usar. De lo contrario, por defecto es el número de CPUs menos 1. +- `--experimental-multi-worker=`: Habilitar soporte experimental multi-worker que requiere un directorio `/wordpress` respaldado por un sistema de archivos real. Pasa un número positivo para especificar el número de workers a usar. De lo contrario, por defecto es el número de CPUs menos uno. -:::caution -Con la bandera `--follow-symlinks`, los siguientes enlaces simbólicos expondrán archivos fuera de los directorios montados a Playground y podrían ser un riesgo de seguridad. +:::info + + + +En Windows, el formato de ruta `/host/path:/vfs/path` puede causar problemas. Para resolver esto, usa las banderas `--mount-dir` y `--mount-dir-before-install`. Estas banderas te permiten especificar rutas del host y del sistema de archivos virtual en un formato alternativo `"/host/path"` `"/vfs/path"`. ::: + + ## ¿Necesitas ayuda con el CLI? + + Con el Playground CLI, puedes usar la bandera `--help` para obtener la lista completa de comandos y argumentos disponibles. ```bash npx @wp-playground/cli@latest --help ``` + + ## Uso Programático con JavaScript + + El Playground CLI también puede ser controlado programáticamente desde tu código JavaScript/TypeScript usando la función `runCLI`. Esto te da acceso directo a todas las funcionalidades del CLI dentro de tu código, lo cual es útil para automatizar pruebas end-to-end. Cubramos los conceptos básicos del uso de `runCLI`. + + ### Ejecutar una instancia de WordPress con una versión específica -Usando la función `runCLI`, puedes especificar opciones como las versiones de PHP y WordPress. En el ejemplo a continuación, solicitamos PHP 8.3, la última versión de WordPress, y iniciar sesión automáticamente. Todos los argumentos soportados están definidos en el tipo `RunCLIArgs`. + + +Usando la función `runCLI`, puedes especificar opciones como las versiones de PHP y WordPress. En el ejemplo a continuación, solicitamos PHP 8.3, la última versión de WordPress, y ser automáticamente conectado. Todos los argumentos soportados están definidos en el tipo `RunCLIArgs`. ```TypeScript import { runCLI, RunCLIArgs, RunCLIServer } from "@wp-playground/cli"; @@ -225,10 +451,81 @@ cliServer = await runCLI({ } as RunCLIArgs); ``` -Para ejecutar el código anterior, el desarrollador puede establecer su método preferido. Una forma simple de ejecutar este código es guardarlo como un archivo `.ts` y ejecutarlo con una herramienta como `tsx`. Por ejemplo: `tsx my-script.ts` + + +Para ejecutar el código anterior, puedes establecer tu método preferido. Una forma simple de ejecutar este código es guardarlo como un archivo `.ts` y ejecutarlo con una herramienta como `tsx`. Por ejemplo: `tsx my-script.ts` + + + +**Probando con versiones específicas de PHP:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + php: '8.0', + skipWordPressSetup: true, + skipSqliteSetup: true, +}); + +// Probar versión de PHP +await cliServer.playground.writeFile( + '/wordpress/version.php', + '' +); + +const versionUrl = new URL('/version.php', cliServer.serverUrl); +const response = await fetch(versionUrl); +const version = await response.text(); +console.log('Versión de PHP:', version); // Salida: 8.0.x +``` + + + +### Configurar una URL de sitio personalizada programáticamente + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'site-url': 'https://my-staging.example.com', + port: 9500 +}); + +// Verificar que la URL del sitio está configurada correctamente +await cliServer.playground.writeFile( + '/wordpress/check-url.php', + '' +); + +const checkUrl = new URL('/check-url.php', cliServer.serverUrl); +const response = await fetch(checkUrl); +console.log('URL del sitio:', await response.text()); +``` + + + +### Controlar la verbosidad programáticamente + +```TypeScript +import { runCLI } from "@wp-playground/cli"; +import { logger } from '@php-wasm/logger'; + +const cliServer = await runCLI({ + command: 'server', + verbosity: 'debug' // o 'quiet' o 'normal' +}); + +// Agregar registro personalizado +logger.debug('Mensaje de depuración personalizado'); +``` + + ### Configurar un Blueprint + + Puedes proporcionar un blueprint de dos maneras: ya sea como un objeto literal pasado directamente a la propiedad `blueprint`, o como una cadena que contiene la ruta a un archivo `.json` externo. ```TypeScript @@ -244,8 +541,8 @@ cliServer = await runCLI({ { "step": "setSiteOptions", "options": { - "blogname": "Blueprint Title", - "blogdescription": "A great blog description" + "blogname": "Título del Blueprint", + "blogdescription": "Una gran descripción de blog" } } ], @@ -253,6 +550,8 @@ cliServer = await runCLI({ }); ``` + + Para una seguridad de tipos completa al definir tu objeto blueprint, puedes importar y usar el tipo `BlueprintDeclaration` del paquete `@wp-playground/blueprints`: ```TypeScript @@ -275,27 +574,53 @@ const myBlueprint: BlueprintDeclaration = { }; ``` + + ### Montar un plugin programáticamente -Es posible montar directorios locales programáticamente usando `runCLI`. Las opciones `mount` y `mount-before-install` están disponibles. La propiedad `hostPath` espera una ruta a un directorio en tu máquina local. Esta ruta debe ser relativa a donde se está ejecutando tu script. + + +Puedes montar directorios locales programáticamente usando `runCLI`. Las opciones `mount` y `mount-before-install` están disponibles. La propiedad `hostPath` espera una ruta a un directorio en tu máquina local. Esta ruta debe ser relativa a donde se está ejecutando tu script. ```TypeScript - cliServer = await runCLI({ - command: 'server', - login: true, - 'mount-before-install': [ - { - hostPath: './[my-plugin-local-path]', - vfsPath: '/wordpress/wp-content/plugins/my-plugin', - }, - ], - }); +cliServer = await runCLI({ + command: 'server', + login: true, + 'mount-before-install': [ + { + hostPath: './[my-plugin-local-path]', + vfsPath: '/wordpress/wp-content/plugins/my-plugin', + }, + ], +}); ``` -Con esas opciones podemos combinar el montaje de partes del proyecto con blueprints, por ejemplo: + + +**Auto-montaje programático:** ```TypeScript +import { runCLI } from "@wp-playground/cli"; +import process from 'node:process'; +// Cambiar a tu directorio de proyecto +process.chdir('./my-plugin'); + +const cliServer = await runCLI({ + command: 'server', + autoMount: '' // Cadena vacía activa la detección automática +}); +``` + + + +### Combinar montajes con blueprints + + + +Puedes combinar el montaje de partes del proyecto con blueprints, por ejemplo: + +```TypeScript import { runCLI, RunCLIArgs, RunCLIServer } from "@wp-playground/cli"; let cliServer: RunCLIServer; @@ -321,3 +646,360 @@ cliServer = await runCLI({ } } as RunCLIArgs); ``` + + + +**Múltiples montajes con blueprints:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + }, + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } +}); +``` + + + +**Blueprint complejo con múltiples configuraciones:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + php: '8.3', + wp: 'latest', + login: true, + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + landingPage: '/wp-admin/plugins.php', + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'setSiteOptions', + options: { + blogname: 'Sitio de Prueba de Plugin', + permalink_structure: '/%postname%/' + } + }, + { + step: 'runPHP', + code: '' + } + ] + } +}); +``` + + + +### Selección de modo (Blueprint v2) + + + +Puedes especificar diferentes modos cuando trabajas con Blueprint v2: + + + +**Crear un nuevo sitio:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'create-new-site', + 'mount-before-install': [ + { + hostPath: './my-new-site', + vfsPath: '/wordpress' + } + ] +}); +``` + + + +**Aplicar a un sitio existente:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'apply-to-existing-site', + 'mount-before-install': [ + { + hostPath: './existing-wordpress', + vfsPath: '/wordpress' + } + ], + blueprint: { + steps: [ + { + step: 'setSiteOptions', + options: { + blogname: 'Nombre de Sitio Actualizado' + } + } + ] + } +}); +``` + + + +## Pruebas automatizadas + + + +### Pruebas de integración con Vitest + + + +La API programática es excelente para pruebas automatizadas. Aquí hay un ejemplo completo usando Vitest: + +```TypeScript +import { describe, test, expect, afterEach } from 'vitest'; +import { runCLI, RunCLIServer } from "@wp-playground/cli"; + +describe('Pruebas de Mi Plugin', () => { + let cliServer: RunCLIServer; + + afterEach(async () => { + if (cliServer) { + await cliServer[Symbol.asyncDispose](); + } + }); + + test('el plugin se activa con éxito', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); + const html = await response.text(); + expect(html).toContain('Mi Plugin'); + }); + + test('la página de configuración del plugin se carga', async () => { + cliServer = await runCLI({ + command: 'server', + login: true, // Auto-login como admin + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const settingsUrl = new URL( + '/wp-admin/options-general.php?page=my-plugin', + cliServer.serverUrl + ); + const response = await fetch(settingsUrl); + + expect(response.status).toBe(200); + }); +}); +``` + + + +### Probar personalizaciones de temas + +```TypeScript +test('el tema muestra encabezado personalizado', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'installTheme', + themeData: { + resource: 'vfs', + path: '/wordpress/wp-content/themes/my-theme' + } + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + const html = await response.text(); + + expect(html).toContain('
'); +}); +``` + + + +### Probar un plugin con diferentes versiones de WordPress/PHP + +```TypeScript +test('el plugin funciona con WordPress 6.4 y PHP 8.0', async () => { + cliServer = await runCLI({ + command: 'server', + php: '8.0', + wp: '6.4', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); +}); +``` + + + +## Configuración avanzada + + + +### Omitir configuración de WordPress y SQLite + + + +Cuando solo necesitas probar código PHP sin WordPress, puedes omitir la configuración para pruebas más rápidas: + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + skipWordPressSetup: true, + skipSqliteSetup: true, + php: '8.3' +}); + +// Escribir y probar scripts PHP personalizados +await cliServer.playground.writeFile( + '/wordpress/test.php', + '' +); + +const testUrl = new URL('/test.php', cliServer.serverUrl); +const response = await fetch(testUrl); +console.log(await response.text()); // Salida: Hola desde PHP! +``` + + + +### Manejo de errores + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +try { + const cliServer = await runCLI({ + command: 'server', + debug: true // Habilitar registro de errores PHP + }); + + // Tu código de prueba aquí + +} catch (error) { + console.error('Error al iniciar el servidor:', error); +} +``` + + + +### Seguir enlaces simbólicos programáticamente + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + followSymlinks: true, + 'mount-before-install': [ + { + hostPath: './symlinked-directory', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ] +}); +``` + +:::caution + + + +Usar enlaces simbólicos puede exponer archivos fuera de los directorios montados. Solo habilita esta función cuando confíes en los destinos de los enlaces simbólicos. +::: diff --git a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index d7da47b160..47e897e082 100644 --- a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -1,25 +1,24 @@ --- title: Playground CLI slug: /developers/local-development/wp-playground-cli +description: Uma ferramenta de linha de comando para desenvolvimento e testes do WordPress com configuração rápida, configuração flexível e dependências mínimas. --- # Playground CLI - + -[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) é uma ferramenta de linha de comando que simplifica o fluxo de desenvolvimento e teste do WordPress. -O Playground CLI suporta auto-montagem de um diretório com um plugin, tema ou instalação WordPress. Mas se você precisa de flexibilidade, o CLI suporta comandos de montagem para personalizar seu ambiente local. +[@wp-playground/cli](https://www.npmjs.com/package/@wp-playground/cli) é uma ferramenta de linha de comando que simplifica o fluxo de desenvolvimento e teste do WordPress. Você pode usar o Playground CLI para auto-montar um diretório com um plugin, tema ou instalação WordPress. Se você precisa de flexibilidade, pode usar comandos de montagem para personalizar seu ambiente local. **Principais recursos:** - + - + - **Configuração Rápida**: Configure um ambiente WordPress local em segundos. - **Flexibilidade**: Permite configuração para se adaptar a diferentes cenários. @@ -33,32 +32,83 @@ O Playground CLI suporta auto-montagem de um diretório com um plugin, tema ou i O Playground CLI requer Node.js 20.18 ou superior, que é a versão recomendada de Suporte de Longo Prazo (LTS). Você pode baixá-la no [site do Node.js](https://nodejs.org/en/download). - + ## Início Rápido - + -Executar o Playground CLI é tão simples quanto ir para uma linha de comando e executar: +Para executar o Playground CLI, abra uma linha de comando e use o seguinte comando: ```bash npx @wp-playground/cli@latest server ``` - - ![Playground CLI em Ação](@site/static/img/developers/npx-wp-playground-server.gif) - + -Com o comando anterior, você obtém apenas uma instância WordPress fresca para testar. A maioria dos desenvolvedores quer ver seu trabalho rodando. Se este é o seu caso, teste um plugin ou tema. Você pode executar o CLI na pasta do seu projeto e executar o Playground CLI com a flag `--auto-mount`: +Com o comando anterior, você obtém apenas uma instância WordPress fresca para testar. A maioria dos desenvolvedores vai querer testar seu próprio trabalho. Para testar um plugin ou tema, navegue até a pasta do seu projeto e execute o CLI com a flag `--auto-mount`: ```bash cd my-plugin-or-theme-directory npx @wp-playground/cli@latest server --auto-mount ``` - + + +### Auto-montagem de diferentes tipos de projetos + + + +A flag `--auto-mount` detecta inteligentemente o tipo do seu projeto e o monta apropriadamente: + + + +**Diretório de plugin:** + +```bash +cd my-plugin +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Diretório de tema:** + +```bash +cd my-theme +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Diretório wp-content:** + +```bash +cd my-site/wp-content +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Instalação completa do WordPress:** + +```bash +cd my-wordpress +npx @wp-playground/cli@latest server --auto-mount +``` + + + +**Projeto estático HTML/PHP:** + +```bash +cd my-static-site +npx @wp-playground/cli@latest server --auto-mount +``` + + ### Escolhendo uma Versão do WordPress e PHP @@ -67,10 +117,30 @@ npx @wp-playground/cli@latest server --auto-mount Por padrão, o CLI carrega a versão estável mais recente do WordPress e PHP 8.3 devido ao seu desempenho melhorado. Para especificar suas versões preferidas, você pode usar as flags `--wp=` e `--php=`: ```bash -npx @wp-playground/cli@latest server --wp=6.8 --php=8.4 +npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 ``` - + + +### Definindo uma URL de site personalizada + + + +Você pode configurar uma URL de site personalizada para seu ambiente de desenvolvimento, o que é útil para testar funcionalidades específicas de domínio ou simular ambientes de produção: + +```bash +npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test +``` + + + +Você também pode especificar uma porta personalizada: + +```bash +npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 +``` + + ### Carregando Blueprints @@ -82,18 +152,13 @@ Uma maneira de levar sua experiência de desenvolvimento do Playground CLI para Usando a flag `--blueprint=`, desenvolvedores podem executar um Playground com um estado inicial personalizado. Usaremos o exemplo abaixo para fazer isso. - +**(my-blueprint.json)** -**(meu-blueprint.json)** - -```bash +```json { - "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", - "login": true, - "plugins": [ - "hello-dolly", - "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip" - ] + "landingPage": "/wp-admin/options-general.php?page=akismet-key-config", + "login": true, + "plugins": ["hello-dolly", "https://raw.githubusercontent.com/adamziel/blueprints/trunk/docs/assets/hello-from-the-dashboard.zip"] } ``` @@ -117,6 +182,20 @@ Alguns projetos têm uma estrutura específica que requer uma configuração per npx @wp-playground/cli@latest server --mount=.:/wordpress/wp-content/plugins/MY-PLUGIN-DIRECTORY ``` + + +**Múltiplas montagens:** + + + +Você pode montar múltiplos diretórios de uma vez: + +```bash +npx @wp-playground/cli@latest server \ + --mount=./my-plugin:/wordpress/wp-content/plugins/my-plugin \ + --mount=./my-theme:/wordpress/wp-content/themes/my-theme +``` + ### Montando antes da instalação do WordPress @@ -129,15 +208,28 @@ Considere montar seus arquivos de projeto WordPress antes da instalação do Wor npx @wp-playground/cli@latest server --mount-before-install=.:/wordpress/ ``` - - - + -:::info -No Windows, o formato de caminho `/host/path:/vfs/path` pode causar problemas. Para resolver isso, use as flags `--mount-dir` e `--mount-dir-before-install`. Estas flags permitem que você especifique caminhos do host e do sistema de arquivos virtual em um formato alternativo `"/host/path"` `"/vfs/path"`. +### Suporte a links simbólicos para monorepos + + + +Se você está trabalhando em um monorepo ou estrutura de projeto complexa onde os pacotes são vinculados simbolicamente, você pode habilitar o seguimento de links simbólicos: + +```bash +npx @wp-playground/cli@latest server \ + --follow-symlinks \ + --mount-before-install=./packages/my-plugin:/wordpress/wp-content/plugins/my-plugin +``` + +:::caution + + + +Usar `--follow-symlinks` pode expor arquivos fora dos diretórios montados ao Playground e pode ser um risco de segurança. Use esta flag apenas quando confiar nos destinos dos links simbólicos. ::: - + ### Entendendo a Persistência de Dados e Localização do SQLite @@ -152,7 +244,7 @@ Por padrão, o Playground CLI armazena arquivos WordPress e o banco de dados SQL └── tmp/ # Arquivos temporários PHP ``` - + **Encontrando Seu Diretório Temporário:** @@ -189,7 +281,7 @@ Mount before WP install: /wordpress -> /private/var/folders/c8/mwz12ycx4s509056kby3hk180000gn/T/node-playground-cli-site-62926--62926-yQNOdvJVIgYC/wordpress ``` - + **Onde o Banco de Dados SQLite é Armazenado?** @@ -198,22 +290,20 @@ Mount before WP install: /wordpress -> A localização do banco de dados depende do que você montar: + + - **Auto-montagem de wp-content ou WordPress completo**: - - - - Banco de dados: `/wp-content/database/.ht.sqlite` - ✅ **Persistido localmente** na pasta do seu projeto + + - **Auto-montagem apenas de plugin/tema**: - - - - Banco de dados: `/playground-/wordpress/wp-content/database/.ht.sqlite` - ⚠️ **Perdido quando o servidor para** (diretórios temporários são limpos) @@ -221,7 +311,7 @@ A localização do banco de dados depende do que você montar: - **Montagens personalizadas**: A localização do banco de dados segue sua configuração de montagem - + **Limpeza Automática:** @@ -229,10 +319,10 @@ A localização do banco de dados depende do que você montar: O Playground CLI remove automaticamente diretórios temporários que são: - + -- Mais antigos que 2 dias +- Mais antigos que dois dias - Não mais associados com um processo em execução @@ -244,20 +334,38 @@ O Playground CLI remove automaticamente diretórios temporários que são: **Exemplo: Montando wp-content para persistência** ```bash -# Mount your entire wp-content directory +# Monte seu diretório wp-content inteiro cd my-wordpress-project npx @wp-playground/cli@latest server --mount=./wp-content:/wordpress/wp-content ``` - + + +## Verbosidade e depuração + + + +O CLI suporta diferentes níveis de verbosidade para controlar a saída, para os modos `quiet`, `normal` e `debug`. O modo padrão é `normal`. Para o modo silencioso, execute o servidor sem saída (útil para scripts e automação): + +```bash +npx @wp-playground/cli@latest server --verbosity=quiet +``` + + + +Obtenha informações de registro detalhadas para solução de problemas, com o modo `debug`: + +```bash +npx @wp-playground/cli@latest server --verbosity=debug +``` + + ## Comandos e Argumentos - + -O Playground CLI é simples, configurável e sem opiniões. Você pode configurá-lo de acordo -com sua configuração WordPress única. Com o Playground CLI, você pode usar os seguintes comandos de nível superior: +O Playground CLI é simples, configurável e sem opiniões. Você pode configurá-lo de acordo com sua configuração WordPress única. Com o Playground CLI, você pode usar os seguintes comandos de nível superior: @@ -293,10 +401,13 @@ O comando `server` suporta os seguintes argumentos opcionais: - `--internal-cookie-store`: Habilitar tratamento interno de cookies. Quando habilitado, o Playground gerenciará cookies internamente usando um HttpCookieStore que persiste cookies entre requisições. Quando desabilitado, cookies são tratados externamente (por exemplo, por um navegador em ambientes Node.js). Padrão é false. - `--xdebug`: Habilitar Xdebug. Padrão é false. - `--experimental-devtools`: Habilitar ferramentas de desenvolvimento experimentais do navegador. Padrão é false. -- `--experimental-multi-worker=`: Habilitar suporte experimental multi-worker que requer um diretório `/wordpress` apoiado por um sistema de arquivos real. Passe um número positivo para especificar o número de workers a usar. Caso contrário, padrão é o número de CPUs menos 1. +- `--experimental-multi-worker=`: Habilitar suporte experimental multi-worker que requer um diretório `/wordpress` apoiado por um sistema de arquivos real. Passe um número positivo para especificar o número de workers a usar. Caso contrário, padrão é o número de CPUs menos um. -:::caution -Com a flag `--follow-symlinks`, os seguintes links simbólicos irão expor arquivos fora dos diretórios montados ao Playground e podem ser um risco de segurança. +:::info + + + +No Windows, o formato de caminho `/host/path:/vfs/path` pode causar problemas. Para resolver isso, use as flags `--mount-dir` e `--mount-dir-before-install`. Estas flags permitem que você especifique caminhos do host e do sistema de arquivos virtual em um formato alternativo `"/host/path"` `"/vfs/path"`. ::: @@ -311,7 +422,7 @@ Com o Playground CLI, você pode usar a flag `--help` para obter a lista complet npx @wp-playground/cli@latest --help ``` - + ## Uso Programático com JavaScript @@ -340,11 +451,76 @@ cliServer = await runCLI({ } as RunCLIArgs); ``` - + + +Para executar o código acima, você pode definir seu método preferido. Uma maneira simples de executar este código é salvá-lo como um arquivo `.ts` e executá-lo com uma ferramenta como `tsx`. Por exemplo: `tsx my-script.ts` + + + +**Testando com versões específicas do PHP:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + php: '8.0', + skipWordPressSetup: true, + skipSqliteSetup: true, +}); + +// Testar versão do PHP +await cliServer.playground.writeFile( + '/wordpress/version.php', + '' +); + +const versionUrl = new URL('/version.php', cliServer.serverUrl); +const response = await fetch(versionUrl); +const version = await response.text(); +console.log('Versão do PHP:', version); // Saída: 8.0.x +``` + + + +### Definindo uma URL de site personalizada programaticamente + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'site-url': 'https://my-staging.example.com', + port: 9500 +}); + +// Verificar se a URL do site está configurada corretamente +await cliServer.playground.writeFile( + '/wordpress/check-url.php', + '' +); + +const checkUrl = new URL('/check-url.php', cliServer.serverUrl); +const response = await fetch(checkUrl); +console.log('URL do Site:', await response.text()); +``` + + + +### Controlando a verbosidade programaticamente + +```TypeScript +import { runCLI } from "@wp-playground/cli"; +import { logger } from '@php-wasm/logger'; + +const cliServer = await runCLI({ + command: 'server', + verbosity: 'debug' // ou 'quiet' ou 'normal' +}); -Para executar o código acima, o desenvolvedor pode definir seu método preferido. Uma maneira simples de executar este código é salvá-lo como um arquivo `.ts` e executá-lo com uma ferramenta como `tsx`. Por exemplo: `tsx meu-script.ts` +// Adicionar registro personalizado +logger.debug('Mensagem de depuração personalizada'); +``` - + ### Definindo um Blueprint @@ -365,8 +541,8 @@ cliServer = await runCLI({ { "step": "setSiteOptions", "options": { - "blogname": "Blueprint Title", - "blogdescription": "A great blog description" + "blogname": "Título do Blueprint", + "blogdescription": "Uma ótima descrição de blog" } } ], @@ -402,29 +578,49 @@ const myBlueprint: BlueprintDeclaration = { ### Montando um plugin programaticamente - + -É possível montar diretórios locais programaticamente usando `runCLI`. As opções `mount` e `mount-before-install` estão disponíveis. A propriedade `hostPath` espera um caminho para um diretório na sua máquina local. Este caminho deve ser relativo a onde seu script está sendo executado. +Você pode montar diretórios locais programaticamente usando `runCLI`. As opções `mount` e `mount-before-install` estão disponíveis. A propriedade `hostPath` espera um caminho para um diretório na sua máquina local. Este caminho deve ser relativo a onde seu script está sendo executado. ```TypeScript - cliServer = await runCLI({ - command: 'server', - login: true, - 'mount-before-install': [ - { - hostPath: './[my-plugin-local-path]', - vfsPath: '/wordpress/wp-content/plugins/my-plugin', - }, - ], - }); +cliServer = await runCLI({ + command: 'server', + login: true, + 'mount-before-install': [ + { + hostPath: './[my-plugin-local-path]', + vfsPath: '/wordpress/wp-content/plugins/my-plugin', + }, + ], +}); ``` - + -Com essas opções podemos combinar a montagem de partes do projeto com blueprints, por exemplo: +**Auto-montagem programática:** ```TypeScript +import { runCLI } from "@wp-playground/cli"; +import process from 'node:process'; + +// Mudar para o diretório do seu projeto +process.chdir('./my-plugin'); + +const cliServer = await runCLI({ + command: 'server', + autoMount: '' // String vazia aciona a detecção automática +}); +``` + + + +### Combinando montagens com blueprints + + +Você pode combinar a montagem de partes do projeto com blueprints, por exemplo: + +```TypeScript import { runCLI, RunCLIArgs, RunCLIServer } from "@wp-playground/cli"; let cliServer: RunCLIServer; @@ -450,3 +646,360 @@ cliServer = await runCLI({ } } as RunCLIArgs); ``` + + + +**Múltiplas montagens com blueprints:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + }, + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } +}); +``` + + + +**Blueprint complexo com múltiplas configurações:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + php: '8.3', + wp: 'latest', + login: true, + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + landingPage: '/wp-admin/plugins.php', + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + }, + { + step: 'setSiteOptions', + options: { + blogname: 'Site de Teste de Plugin', + permalink_structure: '/%postname%/' + } + }, + { + step: 'runPHP', + code: '' + } + ] + } +}); +``` + + + +### Seleção de modo (Blueprint v2) + + + +Você pode especificar diferentes modos ao trabalhar com Blueprint v2: + + + +**Criando um novo site:** + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'create-new-site', + 'mount-before-install': [ + { + hostPath: './my-new-site', + vfsPath: '/wordpress' + } + ] +}); +``` + + + +**Aplicando a um site existente:** + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + 'experimental-blueprints-v2-runner': true, + mode: 'apply-to-existing-site', + 'mount-before-install': [ + { + hostPath: './existing-wordpress', + vfsPath: '/wordpress' + } + ], + blueprint: { + steps: [ + { + step: 'setSiteOptions', + options: { + blogname: 'Nome do Site Atualizado' + } + } + ] + } +}); +``` + + + +## Testes automatizados + + + +### Testes de integração com Vitest + + + +A API programática é excelente para testes automatizados. Aqui está um exemplo completo usando Vitest: + +```TypeScript +import { describe, test, expect, afterEach } from 'vitest'; +import { runCLI, RunCLIServer } from "@wp-playground/cli"; + +describe('Testes do Meu Plugin', () => { + let cliServer: RunCLIServer; + + afterEach(async () => { + if (cliServer) { + await cliServer[Symbol.asyncDispose](); + } + }); + + test('plugin ativa com sucesso', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); + const html = await response.text(); + expect(html).toContain('Meu Plugin'); + }); + + test('página de configurações do plugin carrega', async () => { + cliServer = await runCLI({ + command: 'server', + login: true, // Auto-login como admin + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const settingsUrl = new URL( + '/wp-admin/options-general.php?page=my-plugin', + cliServer.serverUrl + ); + const response = await fetch(settingsUrl); + + expect(response.status).toBe(200); + }); +}); +``` + + + +### Testando personalizações de temas + +```TypeScript +test('tema exibe cabeçalho personalizado', async () => { + cliServer = await runCLI({ + command: 'server', + mount: [ + { + hostPath: './my-theme', + vfsPath: '/wordpress/wp-content/themes/my-theme' + } + ], + blueprint: { + steps: [ + { + step: 'installTheme', + themeData: { + resource: 'vfs', + path: '/wordpress/wp-content/themes/my-theme' + } + }, + { + step: 'activateTheme', + themeFolderName: 'my-theme' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + const html = await response.text(); + + expect(html).toContain('
'); +}); +``` + + + +### Testando um plugin com diferentes versões do WordPress/PHP + +```TypeScript +test('plugin funciona com WordPress 6.4 e PHP 8.0', async () => { + cliServer = await runCLI({ + command: 'server', + php: '8.0', + wp: '6.4', + mount: [ + { + hostPath: './my-plugin', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ], + blueprint: { + steps: [ + { + step: 'activatePlugin', + pluginPath: '/wordpress/wp-content/plugins/my-plugin/plugin.php' + } + ] + } + }); + + const homeUrl = new URL('/', cliServer.serverUrl); + const response = await fetch(homeUrl); + + expect(response.status).toBe(200); +}); +``` + + + +## Configuração avançada + + + +### Pular configuração do WordPress e SQLite + + + +Quando você precisa apenas testar código PHP sem WordPress, pode pular a configuração para testes mais rápidos: + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + skipWordPressSetup: true, + skipSqliteSetup: true, + php: '8.3' +}); + +// Escrever e testar scripts PHP personalizados +await cliServer.playground.writeFile( + '/wordpress/test.php', + '' +); + +const testUrl = new URL('/test.php', cliServer.serverUrl); +const response = await fetch(testUrl); +console.log(await response.text()); // Saída: Olá do PHP! +``` + + + +### Tratamento de erros + +```TypeScript +import { runCLI } from "@wp-playground/cli"; + +try { + const cliServer = await runCLI({ + command: 'server', + debug: true // Habilitar registro de erros do PHP + }); + + // Seu código de teste aqui + +} catch (error) { + console.error('Falha ao iniciar servidor:', error); +} +``` + + + +### Seguindo links simbólicos programaticamente + +```TypeScript +const cliServer = await runCLI({ + command: 'server', + followSymlinks: true, + 'mount-before-install': [ + { + hostPath: './symlinked-directory', + vfsPath: '/wordpress/wp-content/plugins/my-plugin' + } + ] +}); +``` + +:::caution + + + +Usar links simbólicos pode expor arquivos fora dos diretórios montados. Habilite este recurso apenas quando confiar nos destinos dos links simbólicos. +::: From bcc8beefa2892ed15d66da580864943213dfb220 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 11:06:19 +0000 Subject: [PATCH 05/10] removing duplicated section --- .../04-wp-playground-cli.md | 45 ++----------- .../04-wp-playground-cli.md | 63 +++---------------- .../04-wp-playground-cli.md | 63 +++---------------- 3 files changed, 18 insertions(+), 153 deletions(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index eb62a26b7b..ad78329716 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -28,58 +28,21 @@ npx @wp-playground/cli@latest server ![Playground CLI in Action](@site/static/img/developers/npx-wp-playground-server.gif) -With the previous command, you only get a fresh WordPress instance to test. Most developers will want to test their own work. To test a plugin or a theme, navigate to your project folder and run the CLI with the `--auto-mount` flag: +With the previous command, you only get a fresh WordPress instance to test. Most developers will want to test their own work. To test a plugin or a theme, navigate to your project folder and run the CLI with the `--auto-mount` flag. -```bash -cd my-plugin-or-theme-directory -npx @wp-playground/cli@latest server --auto-mount -``` - -### Auto-mounting different project types - -The `--auto-mount` flag intelligently detects your project type and mounts it appropriately: - -**Plugin directory:** +The `--auto-mount` flag intelligently detects your project type and mounts it to the appropriate location in WordPress. When you run the command from your project directory, Playground CLI analyzes the directory structure and automatically determines whether you're working with a plugin, theme, wp-content directory, full WordPress installation, or static HTML/PHP files. It then mounts your project to the correct path in the virtual WordPress environment, so you can start developing immediately without manual configuration. ```bash cd my-plugin npx @wp-playground/cli@latest server --auto-mount ``` -**Theme directory:** - -```bash -cd my-theme -npx @wp-playground/cli@latest server --auto-mount -``` - -**wp-content directory:** - -```bash -cd my-site/wp-content -npx @wp-playground/cli@latest server --auto-mount -``` - -**Full WordPress installation:** - -```bash -cd my-wordpress -npx @wp-playground/cli@latest server --auto-mount -``` - -**Static HTML/PHP project:** - -```bash -cd my-static-site -npx @wp-playground/cli@latest server --auto-mount -``` - ### Choosing a WordPress and PHP version -By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due to its improved performance. To specify your preferred versions, you can use the flag `--wp=` and `--php=`: +By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due to its improved performance. You can specify different versions using the `--wp=` and `--php=` flags. This is particularly useful when you need to test your plugin or theme for compatibility across different WordPress and PHP versions, ensuring your code works correctly for users running older installations. ```bash -npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 +npx @wp-playground/cli@latest server --wp=6.4 --php=8.0 ``` ### Setting a custom site URL diff --git a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index a05c8d156b..a146f8c737 100644 --- a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -46,78 +46,29 @@ npx @wp-playground/cli@latest server ![Playground CLI en Acción](@site/static/img/developers/npx-wp-playground-server.gif) - + -Con el comando anterior, solo obtienes una instancia fresca de WordPress para probar. La mayoría de los desarrolladores querrán probar su propio trabajo. Para probar un plugin o un tema, navega a la carpeta de tu proyecto y ejecuta el CLI con la bandera `--auto-mount`: +Con el comando anterior, solo obtienes una instancia fresca de WordPress para probar. La mayoría de los desarrolladores querrán probar su propio trabajo. Para probar un plugin o un tema, navega a la carpeta de tu proyecto y ejecuta el CLI con la bandera `--auto-mount`. -```bash -cd my-plugin-or-theme-directory -npx @wp-playground/cli@latest server --auto-mount -``` - - - -### Auto-montaje de diferentes tipos de proyectos - - - -La bandera `--auto-mount` detecta inteligentemente tu tipo de proyecto y lo monta apropiadamente: - - + -**Directorio de plugin:** +La bandera `--auto-mount` detecta inteligentemente tu tipo de proyecto y lo monta en la ubicación apropiada en WordPress. Cuando ejecutas el comando desde tu directorio de proyecto, Playground CLI analiza la estructura del directorio y determina automáticamente si estás trabajando con un plugin, tema, directorio wp-content, instalación completa de WordPress o archivos estáticos HTML/PHP. Luego monta tu proyecto en la ruta correcta en el entorno WordPress virtual, para que puedas comenzar a desarrollar inmediatamente sin configuración manual. ```bash cd my-plugin npx @wp-playground/cli@latest server --auto-mount ``` - - -**Directorio de tema:** - -```bash -cd my-theme -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Directorio wp-content:** - -```bash -cd my-site/wp-content -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Instalación completa de WordPress:** - -```bash -cd my-wordpress -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Proyecto estático HTML/PHP:** - -```bash -cd my-static-site -npx @wp-playground/cli@latest server --auto-mount -``` - ### Elegir una Versión de WordPress y PHP - + -Por defecto, el CLI carga la última versión estable de WordPress y PHP 8.3 debido a su rendimiento mejorado. Para especificar tus versiones preferidas, puedes usar las banderas `--wp=` y `--php=`: +Por defecto, el CLI carga la última versión estable de WordPress y PHP 8.3 debido a su rendimiento mejorado. Puedes especificar versiones diferentes usando las banderas `--wp=` y `--php=`. Esto es particularmente útil cuando necesitas probar tu plugin o tema para compatibilidad en diferentes versiones de WordPress y PHP, asegurando que tu código funcione correctamente para usuarios ejecutando instalaciones más antiguas. ```bash -npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 +npx @wp-playground/cli@latest server --wp=6.4 --php=8.0 ``` diff --git a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index 47e897e082..428464e126 100644 --- a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -46,78 +46,29 @@ npx @wp-playground/cli@latest server ![Playground CLI em Ação](@site/static/img/developers/npx-wp-playground-server.gif) - + -Com o comando anterior, você obtém apenas uma instância WordPress fresca para testar. A maioria dos desenvolvedores vai querer testar seu próprio trabalho. Para testar um plugin ou tema, navegue até a pasta do seu projeto e execute o CLI com a flag `--auto-mount`: +Com o comando anterior, você obtém apenas uma instância WordPress fresca para testar. A maioria dos desenvolvedores vai querer testar seu próprio trabalho. Para testar um plugin ou tema, navegue até a pasta do seu projeto e execute o CLI com a flag `--auto-mount`. -```bash -cd my-plugin-or-theme-directory -npx @wp-playground/cli@latest server --auto-mount -``` - - - -### Auto-montagem de diferentes tipos de projetos - - - -A flag `--auto-mount` detecta inteligentemente o tipo do seu projeto e o monta apropriadamente: - - + -**Diretório de plugin:** +A flag `--auto-mount` detecta inteligentemente o tipo do seu projeto e o monta no local apropriado no WordPress. Quando você executa o comando do diretório do seu projeto, o Playground CLI analisa a estrutura do diretório e determina automaticamente se você está trabalhando com um plugin, tema, diretório wp-content, instalação completa do WordPress ou arquivos estáticos HTML/PHP. Ele então monta seu projeto no caminho correto no ambiente WordPress virtual, para que você possa começar a desenvolver imediatamente sem configuração manual. ```bash cd my-plugin npx @wp-playground/cli@latest server --auto-mount ``` - - -**Diretório de tema:** - -```bash -cd my-theme -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Diretório wp-content:** - -```bash -cd my-site/wp-content -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Instalação completa do WordPress:** - -```bash -cd my-wordpress -npx @wp-playground/cli@latest server --auto-mount -``` - - - -**Projeto estático HTML/PHP:** - -```bash -cd my-static-site -npx @wp-playground/cli@latest server --auto-mount -``` - ### Escolhendo uma Versão do WordPress e PHP - + -Por padrão, o CLI carrega a versão estável mais recente do WordPress e PHP 8.3 devido ao seu desempenho melhorado. Para especificar suas versões preferidas, você pode usar as flags `--wp=` e `--php=`: +Por padrão, o CLI carrega a versão estável mais recente do WordPress e PHP 8.3 devido ao seu desempenho melhorado. Você pode especificar versões diferentes usando as flags `--wp=` e `--php=`. Isso é particularmente útil quando você precisa testar seu plugin ou tema para compatibilidade em diferentes versões do WordPress e PHP, garantindo que seu código funcione corretamente para usuários executando instalações mais antigas. ```bash -npx @wp-playground/cli@latest server --wp=6.8 --php=8.3 +npx @wp-playground/cli@latest server --wp=6.4 --php=8.0 ``` From ae0ad3cc2dce21fcf64e64320ee7bd15eae68e09 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 12:59:01 +0000 Subject: [PATCH 06/10] removing uncessary demo --- .../05-local-development/04-wp-playground-cli.md | 6 ------ .../05-local-development/04-wp-playground-cli.md | 8 -------- .../05-local-development/04-wp-playground-cli.md | 8 -------- 3 files changed, 22 deletions(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index ad78329716..8fb1dd4a20 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -53,12 +53,6 @@ You can configure a custom site URL for your development environment, which is u npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test ``` -You can also specify a custom port: - -```bash -npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 -``` - ### Loading blueprints One way to take your Playground CLI development experience to the next level is to integrate with [Blueprints](/blueprints/getting-started/). For those unfamiliar with this technology, it allows developers to configure the initial state for their WordPress Playground instances. diff --git a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index a146f8c737..465d4ccf5a 100644 --- a/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/es/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -83,14 +83,6 @@ Puedes configurar una URL de sitio personalizada para tu entorno de desarrollo, npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test ``` - - -También puedes especificar un puerto personalizado: - -```bash -npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 -``` - ### Cargar Blueprints diff --git a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md index 428464e126..31b5496da5 100644 --- a/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/i18n/pt-BR/docusaurus-plugin-content-docs/current/developers/05-local-development/04-wp-playground-cli.md @@ -83,14 +83,6 @@ Você pode configurar uma URL de site personalizada para seu ambiente de desenvo npx @wp-playground/cli@latest server --site-url=https://my-local-dev.test ``` - - -Você também pode especificar uma porta personalizada: - -```bash -npx @wp-playground/cli@latest server --port=3000 --site-url=http://localhost:3000 -``` - ### Carregando Blueprints From 2f4f3abc7923b65e5137bf58f91fc9fa74e13206 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 15:56:31 +0000 Subject: [PATCH 07/10] Update packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Adam Zieliński --- .../developers/05-local-development/04-wp-playground-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 8fb1dd4a20..903a0fb67f 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -30,7 +30,7 @@ npx @wp-playground/cli@latest server With the previous command, you only get a fresh WordPress instance to test. Most developers will want to test their own work. To test a plugin or a theme, navigate to your project folder and run the CLI with the `--auto-mount` flag. -The `--auto-mount` flag intelligently detects your project type and mounts it to the appropriate location in WordPress. When you run the command from your project directory, Playground CLI analyzes the directory structure and automatically determines whether you're working with a plugin, theme, wp-content directory, full WordPress installation, or static HTML/PHP files. It then mounts your project to the correct path in the virtual WordPress environment, so you can start developing immediately without manual configuration. +The `--auto-mount` flag analyzes the directory structure and automatically determines whether you're working with a plugin, theme, wp-content directory, full WordPress installation, or static HTML/PHP files. It then mounts your project to the correct path in the virtual WordPress environment, so you can start developing immediately without manual configuration. ```bash cd my-plugin From f8f2357a83cf1deaa9371518338c816d5bf01da1 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 15:56:44 +0000 Subject: [PATCH 08/10] Update packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Adam Zieliński --- .../developers/05-local-development/04-wp-playground-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 903a0fb67f..8f62e314c5 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -39,7 +39,7 @@ npx @wp-playground/cli@latest server --auto-mount ### Choosing a WordPress and PHP version -By default, the CLI loads the latest stable version of WordPress and PHP 8.3 due to its improved performance. You can specify different versions using the `--wp=` and `--php=` flags. This is particularly useful when you need to test your plugin or theme for compatibility across different WordPress and PHP versions, ensuring your code works correctly for users running older installations. +By default, the CLI loads PHP 8.3 and the latest stable version of WordPress. You can specify different versions using the `--wp=` and `--php=` flags. This is particularly useful when you need to test your plugin or theme for compatibility across different WordPress and PHP versions, ensuring your code works correctly for users running older installations. ```bash npx @wp-playground/cli@latest server --wp=6.4 --php=8.0 From 42a3123881d758d8f3187adb89dc5f1e0458ddbf Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 15:57:04 +0000 Subject: [PATCH 09/10] Update packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Adam Zieliński --- .../05-local-development/04-wp-playground-cli.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 8f62e314c5..1cc76da436 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -103,7 +103,18 @@ npx @wp-playground/cli@latest server --mount-before-install=.:/wordpress/ ### Symlink support for monorepos -If you're working in a monorepo or complex project structure where packages are symlinked, you can enable symlink following: +Sometimes you're working with a complex project structure where directories are symlinked to another location on the disk, e.g.: + +``` +/home/alex/my-project +└── wp-content + └── plugins + ├── hello-dolly/ # regular directory + └── secret-plugin → /home/www/plugins/secret-plugin +``` + +By default, Playground CLI only accesses the directories you explicitly mount and won't any load files from `/home/www/plugins/secret-plugin`. You can, however, explicitly instruct Playground CLI to follow that, and other, symlinks with the `--follow-symlink` option: + ```bash npx @wp-playground/cli@latest server \ From 8e2b3f155172a084f43b146d67d991d1b1e49cb5 Mon Sep 17 00:00:00 2001 From: Fellyph Cintra Date: Tue, 28 Oct 2025 18:05:14 +0000 Subject: [PATCH 10/10] Update packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Adam Zieliński --- .../developers/05-local-development/04-wp-playground-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md index 1cc76da436..8c40b8275a 100644 --- a/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md +++ b/packages/docs/site/docs/developers/05-local-development/04-wp-playground-cli.md @@ -197,7 +197,7 @@ npx @wp-playground/cli@latest server --mount=./wp-content:/wordpress/wp-content ## Verbosity and debugging -The CLI supports different verbosity levels to control output, for `quiet`, `normal` and `debug` mode. The default mode is `normal`. For quiet mode, run the server with no output (useful for scripts and automation): +The CLI supports different output verbosity levels for `quiet`, `normal` (default) and `debug` mode. Sometimes you want to hide all the stdout output, e.g. in a script or a CI automation. You can do that using the `--verbosity=quiet` option: ```bash npx @wp-playground/cli@latest server --verbosity=quiet