bugsnag-js
bugsnag-js copied to clipboard
Updated Next.js to v13
Update Next.JS app to v13 Tested all scenarios which should work in local environment, all worked fine.
Changeset
Dependencies are updated to the current version
Testing
Test scenarios are included in Next.JS example readme
@bugsnag/browser bundle size diff
| Minified | Minfied + Gzipped | |
|---|---|---|
| Before | 44.21 kB |
13.51 kB |
| After | 44.21 kB |
13.51 kB |
| ± | No change | No change |
code coverage diff
<temporarily disabled>
Generated by :no_entry_sign: dangerJS against 7130f7ae052705586501018c945496c7a077c196
I've tried all scenarios with the update, and noticed some unexpected behaviour. The README says we expect API scenario 2 and Client scenario 1 to fail, but I saw Client 1 works and API 2 works. However, I was unable to get anything for API scenario 1.
I think it might be worth quickly checking all scenarios again with Next.js v13.5.4, and making sure the behaviour you see matches up with what we say in the README. Is this a direct result of changing the version of Next, or do you see the same behaviour in the old example app?