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
It's possible to configure Solidarity Options to have the latest version of a package as the wanted version.
{ "rule": "cli", "binary": "gam", "error": "Try npm install -g gam-cli", "semver": "latest", "error": "please install with brew install watchman" },
npm install -g gam-cli
brew install watchman
Something like this.
The text was updated successfully, but these errors were encountered:
We don't currently have this to my knowledge, but it is an interesting idea!
This would require us to make a network call to a package manager to find the latest version, then check against semver of current.
A basic implementation might be easy, but I can see this scope creeping to every package manager ever.
@GantMan Got any input?
Sorry, something went wrong.
you can use
npm show package-name version
To check the version.
yes that would work - for npm.
with the current config object, I'm not sure there is a way for us to know this is a binary from npm.
No branches or pull requests
It's possible to configure Solidarity Options to have the latest version of a package as the wanted version.
{
"rule": "cli",
"binary": "gam",
"error": "Try
npm install -g gam-cli
","semver": "latest",
"error": "please install with
brew install watchman
"},
Something like this.
The text was updated successfully, but these errors were encountered: