Update Nx, Vite, and ESLint dependencies (#35)

## Motivation for the change, related issues

When I am learning about Nx or Vite or troubleshooting potential issues
with them, I find that our versions are old enough that I am not sure
whether docs and merged bug fixes apply the versions we're using.

This is a PR to explore updating and dispelling that uncertainty and
doubt.

**UPDATE (2025-04-16)** This PR is also required in order to use the
[eslint-plugin-erasable-syntax-only](https://www.npmjs.com/package/eslint-plugin-erasable-syntax-only)
package. That package depends on a newer ESLint version than we're using
today, and we cannot update that separately because our older version of
Nx depends on an older ESLint.

## Implementation details

- Use `nx migrate` to migrate to latest feasible version.
- Update Vite dependencies to latest versions compatible with the nx
packages.
- Fix any issues

## Testing Instructions (or ideally a Blueprint)

- CI

Author: brandonpayton

package-lock.json

@@ -65,15 +65,15 @@
 	"private": true,
 	"dependencies": {
 		"@preact/signals-react": "1.3.6",
-		"@reduxjs/toolkit": "2.2.5",
+		"@reduxjs/toolkit": "2.6.1",
 		"@types/ini": "4.1.0",
 		"@types/react-transition-group": "4.4.11",
 		"@types/wicg-file-system-access": "2023.10.5",
 		"@wordpress/dataviews": "4.5.0",
 		"@zip.js/zip.js": "2.7.57",
 		"ajv": "8.12.0",
 		"async-lock": "1.4.1",
-		"axios": "1.6.1",
+		"axios": "1.7.9",
 		"classnames": "^2.3.2",
 		"comlink": "^4.4.1",
 		"crc-32": "1.2.2",
@@ -85,66 +85,64 @@
 		"octokit": "3.1.1",
 		"octokit-plugin-create-pull-request": "5.1.1",
 		"pako": "1.0.10",
-		"react": "^18.2.25",
-		"react-dom": "^18.2.25",
+		"react": "18.3.1",
+		"react-dom": "18.3.1",
 		"react-hook-form": "7.53.0",
 		"react-modal": "^3.16.1",
 		"react-redux": "8.1.3",
 		"react-transition-group": "4.4.5",
 		"sha.js": "2.4.11",
 		"sha1": "1.1.1",
 		"unzipper": "0.10.11",
-		"vite-plugin-api": "1.0.4",
 		"wasm-feature-detect": "1.8.0",
 		"wouter": "3.3.5",
 		"xterm": "5.3.0",
 		"xterm-addon-fit": "0.8.0",
 		"yargs": "17.7.2"
 	},
 	"devDependencies": {
-		"@docusaurus/core": "2.4.1",
-		"@docusaurus/module-type-aliases": "2.4.1",
-		"@docusaurus/plugin-client-redirects": "2.4.1",
-		"@docusaurus/plugin-ideal-image": "^2.4.1",
-		"@docusaurus/preset-classic": "2.4.1",
-		"@docusaurus/theme-live-codeblock": "^2.4.1",
-		"@mdx-js/react": "^1.6.22",
-		"@nx/cypress": "16.9.0",
-		"@nx/devkit": "16.9.0",
-		"@nx/esbuild": "16.9.0",
-		"@nx/eslint-plugin": "16.9.0",
-		"@nx/jest": "16.9.0",
-		"@nx/js": "16.9.0",
-		"@nx/linter": "16.9.0",
-		"@nx/node": "16.9.0",
-		"@nx/plugin": "16.9.0",
-		"@nx/react": "16.9.0",
-		"@nx/rollup": "16.9.0",
-		"@nx/vite": "16.9.0",
-		"@nx/web": "16.9.0",
-		"@nx/webpack": "16.9.0",
-		"@nx/workspace": "16.9.0",
+		"@docusaurus/core": "3.7.0",
+		"@docusaurus/module-type-aliases": "3.7.0",
+		"@docusaurus/plugin-client-redirects": "3.7.0",
+		"@docusaurus/plugin-ideal-image": "^3.7.0",
+		"@docusaurus/preset-classic": "3.7.0",
+		"@docusaurus/theme-live-codeblock": "^3.7.0",
+		"@docusaurus/tsconfig": "^3.7.0",
+		"@mdx-js/react": "^3.1.0",
+		"@nx/cypress": "19.8.4",
+		"@nx/devkit": "19.8.4",
+		"@nx/esbuild": "19.8.4",
+		"@nx/eslint-plugin": "19.8.4",
+		"@nx/jest": "19.8.4",
+		"@nx/js": "19.8.4",
+		"@nx/linter": "19.8.4",
+		"@nx/node": "19.8.4",
+		"@nx/plugin": "19.8.4",
+		"@nx/react": "19.8.4",
+		"@nx/rollup": "19.8.4",
+		"@nx/vite": "19.8.4",
+		"@nx/web": "19.8.4",
+		"@nx/webpack": "19.8.4",
+		"@nx/workspace": "19.8.4",
 		"@playwright/test": "1.47.1",
-		"@rollup/plugin-url": "^8.0.1",
-		"@swc-node/register": "~1.6.7",
-		"@swc/core": "~1.3.85",
-		"@testing-library/react": "14.0.0",
-		"@tsconfig/docusaurus": "^1.0.5",
+		"@rollup/plugin-url": "8.0.2",
+		"@swc-node/register": "1.9.2",
+		"@swc/core": "1.5.7",
+		"@testing-library/react": "15.0.6",
 		"@types/ajv": "1.0.0",
 		"@types/file-saver": "^2.0.5",
-		"@types/jest": "^29.4.0",
-		"@types/node": "20.9.0",
-		"@types/react": "18.3.3",
+		"@types/jest": "29.5.14",
+		"@types/node": "20.14.8",
+		"@types/react": "18.3.1",
 		"@types/react-dom": "18.3.0",
 		"@types/react-modal": "3.16.3",
 		"@types/tar-fs": "2.0.4",
 		"@types/wordpress__block-editor": "11.5.15",
 		"@types/wordpress__blocks": "12.5.14",
-		"@typescript-eslint/eslint-plugin": "5.62.0",
-		"@typescript-eslint/parser": "5.62.0",
-		"@vitejs/plugin-react": "4.2.0",
-		"@vitest/coverage-c8": "0.32.4",
-		"@vitest/ui": "0.32.4",
+		"@typescript-eslint/eslint-plugin": "8.30.1",
+		"@typescript-eslint/parser": "8.30.1",
+		"@vitejs/plugin-react": "4.3.4",
+		"@vitest/ui": "2.1.9",
 		"@wordpress/block-editor": "13.4.0",
 		"@wordpress/blocks": "13.4.0",
 		"@wordpress/components": "28.4.0",
@@ -154,39 +152,39 @@
 		"@wordpress/notices": "5.4.0",
 		"chalk": "5.2.0",
 		"clsx": "^1.2.1",
-		"cypress": "^13.0.0",
-		"docusaurus-plugin-typedoc-api": "^3.0.0",
+		"cypress": "13.17.0",
+		"docusaurus-plugin-typedoc-api": "^4.4.0",
 		"dts-bundle-generator": "^7.2.0",
-		"esbuild": "0.19.7",
+		"esbuild": "0.19.9",
 		"esbuild-node-externals": "1.13.1",
 		"esbuild-plugin-copy": "^2.1.0",
 		"esbuild-plugin-ignore": "1.1.1",
-		"eslint": "8.46.0",
-		"eslint-config-prettier": "8.1.0",
-		"eslint-plugin-comment-length": "1.7.3",
-		"eslint-plugin-cypress": "^2.13.4",
-		"eslint-plugin-import": "2.27.5",
-		"eslint-plugin-jsx-a11y": "6.7.1",
+		"eslint": "9.24.0",
+		"eslint-config-prettier": "9.1.0",
+		"eslint-plugin-comment-length": "2.2.1",
+		"eslint-plugin-cypress": "^4.2.1",
+		"eslint-plugin-import": "2.31.0",
+		"eslint-plugin-jsx-a11y": "6.10.2",
 		"eslint-plugin-playground-dev": "file:packages/meta/src/eslint-plugin-playground-dev",
-		"eslint-plugin-react": "7.32.2",
-		"eslint-plugin-react-hooks": "4.6.0",
+		"eslint-plugin-react": "7.37.5",
+		"eslint-plugin-react-hooks": "5.2.0",
 		"gh-pages": "5.0.0",
 		"glob": "^9.3.0",
 		"husky": "8.0.3",
-		"jest": "^29.4.1",
-		"jest-environment-jsdom": "^29.4.1",
+		"jest": "29.7.0",
+		"jest-environment-jsdom": "29.7.0",
 		"jest-environment-node": "^29.4.1",
 		"jsdom": "22.1.0",
 		"jsonc-eslint-parser": "^2.1.0",
 		"lerna": "6.6.2",
-		"nx": "16.9.0",
+		"nx": "19.8.4",
 		"ora": "6.3.0",
 		"prettier": "^2.6.2",
 		"prism-react-renderer": "^1.3.5",
 		"raw-loader": "^4.0.2",
 		"react-markdown": "^8.0.7",
 		"rimraf": "^4.4.0",
-		"rollup": "^3.2.0",
+		"rollup": "^4.34.6",
 		"rollup-plugin-dts": "^5.2.0",
 		"rollup-plugin-external-globals": "0.7.3",
 		"rollup-plugin-ts": "^3.2.0",
@@ -197,22 +195,21 @@
 		"tslib": "^2.3.0",
 		"typedoc": "0.23.27",
 		"typescript": "5.4.5",
-		"vite": "4.5.0",
+		"vite": "^5.0.0",
 		"vite-plugin-dts": "3.6.3",
 		"vite-plugin-eslint": "^1.8.1",
 		"vite-plugin-external": "1.2.8",
-		"vite-plugin-static-copy": "0.13.1",
+		"vite-plugin-static-copy": "2.2.0",
 		"vite-plugin-wasm": "^3.2.2",
 		"vite-tsconfig-paths": "4.2.0",
 		"vitepress": "1.0.0-alpha.60",
-		"vitest": "0.32.4",
+		"vitest": "2.1.9",
 		"webpack-node-externals": "^3.0.0"
 	},
 	"overrides": {
-		"nx": "16.9.0",
-		"rollup": "^3.2.0",
-		"react": "^18.2.25",
-		"react-dom": "^18.2.25",
+		"rollup": "^4.34.6",
+		"react": "18.3.1",
+		"react-dom": "18.3.1",
 		"typescript": "5.4.5",
 		"typedoc": "0.23.27",
 		"ws": "^8.18.0"

package.json

@@ -47,6 +47,8 @@ Blueprints fetch any resources you declare for you. You don't have to worry abou
 
 Because Blueprints can be pasted in the URL, you can embed or link to a Playground with a specific configuration. For example, clicking this button will open a Playground with PHP 7.4 and a pendant theme installed:
 
+import BlueprintExample from '@site/src/components/Blueprints/BlueprintExample.mdx';
+
 <BlueprintExample justButton={true} blueprint={{
 	"preferredVersions": {
 		"php": "7.4",

packages/docs/site/docs/blueprints/01-index.md

@@ -50,7 +50,7 @@ nx recompile-php php-wasm-web
 
 **Supported build options:**
 
--   `PHP_VERSION` – The PHP version to build, default: `8.0.24`. This value must point to an existing branch of the <https://github.com/php/php-src.git> repository when prefixed with `PHP-`. For example, `7.4.0` is valid because the branch `PHP-7.4.0` exists, but just `7` is invalid because there's no branch `PHP-7`. The PHP versions that are known to work are `7.4.*` and `8.0.*`. Others likely work as well but they haven't been tried.
+-   `PHP_VERSION` – The PHP version to build, default: `8.0.24`. This value must point to an existing branch of the https://github.com/php/php-src.git repository when prefixed with `PHP-`. For example, `7.4.0` is valid because the branch `PHP-7.4.0` exists, but just `7` is invalid because there's no branch `PHP-7`. The PHP versions that are known to work are `7.4.*` and `8.0.*`. Others likely work as well but they haven't been tried.
 -   `EMSCRIPTEN_ENVIRONMENT` – `web` or `node`, default: `web`. The platform to build for. When building for `web`, two JavaScript loaders will be created: `php-web.js` and `php-webworker.js`. When building for Node.js, only one loader called `php-node.js` will be created.
 -   `WITH_LIBXML` – `yes` or `no`, default: `no`. Whether to build with `libxml2` and the `dom`, `xml`, and `simplexml` PHP extensions (`DOMDocument`, `SimpleXML`, ..).
 -   `WITH_LIBZIP` – `yes` or `no`, default: `yes`. Whether to build with `zlib`, `libzip`, and the `zip` PHP extension (`ZipArchive`).

packages/docs/site/docs/developers/23-architecture/03-wasm-php-compiling.md

@@ -2,7 +2,7 @@
 title: How does it work?
 ---
 
-## Database is supported via MySQL<->SQLite translation layer
+## Database is supported via MySQL\<\-\>SQLite translation layer
 
 WordPress requires MySQL. However, there isn't a WebAssembly version of MySQL you could run in the browser. WordPress Playground therefore ships PHP with the [native SQLite driver](https://www.php.net/manual/en/ref.pdo-sqlite.php) and leans on SQLite.
 

packages/docs/site/docs/developers/23-architecture/16-wordpress-database.md

@@ -27,7 +27,7 @@ Also, JavaScript popups originating in the `iframe` may not always display.
 
 ### Run WordPress PHP functions
 
-Playground supports running PHP code in Blueprints using the [`runPHP` step](blueprints/steps#RunPHPStep). To run WordPress-specific PHP functions, you’d need to first require [wp-load.php](https://github.com/WordPress/WordPress/blob/master/wp-load.php):
+Playground supports running PHP code in Blueprints using the [`runPHP` step](/blueprints/steps#RunPHPStep). To run WordPress-specific PHP functions, you’d need to first require [wp-load.php](https://github.com/WordPress/WordPress/blob/master/wp-load.php):
 
 ```json
 {