You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the package index has now been deprecated, we should start the discussion about whether we want a new discovery mechanism, and how that could work.
As the installation of packages has now been split off of the discovery mechanism, discovery can just as well be something entirely external to WP-CLI. It could be a full-blown package repository, but it could just as well be a specialized search engine.
That will only cover commands stored on GitHub. Ideally, we'd have a discovery mechanism for finding both stand-alone commands as well as commands included with plugins, no matter where the source files are stored.
For plugin commands, maybe the more appropriate place would be the WordPress.org plugin repo. It'd be cool to work out a way for plugin authors to easily incorporate that detail.
Although the package index will remain in place for backward compatibility reasons, it has been deprecated and will not be updated further. Please refer to #51 to read about its potential replacement.
Reacted by Jason A. Lefkowitz, Rasso Hilber and Dan Smart
There are several good suggestions above, but I've been unable to find (so far) why none of them were selected as appropriate. I've read the blog post and it seems that a packagist-like solution (Satis, wpackagist, etc) would solve both the central search location, and discoverability issues.
They do not address discovering cli packages that are bundled into plugins/themes; HOWEVER, one could argue in those situations the cli functionality is worthless without the plugin/theme it is bundled into.
IMO, I don't think plugin/theme cli discoverability should be a road-block for a centralized wp-cli package repository. I'm curious why none of the above solutions were ever implemented. Resources? Sponsor? Agreement?
I'm curious why none of the above solutions were ever implemented. Resources? Sponsor? Agreement?
Honestly, I think it's more a lack of momentum than anything else. It's a little bit of a solution in search of a problem — in reality, there aren't a ton of new packages created on a regular basis.
At this point, my preferred approach would be:
A page in the handbook that lists community packages maintained outside of the WP-CLI community.
Create more repos inside of this GitHub organization for common, general purpose commands.
Out of curiosity, how did you stumble upon this issue? What problem are you hoping to see addressed?
Out of curiosity, how did you stumble upon this issue? What problem are you hoping to see addressed?
I've been writing several wp-cli packages that I've been installing via git url. I'm now doing a presentation on writing custom wp-cli packages and noticed the handbookmentions the package index numerous times. But when I went to investigate how to submit a package to the index (linked from the package-index page), discovered it was deprecated. That led me down a rabbit hole that ultimately brought me here. 😄
there aren't a ton of new packages created on a regular basis.
I can't speak with confidence on whether there are, or there aren't, but I'll offer this counterpoint: one possibility is people follow the same path I did above, see that the index is deprecated, but then just stop. As an example of this, you can read the discussion surrounding the deprecation (and reversal) of Gitlab's public accessibility job template.
I've been writing several wp-cli packages that I've been installing via git url.
Are these packages meant for public consumption? Do you intend to maintain and support them?
I can't speak with confidence on whether there are, or there aren't, but I'll offer this counterpoint: one possibility is people follow the same path I did above, see that the index is deprecated, but then just stop.
Sure, makes sense. If there's interest at an upcoming Contributor Day, we could potentially discuss reviving a package index cc @wp-cli/maintainers
Wondering if there has been any progress/discussion on the possibility of getting the package manager for wp-cli working again? There are those of us who manage hundreds of wordpress websites and having a working, dependable package manager for wp cli would be very nice.
Activity
danielbachhuber commentedon Aug 23, 2017
What about GitHub repo search against the wp-cli-package label ?
schlessera commentedon Aug 24, 2017
That will only cover commands stored on GitHub. Ideally, we'd have a discovery mechanism for finding both stand-alone commands as well as commands included with plugins, no matter where the source files are stored.
danielbachhuber commentedon Aug 24, 2017
Oh, this is an interesting idea.
danielbachhuber commentedon Aug 25, 2017
For plugin commands, maybe the more appropriate place would be the WordPress.org plugin repo. It'd be cool to work out a way for plugin authors to easily incorporate that detail.
schlessera commentedon Aug 26, 2017
Yes, that might be feasible. Add a meta tag to the plugin file header, with something like:
Another approach would be to scan the plugin files for
WP_CLI::add_command()calls.miya0001 commentedon Aug 26, 2017
Oh, nice. 👍
schlessera commentedon Sep 20, 2017
Related: https://meta.trac.wordpress.org/ticket/3126
stefanos82 commentedon Mar 17, 2019
Maybe https://wpackagist.org/ is much more appropriate suggestion than vim-awesome.
szepeviktor commentedon May 26, 2020
How about Packagist?
https://packagist.org/packages/wp-cli/core-command?query=&type=wp-cli-package
redtux commentedon Oct 17, 2020
Hi, I just found out about the fact that
wp packageis deprecated by runningwp package browse.Would it be possible to include this information in the docs? https://developer.wordpress.org/cli/commands/package/
gilzow commentedon Jun 22, 2023
Was a replacement ever decided on? OR if not, can we resurface the discussion?
danielbachhuber commentedon Jun 27, 2023
It was not.
Sure, how would you suggest moving the discussion forward?
gilzow commentedon Jun 27, 2023
Thanks for the response, @danielbachhuber !
There are several good suggestions above, but I've been unable to find (so far) why none of them were selected as appropriate. I've read the blog post and it seems that a packagist-like solution (Satis, wpackagist, etc) would solve both the central search location, and discoverability issues.
They do not address discovering cli packages that are bundled into plugins/themes; HOWEVER, one could argue in those situations the cli functionality is worthless without the plugin/theme it is bundled into.
IMO, I don't think plugin/theme cli discoverability should be a road-block for a centralized wp-cli package repository. I'm curious why none of the above solutions were ever implemented. Resources? Sponsor? Agreement?
Edit: mispelling
danielbachhuber commentedon Jun 29, 2023
Honestly, I think it's more a lack of momentum than anything else. It's a little bit of a solution in search of a problem — in reality, there aren't a ton of new packages created on a regular basis.
At this point, my preferred approach would be:
Out of curiosity, how did you stumble upon this issue? What problem are you hoping to see addressed?
gilzow commentedon Jun 29, 2023
I've been writing several wp-cli packages that I've been installing via git url. I'm now doing a presentation on writing custom wp-cli packages and noticed the handbook mentions the package index numerous times. But when I went to investigate how to submit a package to the index (linked from the package-index page), discovered it was deprecated. That led me down a rabbit hole that ultimately brought me here. 😄
I can't speak with confidence on whether there are, or there aren't, but I'll offer this counterpoint: one possibility is people follow the same path I did above, see that the index is deprecated, but then just stop. As an example of this, you can read the discussion surrounding the deprecation (and reversal) of Gitlab's public accessibility job template.
danielbachhuber commentedon Jun 29, 2023
Thanks for the explanation 😊
Are these packages meant for public consumption? Do you intend to maintain and support them?
Sure, makes sense. If there's interest at an upcoming Contributor Day, we could potentially discuss reviving a package index cc @wp-cli/maintainers
swissspidy commentedon Jun 30, 2023
A curated list of some useful and popular commands sounds like a good start in the interim.
Highlighting plugins offering commands would also be nice. Maybe for now also in a curated way? There are around 600 in the repo: https://wpdirectory.net/search/01H46J87X60A5XC4KSJ1A42QVH
gilzow commentedon Jun 30, 2023
Possibly? I could certainly make them more generic to see if anyone else can use them. So far they've mostly been for my own use.
Yes, if I end up putting them in a public directory of some sorts, I'd definitely continue to maintain them.
schlessera commentedon Jul 12, 2023
@swissspidy I already created an "awesome list" in the past: https://github.com/schlessera/awesome-wp-cli
gilzow commentedon Jul 12, 2023
Is it ok if I promote/publicize that repository?
ahathaway commentedon May 13, 2026
Wondering if there has been any progress/discussion on the possibility of getting the package manager for wp-cli working again? There are those of us who manage hundreds of wordpress websites and having a working, dependable package manager for wp cli would be very nice.
What is everyone else doing instead?
swissspidy commentedon May 13, 2026
What is not working for you?
Discovering & installing WP-CLI packages from Packagist should be working as usual.