-
Notifications
You must be signed in to change notification settings - Fork 277
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
[Playground CLI] wp-cli blueprint steps broken #2132
Comments
The version of WP-CLI used by Playground is outdated, it should better use the latest nightly. |
Why nightly and not stable? |
As Pascal noted, we'll need to revisit how we ship the WP CLI binary. Right now it’s always the same prebuilt phar file I’ve minified a year ago:
I've done that to save the transfer size. The official WP-CLI distribution was AFAIR around 20MB also served uncompressed. The one Playground uses is minified PHP code and pruned of some libraries which made it 7MB, or 1.5MB gzipped. At a very least, we should have auto updates like we have for core WordPress releases. Ideally, we’d also do minification – same as we do for the pre-bundled WordPress core releases. In a perfect world, we’d also tree shake the release. I don’t think there are any tools to do that automatically in PHP, but at least we could hardcode removing the same large libraries I did in that minified build. AFAIR I was able to remove something related to parsing PHP and some polyfills for the missing PHP extensions since the Playground ships them. |
The three blueprints in the gallery using various wp-cli commands still seem to work, though. Use wp-cli command to add posts
Use wp-cli to add a post with image
Demo of Twenty-Twenty-Five theme
|
I run the following command:
I have the following step:
I get the following error:
The text was updated successfully, but these errors were encountered: