[wp-trac] [WordPress Trac] #57643: Remove deprecated @wordpress/nux and replace with empty script and style

[WordPress Trac]

#57643: Remove deprecated @wordpress/nux and replace with empty script and style
-------------------------------------------------+-------------------------
 Reporter:  youknowriad                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.2
Component:  Editor                               |     Version:  5.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch gutenberg-merge needs-     |     Focuses:
  dev-note 2nd-opinion                           |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch gutenberg-merge needs-dev-note => has-patch
     gutenberg-merge needs-dev-note 2nd-opinion


Comment:

 Marking with 2nd opinion as discussion of how to proceed is happening in
 the [https://github.com/WordPress/wordpress-develop/pull/3775 PR 3775].

 @azaozz [https://github.com/WordPress/wordpress-
 develop/pull/3775#issuecomment-1405916513  summarized options here]
 (copying since the PR was linked after the comment):

 As far as I see it there are three options here:

 1. Remove `wp-nux` completely from everywhere, including scritp-loader.
 Scripts that still depend on `wp-nux` will not be loaded, so the plugins
 that add them will not work. As `wp-nux` has been deprecated and throwing
 errors for quite some time, it's very likely that these plugins haven't
 been working for years.
 2. Add stubs for the public methods in `wp_nux` and keep it in script-
 loader. Some features in plugins that use it as a dependency will not work
 (this has been the case for over two years anyway), but other things there
 (if any) may still work.
 3. Leave the JS for `wp-nux` in place, remove the CSS. This is pretty
 similar to number two as `wp-nux` has been throwing js errors for a long
 time, i.e. plugins that are using it as a dependency haven't been working
 properly anyway.

 Assuming that `wp-nux` have been causing errors and not working for over
 two years, perhaps option 1 seems most desirable? Then monitor bug reports
 during WP 6.2 beta and RC (that's nearly two months) and if there are many
 affected plugins and themes switch to option 3?

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