[wp-trac] [WordPress Trac] #60478: Upgrade to jQuery 4.0

WordPress Trac noreply at wordpress.org
Sun Jan 18 12:59:14 UTC 2026


#60478: Upgrade to jQuery 4.0
-------------------------------------+-------------------------------------
 Reporter:  nickchomey               |       Owner:  (none)
     Type:  task (blessed)           |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  External Libraries       |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch needs-       |     Focuses:  javascript,
  testing                            |  performance
-------------------------------------+-------------------------------------

Comment (by nickchomey):

 Replying to [comment:34 TobiasBg]:
 > However, several already deprecated API methods (e.g. those that now
 have native JS alternatives) have been removed, which could have an impact
 on plugins that are (still) using them (despite long-existing deprecation
 warnings).

 I use a variety of plugins where jQuery-migrate already logs deprecation
 warnings. I assume these will break entirely when Core moves to 4.0.

 However, one worry I have with relying mainly on wp-jquery-update-test +
 jQuery Migrate is that it only tells you what breaks while you’re clicking
 around. Any JS that doesn’t run during testing just gets missed.

 Would it make sense to add a static scan that looks at a plugin/theme’s JS
 files and flags removed or deprecated jQuery APIs with file + line number,
 without executing the code? This seems a lot like what Plugin Check
 already does for PHP, but for jQuery compatibility.

 As a secondary thing (clearly non-blocking), the same scan could
 eventually point out places where jQuery usage could be optionally
 "modernized" to use vanilla js and browser APIs.

 Whatever the approach, I suspect this will cause more issues than a
 typical core update. So, I think this would need a solid pre-emptive
 outreach effort such that plugin devs even become aware of the changes and
 possible solutions ahead of time.

 This ticket probably isn’t the right place for that discussion, but where
 would it make sense to continue it? Plugin Check repo? Core Slack?

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


More information about the wp-trac mailing list