[wp-trac] [WordPress Trac] #64618: Playground Node.js engine requirement broke Core WP builds

[WordPress Trac]

#64618: Playground Node.js engine requirement broke Core WP builds
------------------------------+------------------------------
 Reporter:  bpayton           |       Owner:  youknowriad
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by berislav.grgicak):

 From now on, I think that staying on the same Node version as Core is a
 good move and that we should downgrade Playground's Node version to match
 Core.

 As @bpayton mentioned, Playground benefits from newer versions of Node,
 and it's in our interest to upgrade. At the same time, we don't want to
 prevent projects from updating to the latest Playground version just
 because we increased the minimum Node version.

 Before every Node version update, we usually check with projects like
 Studio if they already use the newer Node version and wait for the upgrade
 if they don't.

 Until recently, Core didn't use Playground, so we didn't consider
 maintaining support for Core's Node version.

 To avoid issues like this in the future, we could add a simple CI check
 that ensures Playground's Node version matches or is below Core's Node
 version.

 When it comes to Playground features like JSPI, we can document that its
 support depends on a newer Node version.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64618#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform