Skip to main content
Here’s how to open a helpful issue for a bug, a performance problem, or a feature request:
For general questions, join the Discord.

​
Reporting Issues

1

Upgrade Bun

Upgrade Bun to the latest version with bun upgrade. This might fix your problem without opening an issue.
terminal
bun upgrade
You can also try the latest canary release, which includes changes and bug fixes that haven’t reached a stable release yet.
terminal
bun upgrade --canary

# To revert to the stable release
bun upgrade --stable
If the issue persists after upgrading, continue to the next step.
2

Review Existing Issues

Check whether the issue has already been reported before opening a new one. It saves time for everyone and helps us focus on fixing things.If you find a related issue, add a 👍 reaction or comment with extra details instead of opening a new one.
3

Report the Issue

If no one has reported the issue, open a new one or suggest an improvement.Provide as much detail as possible, including:
  • A clear and concise title
  • A code example or steps to reproduce the issue
  • The version of Bun you are using (run bun --version)
  • A description of the issue (what you expected to happen and what actually happened)
  • The operating system and version you are using
    • For macOS and Linux: copy the output of uname -mprs
    • For Windows: copy the output of this command in the PowerShell console: "$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"
The Bun team will review the issue and get back to you as soon as possible.

​
Use bun feedback

bun feedback sends feedback, bug reports, and feature requests directly to the Bun team.
terminal
bun feedback "Love the new release!"
bun feedback report.txt details.log
echo "please document X" | bun feedback --email you@example.com
Pass feedback as text arguments, file paths, or piped input.