@bugsnag/js. We’re deprecating the old
bugsnag-js packages on npm and they will now only receive critical bug fixes.
This release of Bugsnag allows authors of JS applications — whether they are running on the client, server, or universally across both – to use the
@bugsnag/js module in exactly the same way on each platform. The package will automatically load the correct internals based on whether it is running in Node.js or being bundled into a client-side application.
We care about the performance of your applications, and therefore client bundle size, so it’s important to note that only browser relevant code is included when you import
@bugsnag/js with Webpack/Browserify, or load it from the CDN.
Bugsnag Node users will appreciate the greatly modernized interface and superior user experience with the new library. The original Bugsnag Node library will no longer be updated, but it will still be available for users who put off upgrading. Upgrading to the new library will require the same custom configurations done when you initially setup Bugsnag Node, like setting up metadata in your error reports or notifying Bugsnag of handled errors.
If you’re new to Bugsnag, you can try out Universal JS support free for 14-days.