Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update sentry-javascript monorepo to v7.72.0 #1801

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/browser (source) 7.69.0 -> 7.72.0 age adoption passing confidence
@sentry/integrations (source) 7.69.0 -> 7.72.0 age adoption passing confidence
@sentry/node (source) 7.69.0 -> 7.72.0 age adoption passing confidence
@sentry/react (source) 7.69.0 -> 7.72.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/browser)

v7.72.0

Compare Source

Important Changes
  • feat(node): App Not Responding with stack traces (#​9079)

This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.

To enable ANR detection, import and use the enableANRDetection function from the @sentry/node package before you run the rest of your application code.
Any event loop blocking before calling enableANRDetection will not be detected by the SDK.

Example (ESM):

import * as Sentry from "@​sentry/node";

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@​sentry/node");

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
  // Function that runs your app
  runApp();
});
Other Changes
  • fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#​9114)
  • fix(replay): Ensure replay_id is not captured when session is expired (#​9109)

v7.71.0

Compare Source

  • feat(bun): Instrument Bun.serve (#​9080)
  • fix(core): Ensure global event processors are always applied to event (#​9064)
  • fix(core): Run client eventProcessors before global ones (#​9032)
  • fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#​9100)
  • fix(react): Add actual error name to boundary error name (#​9065)
  • fix(react): Compare location against basename-prefixed route. (#​9076)
  • ref(browser): Refactor browser integrations to use processEvent (#​9022)

Work in this release contributed by @​jorrit. Thank you for your contribution!

v7.70.0

Compare Source

Important Changes

This release contains the beta version of @sentry/bun, our SDK for the Bun JavaScript runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.

  • feat(remix): Add Remix 2.x release support. (#​8940)

The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.

Other Changes
  • chore(node): Upgrade cookie to ^0.5.0 (#​9013)
  • feat(core): Introduce processEvent hook on Integration (#​9017)
  • feat(node): Improve non-error messages (#​9026)
  • feat(vercel-edge): Add Vercel Edge Runtime package (#​9041)
  • fix(remix): Use React.ComponentType instead of React.FC as withSentry's generic type. (#​9043)
  • fix(replay): Ensure replay events go through preprocessEvent hook (#​9034)
  • fix(replay): Fix typo in Replay types (#​9028)
  • fix(sveltekit): Adjust handleErrorWithSentry type (#​9054)
  • fix(utils): Try-catch monkeypatching to handle frozen objects/functions (#​9031)

Work in this release contributed by @​Dima-Dim, @​krist7599555 and @​lifeiscontent. Thank you for your contributions!

Special thanks for @​isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 75.58 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 31.49 KB
@​sentry/browser - Webpack (gzipped) 22.09 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 70.27 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 28.59 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 20.66 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 222.15 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 86.64 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 61.49 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 31.46 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 75.61 KB
@​sentry/react - Webpack (gzipped) 22.12 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 93.49 KB
@​sentry/nextjs Client - Webpack (gzipped) 51.07 KB

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) October 2, 2023 03:32
@vercel
Copy link

vercel bot commented Oct 2, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
59-node-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2023 3:32am

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

📦 Next.js Bundle Analysis for @app/web%0A%0AThis analysis was generated by the Next.js Bundle Analysis action. 🤖%0A%0A### ⚠️ Global Bundle Size Increased%0A %0APage | Size (compressed) | %0A|---|---|%0A| global | 53.35 KB (🟡 +930 B) |%0A%0A
%0ADetails%0A

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

%0A

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

%0A

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

%0A
%0A%0A### Four Pages Changed Size%0A %0AThe following pages changed size from the code in this PR compared to its base branch:%0A%0APage | Size (compressed) | First Load | %25 of Budget (350 KB) |%0A|---|---|---|---|%0A| / | 2.36 KB | 55.71 KB | 15.92%25 (+/- <0.01%25) |%0A| /404 | 319 B | 53.66 KB | 15.33%25 (+/- <0.01%25) |%0A| /_error | 864 B | 54.19 KB | 15.48%25 (🟢 -2.40%25) |%0A| /ssr | 335 B | 53.67 KB | 15.34%25 (+/- <0.01%25) |%0A%0A
%0ADetails%0A

Only the gzipped size is provided here based on an expert tip.

%0A

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.

%0A

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

%0A

The "Budget %25" 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%25 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%25 or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%25" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

%0A
%0A

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

Size Change: 0 B

Total Size: 1.95 kB

ℹ️ View Unchanged
Filename Size
./packages/ui/lib/Button/Button.stories.js 198 B
./packages/ui/lib/Button/index.js 260 B
./packages/ui/lib/Footer/Footer.stories.js 138 B
./packages/ui/lib/Footer/index.js 730 B
./packages/ui/lib/Header/Header.stories.js 139 B
./packages/ui/lib/Header/index.js 487 B

compressed-size-action

@renovate renovate bot merged commit 799345e into main Oct 2, 2023
6 of 8 checks passed
@renovate renovate bot deleted the renovate/sentry-javascript-monorepo branch October 2, 2023 03:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants