unable to find new version of an package via npm backend when prefer_offline=true
#8652
Unanswered
chancez
asked this question in
Troubleshooting and bug reports
Replies: 1 comment 4 replies
-
|
As documented at prefer_offline this is applied to "fast" commands and was mainly introduced to avoid the (slow) version lookup use-case. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This might be the expected behavior, but I was trying to update
npm:@zed-industries/claude-agent-acpjust now and it was only finding verison0.21.0even though0.22.2is out.I kinda assumed that
upgradewould bypass the theprefer_offlinesince it kinda requires doing online stuff, no?Here's some out put from when I was debugging.
Then I commented out
prefer_offline = trueandlockfile = truein myconfig.tomland re-ranmise latest:Here's the output of
mise doctor(with my normal config, nothing commented out):Beta Was this translation helpful? Give feedback.
All reactions