Context Navigation

Changes between Initial Version and Version 1 of Ticket #64618, comment 1

initial	v1
1	1	@youknowriad, it would be great if Playground did not have to coordinate Node.js version compatibility with Core, but I'm not sure if that is reasonable to avoid.
2	2
3		Given that `wp-env` ~~uses `npx` to launch `@wp-playground/cli`~~, we could technically remove the declared dependency from the `wp-env` package.json to avoid engine version conflicts based on package.json. But `wp-env` users on Node.js 20.x won't be able to use the Playground mode unless they upgrade to a Playground-compatible Node.js version.
	3	Given that `wp-env` [https://github.com/WordPress/gutenberg/blob/2472df3b94769892778f9f396b5d8607caeac554/packages/env/lib/runtime/playground/index.js#L188 uses npx to launch Playground CLI], we could technically remove the declared dependency from the `wp-env` package.json to avoid engine version conflicts based on package.json. But `wp-env` users on Node.js 20.x won't be able to use the Playground mode unless they upgrade to a Playground-compatible Node.js version.
4	4
5	5	It's technically possible that Playground could fall behind Core's required Node.js version, but it seems unlikely because Playground is constantly needing to leverage bleeding-edge JS runtime features.