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
When the a version tag is specified in bun install Bun should do a network call to pull down the latest version with that tag.
bun install pkg@latest - installs version x
pkg publishes version x + 1
bun install pkg@latest re-installs x - no network call
npm allows arbitrary version tag names, though latest and next are common. If a version tag is specified in the install command Bun should always re-check the registry
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Follow up: even -f doesn't seem to refresh the registry cache.
Shortly after publishing a new version of zod@canary:
$ npm add zod@canary
up to date, audited 3 packages in 165ms
1 package is looking for funding
run `npm fund`for details
found 0 vulnerabilities
$ (cd node_modules/zod && npm pkg get version)
"3.22.0-canary.20230305T082229"
$ yarn add zod@canary
yarn add v1.22.19
warning package.json: No license field
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning No license field
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 🔨 Building fresh packages...
success Saved lockfile.
warning No license field
success Saved 1 new dependency.
info Direct dependencies
└─ zod@3.22.0-canary.20230305T082229
info All dependencies
└─ zod@3.22.0-canary.20230305T082229
✨ Done in 0.14s.
$ (cd node_modules/zod && npm pkg get version)
"3.22.0-canary.20230305T082229"
$ bun add zod@canary
bun add v0.5.8 (c0a49e40)
installed zod@1.10.2-canary
1 packages installed [10.00ms]
$ (cd node_modules/zod && npm pkg get version)
"1.10.2-canary"
$ bun add -f zod@canary
bun add v0.5.8 (c0a49e40)
+ typescript@4.9.5
installed zod@1.10.2-canary
2 packages installed [30.00ms]
$ (cd node_modules/zod && npm pkg get version)
"1.10.2-canary"
What version of Bun is running?
0.3.0
What platform is your computer?
Darwin 22.1.0 arm64 arm
What steps can reproduce the bug?
When the a version tag is specified in
bun install
Bun should do a network call to pull down the latest version with that tag.bun install pkg@latest
- installs versionx
pkg
publishes versionx + 1
bun install pkg@latest
re-installsx
- no network callnpm allows arbitrary version tag names, though
latest
andnext
are common. If a version tag is specified in the install command Bun should always re-check the registryWhat is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: