[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core

[WordPress Trac]

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  reopened
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by dmsnell):

 All, as I tend to do from time to time I overreacted and was needlessly
 emotionally charged when I wrote my comments. I apologize for any
 disrespect I showed towards @youknowriad or others working on this.

 In response I’ve updated my comments to better reflect what I hope is more
 helpful commentary, summarized here:

  - Can we ensure that we find a way to make Core build without introducing
 network dependencies after cloning? or certainly after having run `npm
 install`? As someone who frequently works tethered to a capped data plan,
 it’s not sustainable for me to wait for hundreds of megabytes of
 compressed JS files to download and build when working.
  - Can we adjust this so that nothing more than an absolutely minimum
 build is required for WordPress to function? Releases cannot have stale
 files, but I work productively in stale files all the time. I am not 100%
 always on the latest `trunk`, and I will not always have the latest JS
 files built either, but that doesn’t impede me from working on email, or
 HTML safety, or on web standards support. If and when I realize that
 things are broken I can choose to run the update and the build.
  - Can we //immediately// stop running multiple `git` fetches, especially
 when they aren’t necessary. `git` is immutable, and if we have the `ref`
 there’s no need to try to fetch it again. At a minimum, if we have a
 commit SHA it’s essentially free to check if the ref is already fetched.
  - Similarly, can we avoid running `npm ci` if the `ref` is unchanged
 since the last run? or ideally gate it behind a CLI arg or an ENV value so
 that it doesn't constantly run and download and reinstall packages?

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