We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
If people don't use the latest, they don't get the greatest.
Describe the solution you'd like
When a user runs this CLI on an old version, it should do a version check and let them know how to upgrade.
Could be npm i -g create-replicate or npx create-replicate@latest.
npm i -g create-replicate
npx create-replicate@latest
Describe alternatives you've considered
An alternative would be to display npx create-replicate@latest everywhere, so people are more likely to always be running latest.
But that's not ideal because it looks ugly, and people who aren't reading the docs will still likely run it wihout the @latest
@latest
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
If people don't use the latest, they don't get the greatest.
Describe the solution you'd like
When a user runs this CLI on an old version, it should do a version check and let them know how to upgrade.
Could be
npm i -g create-replicate
ornpx create-replicate@latest
.Describe alternatives you've considered
An alternative would be to display
npx create-replicate@latest
everywhere, so people are more likely to always be running latest.But that's not ideal because it looks ugly, and people who aren't reading the docs will still likely run it wihout the
@latest
The text was updated successfully, but these errors were encountered: