@bugsnag/cli
Advanced tools
Simplify the process of creating releases on the BugSnag dashboard and uploading files to improve the stacktraces in your errors with our command line tool.
The binaries are available on our GitHub releases page for macOS, Linux and Windows.
To install or upgrade to the latest binary for your architecture, you can also run the following cURL or Wget commands:
curl -o- https://raw.githubusercontent.com/bugsnag/bugsnag-cli/main/install.sh | bash
wget -qO- https://raw.githubusercontent.com/bugsnag/bugsnag-cli/main/install.sh | bash
The script downloads the appropriate binary and attempts to install it to ~/.local/bugsnag.
To install or upgrade the BugSnag CLI via npm, you can run the following command:
npm install @bugsnag/cli
This tool is currently being developed. It currently supports the following commands:
Allows you to create a build within BugSnag to enrich releases shown in the BugSnag dashboard.
$ bugsnag-cli create-build --api-key=YOUR_API_KEY --app-version=YOUR_APP_VERSION
See the create-build command reference for full usage information.
For apps that use the NDK, this command extracts symbols from .so files and uploads them along with version information.
$ bugsnag-cli upload android-ndk \
app/build/intermediates/merged_native_libs/release/out/lib/arm64-v8a/libMyApp.so
See the upload android-ndk command reference for full usage information.
If you are using ProGuard, DexGuard, or R8 to minify and optimize your app, this command uploads the mapping file along with version information from your project directory:
$ bugsnag-cli upload android-proguard app/build/outputs/proguard/release/mapping.txt
See the upload android-proguard command reference for full usage information.
If you distribute your app as an Android App Bundle (AAB), they contain all required files and so can be uploaded in a single command:
$ bugsnag-cli upload android-aab app/build/outputs/bundle/release/app-release.aab
See the upload android-aab command reference for full usage information.
To get unminified stack traces for JavaScript code in your React Native app built for Android, source maps must be generated and can be uploaded to BugSnag using the following command from the root of your project:
$ bugsnag-cli upload react-native-android
See the upload react-native-android command reference for full usage information.
To get unminified stack traces for JavaScript code in your React Native app built for iOS, source maps must be generated and uploaded to BugSnag.
$ bugsnag-cli upload react-native-ios
See the upload react-native-ios command reference for full usage information.
To get unminified stack traces for JavaScript code on the web, source maps must be generated and uploaded to BugSnag.
$ bugsnag-cli upload js
See the upload js command reference for full usage information.
If you are stripping debug symbols from your Dart code when building your Flutter apps, you will need to upload symbol files in order to see full stacktraces using the following command:
$ bugsnag-cli upload dart --api-key=YOUR_API_KEY app-debug-info/
Upload dSYM files generated from a Build in Xcode to allow BugSnag to show human-friendly function names, file paths, and line numbers in your iOS, macOS, and tvOS stacktraces.
$ bugsnag-cli upload xcode-build
Upload dSYM files generated from an Archive in Xcode to allow BugSnag to show human-friendly function names, file paths, and line numbers in your iOS, macOS, and tvOS stacktraces.
$ bugsnag-cli upload xcode-archive
The unity-android command uploads the IL2CPP symbols from the .symbols.zip file produced by the Unity build (see Unity documentation for more information) to the NDK symbol API.
$ bugsnag-cli upload unity-android /path/to/build/directory
If you are using BugSnag On-premise, you should use the --build-api-root-url and --upload-api-root-url options to set the URL of your build and upload servers, for example:
bugsnag-cli upload \
--upload-api-root-url https://bugsnag.my-company.com/
# ... other options
Most updates to this repo will be made by Bugsnag employees. We are unable to accommodate significant external PRs such as features additions or any large refactoring, however minor fixes are welcome. See contributing for more information.
This package is free software released under the MIT License. See license for details.
FAQs
BugSnag CLI
The npm package @bugsnag/cli receives a total of 2,344 weekly downloads. As such, @bugsnag/cli popularity was classified as popular.
We found that @bugsnag/cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.