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
Astro v5.2.1
Node v22.13.1
System Windows (x64)
Package Manager unknown
Output static
Adapter none
Integrations none
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
"preferred-pm" 4.1.0 is required to support new "bun.lock" file (text based). However, it looks like @astrojs/upgrade is still using 4.0.0. Could this be updated to 4.1.0 to allow for bun 1.2 to work correctly (when using new bun.lock file) with @astrojs/upgrade? Currently, it reverts back to npm since 4.0.0 only looks for the bun.lockb file.
What needs to happen to get this new version published to npm so that is it usable...or will this eventually happen on it own through some sort of automated process?
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
"preferred-pm" 4.1.0 is required to support new "bun.lock" file (text based). However, it looks like @astrojs/upgrade is still using 4.0.0. Could this be updated to 4.1.0 to allow for bun 1.2 to work correctly (when using new bun.lock file) with @astrojs/upgrade? Currently, it reverts back to npm since 4.0.0 only looks for the bun.lockb file.
See #13065 for more info.
Thank you.
What's the expected result?
@astrojs/upgrade package.json file should use
"preferred-pm": "^4.1.0"
Since this is a CLI issue, there is no StackBlitz reproduction.
Link to Minimal Reproducible Example
http://localhost:4321
Participation
The text was updated successfully, but these errors were encountered: