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
Personal experience -- and Issues like #530 -- have shown that the way NPX deals with versions of installed binaries tends to surprise people:
npx pepr
npx pepr@version
npx pepr --version
Our answer (i.e. #530) is to instruct people to clear their machine's .npm cache (i.e. where npx installs things), but... maybe there's a better way?
It would be nice if there was a command that users could run (sort of like npx pepr update) that would install & relink a newer npx pepr-able version.
npx pepr update
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Personal experience -- and Issues like #530 -- have shown that the way NPX deals with versions of installed binaries tends to surprise people:
npx pepr
installs the most recent version availablenpx pepr@version
will install the requested (potentially newer) versionnpx pepr --version
(i.e no version tag) will show that npx still uses the older, origninally installed version.Our answer (i.e. #530) is to instruct people to clear their machine's .npm cache (i.e. where npx installs things), but... maybe there's a better way?
It would be nice if there was a command that users could run (sort of like
npx pepr update
) that would install & relink a newernpx pepr
-able version.The text was updated successfully, but these errors were encountered: