[wp-trac] [WordPress Trac] #61734: Add the ability to handle "fetchpriority" to ES Modules and Import Maps

WordPress Trac noreply at wordpress.org
Thu Oct 23 18:55:57 UTC 2025


#61734: Add the ability to handle "fetchpriority" to ES Modules and Import Maps
-------------------------------------+-------------------------------------
 Reporter:  dennysdionigi            |       Owner:  westonruter
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.9
Component:  Script Loader            |     Version:  6.5
 Severity:  minor                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-      |     Focuses:  javascript,
  tests needs-dev-note               |  performance
-------------------------------------+-------------------------------------

Comment (by johnbillion):

 I'm not sure it makes much difference for QM. The main thing QM does is
 recursively builds the full list of all modules required on the page using
 the `dependencies` element in the array that was previously returned by
 `get_dependencies()`. It now fetches the array of module data from the
 `WP_Script_Modules::$registered` property (which is also not public).

 If `get_dependencies()` was restored to its previous shape and made public
 that would be nice but all it would really do it prevent manual calls to
 the `registered` property.

 Here are the non-public methods and properties that QM has to query to
 build a list of the enqueued modules and build the full list of dependent
 modules: https://github.com/johnbillion/query-
 monitor/blob/f7ec89b87d88bd66f68bca52d2e4f2c679b63c04/classes/Collector_Assets.php#L295-L305

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


More information about the wp-trac mailing list