Deprecate wp-now in README and CLI output - #408
Merged
Conversation
This was referenced Jun 8, 2026
adamziel
marked this pull request as ready for review
June 8, 2026 11:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What it does
Displays a deprecation notice whenever
wp-nowruns and adds the same warning to the@wp-now/wp-nowREADME.Rationale
wp-nowis no longer maintained and should point users to@wp-playground/cli. This is the package-side follow-up to the Playground migration docs.Supersedes #378 with a smaller patch and without the placeholder code left in that PR.
Implementation
runCli()startup.npx @wp-playground/cli@latest start.Testing instructions
git diff --check.npx --yes prettier@2.6.2 --check packages/wp-now/README.md packages/wp-now/src/run-cli.ts.I did not run the full test suite because this checkout does not have dependencies installed.