[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:
------------------------------+--------------------------
Changes (by peterwilsoncc):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for notes in [https://github.com/WordPress/wordpress-
 develop/pull/10725#issuecomment-3767692119 PR#10725] and [comment:35
 comment #35] which I've been able to reproduce.

 Additionally the hash check needs to take place at the start of each grunt
 command along with the install changed check, see
 [https://github.com/WordPress/wordpress-
 develop/blob/16aa10f04dfaa8b9084f05213a9371526dc3e79b/Gruntfile.js#L98-L99
 Gruntfile.js#L98-L99].

 For package changes, they need to be detected on each build task. I
 usually run `npm run grunt clean:qunit` to trigger it as it's nice and
 quick:

 1. Modify an npm dependency
 2. Run `npm run grunt clean:qunit`
 3. Observe reinstall trigger
 4. Modify Gutenberg hash
 5. Run `npm run grunt clean:qunit`
 6. Observe GB update fails.

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