Closed renovate[bot] closed 1 year ago
vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| kami | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 6, 2023 8:37pm |
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/[page] |
52.31 KB |
250.3 KB | 71.52% (🟢 -0.02%) |
/_error |
5.96 KB |
203.96 KB | 58.27% (🟢 -0.01%) |
/friends |
57.49 KB |
255.48 KB | 73.00% (🟢 -0.02%) |
/notes/[id] |
74.97 KB |
272.97 KB | 77.99% (🟢 -0.01%) |
/posts/[category]/[slug] |
79.2 KB |
277.19 KB | 79.20% (🟢 -0.01%) |
/preview |
56.09 KB |
254.08 KB | 72.60% (🟢 -0.02%) |
/projects/[id] |
51.46 KB |
249.46 KB | 71.27% (🟢 -0.01%) |
/recently |
96.15 KB |
294.14 KB | 84.04% (🟢 -0.01%) |
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
This PR contains the following updates:
7.66.0->7.68.0Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
### [`v7.68.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7680) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/7.67.0...7.68.0) - feat(browser): Add `BroadcastChannel` and `SharedWorker` to TryCatch EventTargets ([#8943](https://togithub.com/getsentry/sentry-javascript/issues/8943)) - feat(core): Add `name` to `Span` ([#8949](https://togithub.com/getsentry/sentry-javascript/issues/8949)) - feat(core): Add `ServerRuntimeClient` ([#8930](https://togithub.com/getsentry/sentry-javascript/issues/8930)) - fix(node-experimental): Ensure `span.finish()` works as expected ([#8947](https://togithub.com/getsentry/sentry-javascript/issues/8947)) - fix(remix): Add new sourcemap-upload script files to prepack assets. ([#8948](https://togithub.com/getsentry/sentry-javascript/issues/8948)) - fix(publish): Publish downleveled TS3.8 types and fix types path ([#8954](https://togithub.com/getsentry/sentry-javascript/issues/8954)) ### [`v7.67.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7670) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/7.66.0...7.67.0) ##### Important Changes - **feat: Mark errors caught by the SDK as unhandled** - feat(browser): Mark errors caught from `TryCatch` integration as unhandled ([#8890](https://togithub.com/getsentry/sentry-javascript/issues/8890)) - feat(integrations): Mark errors caught from `HttpClient` and `CaptureConsole` integrations as unhandled ([#8891](https://togithub.com/getsentry/sentry-javascript/issues/8891)) - feat(nextjs): Mark errors caught from NextJS wrappers as unhandled ([#8893](https://togithub.com/getsentry/sentry-javascript/issues/8893)) - feat(react): Mark errors captured from ErrorBoundary as unhandled ([#8914](https://togithub.com/getsentry/sentry-javascript/issues/8914)) - feat(remix): Add debugid injection and map deletion to sourcemaps script ([#8814](https://togithub.com/getsentry/sentry-javascript/issues/8814)) - feat(remix): Mark errors caught from Remix instrumentation as unhandled ([#8894](https://togithub.com/getsentry/sentry-javascript/issues/8894)) - feat(serverless): Mark errors caught in Serverless handlers as unhandled ([#8907](https://togithub.com/getsentry/sentry-javascript/issues/8907)) - feat(vue): Mark errors caught by Vue wrappers as unhandled ([#8905](https://togithub.com/getsentry/sentry-javascript/issues/8905)) This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled. Previously, some of our instrumentations correctly set unhandled, while others set handled. Going forward, all errors caught automatically from our SDKs will be marked as unhandled. If you manually capture errors (e.g. by calling `Sentry.captureException`), your errors will continue to be reported as handled. This change might lead to a decrease in reported crash-free sessions and consequently in your release health score. If you have concerns about this, feel free to open an issue. ##### Other Changes - feat(node-experimental): Implement new performance APIs ([#8911](https://togithub.com/getsentry/sentry-javascript/issues/8911)) - feat(node-experimental): Sync OTEL context with Sentry AsyncContext ([#8797](https://togithub.com/getsentry/sentry-javascript/issues/8797)) - feat(replay): Allow to configure `maxReplayDuration` ([#8769](https://togithub.com/getsentry/sentry-javascript/issues/8769)) - fix(browser): Add replay and profiling options to `BrowserClientOptions` ([#8921](https://togithub.com/getsentry/sentry-javascript/issues/8921)) - fix(browser): Check for existence of instrumentation targets ([#8939](https://togithub.com/getsentry/sentry-javascript/issues/8939)) - fix(nextjs): Don't re-export default in route handlers ([#8924](https://togithub.com/getsentry/sentry-javascript/issues/8924)) - fix(node): Improve mysql integration ([#8923](https://togithub.com/getsentry/sentry-javascript/issues/8923)) - fix(remix): Guard against missing default export for server instrument ([#8909](https://togithub.com/getsentry/sentry-javascript/issues/8909)) - ref(browser): Deprecate top-level `wrap` function ([#8927](https://togithub.com/getsentry/sentry-javascript/issues/8927)) - ref(node-otel): Avoid exporting internals & refactor attribute adding ([#8920](https://togithub.com/getsentry/sentry-javascript/issues/8920)) Work in this release contributed by [@SorsOps](https://togithub.com/SorsOps). Thank you for your contribution!Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.