-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the nux package #46110
Remove the nux package #46110
Conversation
Size Change: -3.62 kB (0%) Total Size: 1.32 MB
ℹ️ View Unchanged
|
Won't doing this break backwards compatibility for |
It is a breaking change, the idea is that it's low impact and that the developers have been notified about it for a long time now. (At least 26 months) |
I don't have a real opinion for how to best deal with this. Just wanted to share the usage data here in the ticket:
|
Thanks for the links @fabiankaegy that's very helpful. I tried to go through the results to assess how valid are these results. I found that most of the results (like 99%) of the So for the second search query, a number of plugins mention Other than that, there seem to be only two plugins that may be using the wp.nux global:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes look good to me, and we have the plan to warn the possible user of the package, so it seems this change can be merged.
06d0e79
to
642bba9
Compare
👍 makes sense. Might be worth preparing the Core patch now. |
642bba9
to
5144808
Compare
I'll see if I can prepare the core patch |
Core patch available here WordPress/wordpress-develop#3775 |
Thanks @youknowriad 🙌 |
I have reached out to them :) Apologies for the delay here. I accidentally marked this as read and happened to stumble back on it. |
This reverts commit 9ea80f6.
This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php
This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php
This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php
* Revert "Remove the nux package (#46110)" This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php * Set peterwilsoncc as owner following revert. * Update rememo for nux to match other packages. * Update docs per precommit check. * Remove unused wp-nux CSS dependency. See * WordPress/wordpress-develop@8a6afdd * https://core.trac.wordpress.org/ticket/57827 * Use legacy fake timers for tests. * Update nux snapshot. The addition of the transforms of 0 pixels can be added safely as they have no effect. * Update starting version following e086b2b
This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php
This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php
* Revert "Remove the nux package (#46110)" This reverts commit 9ea80f6. # Conflicts: # lib/client-assets.php * Set peterwilsoncc as owner following revert. * Update docs per precommit check. * Remove unused wp-nux CSS dependency. See * WordPress/wordpress-develop@8a6afdd * https://core.trac.wordpress.org/ticket/57827 * Update rememo for nux to match other packages. * Use legacy fake timers for tests. * Update nux snapshot. The addition of the transforms of 0 pixels can be added safely as they have no effect. * Update starting version following e086b2b * Update starting version following 57ab3bd
What?
This package has been marked for removal for WordPress 6.2. There's no precedent on how to proceed with package removals. I've elected to remove it entirely to cleanup the repository properly. Let me know if you think there are any downsides to this. Also I think we have tools that rely on the presence of the folders so better to get rid of it to avoid performing builds... for this folder.
We'd need to follow-up on this on WordPress Core to actually remove the dependency and the script handle.