You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in a team where all our development tools are pinned via Nix so we have the same reproducible environment.
We update the environment on a regular basis but with the fast development of pnpm we are often a bit behind so we get the notification message. It is not really a big issue as we can just ignore it until the next time we upgrade our dev tools but it is still a small annoyance and can it can be confusing for newcomers because the suggested upgrade command will not work.
Describe the solution you'd like
Having an additional configuration flags check-for-updates defaulting to true would be great.
Describe the drawbacks of your solution
Users could set this option to just ignore the new versions and never update pnpm which is not a good thing. It is however probable that users doing that on purpose never update even today anyway.
Describe alternatives you've considered
When update-notifier was used it was possible to disable the notification with the env variable NO_UPDATE_NOTIFIER. It looks like this is no more possible since 90487a3 and unless I miss something there is no alternative.
The text was updated successfully, but these errors were encountered:
The configuration option `update-notifier` allows users to disable the
update verification. This is interesting when pnpm is installed from
another package manager because the given instructions will not be
accurate. The `update-notifier` option exists in NPM so it can also
ease the migration to pnpm.
(https://docs.npmjs.com/cli/v8/using-npm/config#update-notifier).
close#4158.
Co-authored-by: Zoltan Kochan <z@kochan.io>
Describe the user story
I'm in a team where all our development tools are pinned via Nix so we have the same reproducible environment.
We update the environment on a regular basis but with the fast development of
pnpm
we are often a bit behind so we get the notification message. It is not really a big issue as we can just ignore it until the next time we upgrade our dev tools but it is still a small annoyance and can it can be confusing for newcomers because the suggested upgrade command will not work.Describe the solution you'd like
Having an additional configuration flags
check-for-updates
defaulting totrue
would be great.Describe the drawbacks of your solution
Users could set this option to just ignore the new versions and never update
pnpm
which is not a good thing. It is however probable that users doing that on purpose never update even today anyway.Describe alternatives you've considered
When
update-notifier
was used it was possible to disable the notification with the env variableNO_UPDATE_NOTIFIER
. It looks like this is no more possible since 90487a3 and unless I miss something there is no alternative.The text was updated successfully, but these errors were encountered: