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
Starting from Bun v1.2.0, the default lock file format changed from bun.lockb (binary) to bun.lock (text-based). The current implementation in BunPackageInstallerLifecycleHook only checks for bun.lockb, which means projects using newer versions of Bun will fail the package installation step.
Regression
No response
Steps to reproduce
1. Create a new Aspire project with Bun support
2. Install Bun v1.2.0 or later
3. Run bun install in your project directory (this will create a bun.lock file)
4. Try to run the Aspire project
The application fails to start with the error:
: No bun.lockb file found in {WorkingDirectory}
Expected behavior
The package installer should:
Check for either bun.lock (new format) or bun.lockb (legacy format)
Continue execution if either file exists
Only throw an error if neither lock file is present
Screenshots
No response
IDE and version
VS 2022
IDE version
No response
Nuget packages
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item
The text was updated successfully, but these errors were encountered:
Describe the bug
Starting from Bun v1.2.0, the default lock file format changed from bun.lockb (binary) to bun.lock (text-based). The current implementation in BunPackageInstallerLifecycleHook only checks for bun.lockb, which means projects using newer versions of Bun will fail the package installation step.
Regression
No response
Steps to reproduce
Expected behavior
The package installer should:
Screenshots
No response
IDE and version
VS 2022
IDE version
No response
Nuget packages
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item
The text was updated successfully, but these errors were encountered: