[wp-trac] [WordPress Trac] #63254: Introduce development mode for block editor styles

[WordPress Trac]

#63254: Introduce development mode for block editor styles
--------------------------------------------------+-----------------------
 Reporter:  helgatheviking                        |       Owner:  audrasjb
     Type:  defect (bug)                          |      Status:  accepted
 Priority:  normal                                |   Milestone:  6.8.2
Component:  Editor                                |     Version:  5.5
 Severity:  normal                                |  Resolution:
 Keywords:  has-patch dev-feedback needs-testing  |     Focuses:
--------------------------------------------------+-----------------------

Comment (by rollybueno):

 == Test Report
 === Description
 This report validates whether the indicated patch works as expected.

 Patch tested: https://github.com/WordPress/wordpress-develop/pull/8725

 === Environment
 - WordPress: 6.9-alpha-60093-src
 - PHP: 8.2.28
 - Server: nginx/1.27.5
 - Database: mysqli (Server: 8.4.5 / Client: mysqlnd 8.2.28)
 - Browser: Chrome 137.0.0.0
 - OS: Linux
 - Theme: Twenty Twenty-Five 1.2
 - MU Plugins: None activated
 - Plugins:
   * Block Development Boilerplate 0.1.0
   * Test Reports 1.2.0

 === Actual Results
 1. ✅ Created a custom block using the official guide:
 https://developer.wordpress.org/block-editor/reference-guides/packages
 /packages-create-block/
 2. ✅ Tested on trunk (before applying the patch) and confirmed the `ver`
 query parameter for `style.css` did not use timestamp for cache-busting.
 3. ✅ Applied the patch from [https://github.com/WordPress/wordpress-
 develop/pull/8725], then ran `npm run env:stop` and restarted Docker to
 flush caching.
 4. ✅ After restart, modifying the block correctly triggered a version
 bump in the `ver` query parameter.
 5. ✅ The issue is no longer reproducible after applying the patch.

 === Additional Notes
 - Restarting Docker after applying the patch was essential to invalidate
 cached data and properly confirm the fix.
 - The patch ensures that block assets are properly cache-busted when a
 custom block is updated during development.

 === Supplemental Artifacts
 **TRUNK**: You can clearly see here that the custom block `ver` param is
 using ''Version'' value from plugin header, which in my case is 0.1.0
 [[Image(https://i.imgur.com/7ueDIDw.png)]]

 https://github.com/WordPress/wordpress-develop/pull/8725 - After checking
 out to this PR, restarting Docker, I can see the same plugin asset is now
 using cache-busting patch from this specific line of code:
 https://github.com/WordPress/wordpress-develop/pull/8725/files#diff-
 8c99af92e4ec0fdb307ddd9b42be1e1ef1efe4a9f31287c23f346244dddd1ce9R332
 [[Image(https://i.imgur.com/5JhluCv.png)]]

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