@sentry-internal/browser-utils - npm Package Versions

published 8.10.0 • 5 months ago

Changelog

8.10.0

Important Changes

feat(remix): Migrate to opentelemetry-instrumentation-remix. (#12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes

feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#12512)
feat(feedback): Allow passing tags field to any feedback config param (#12197)
feat(feedback): Improve screenshot quality for retina displays (#12487)
feat(feedback): Screenshots don't resize after cropping (#12481)
feat(node) add max lineno and colno limits (#12514)
feat(profiling) add global profile context while profiler is running (#12394)
feat(react): Add React version to events (#12390)
feat(replay): Add url to replay hydration error breadcrumb type (#12521)
fix(core): Ensure standalone spans respect sampled flag (#12533)
fix(core): Use maxValueLength in extra error data integration (#12174)
fix(feedback): Fix scrolling after feedback submission (#12499)
fix(feedback): Send feedback rejects invalid responses (#12518)
fix(nextjs): Update @rollup/plugin-commonjs (#12527)
fix(node): Ensure status is correct for http server span errors (#12477)
fix(node): UnifygetDynamicSamplingContextFromSpan (#12522)
fix(profiling): continuous profile chunks should be in seconds (#12532)
fix(remix): Add nativeFetch support for accessing request headers (#12479)
fix(remix): Export no-op as captureRemixServerException from client SDK (#12497)
ref(node) refactor contextlines to use readline (#12221)

Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!

8.9.2

published 8.9.2 • 5 months ago

Changelog

8.9.2

fix(profiling): Update exports so types generate properly (#12469)

8.9.1

published 8.9.1 • 5 months ago

Changelog

8.9.1

Important changes

feat(solid): Add Solid SDK

This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for Solid Router and a custom ErrorBoundary. See the package README for how to use the SDK.

Other changes

feat(deps): bump @opentelemetry/instrumentation-express from 0.40.0 to 0.40.1 (#12438)
feat(deps): bump @opentelemetry/instrumentation-mongodb from 0.44.0 to 0.45.0 (#12439)
feat(deps): bump @opentelemetry/propagator-aws-xray from 1.24.1 to 1.25.0 (#12437)
feat(nextjs): Allow for suppressing warning about missing global error handler file (#12369)
feat(redis): Add cache logic for redis-4 (#12429)
feat(replay): Replay Web Vital Breadcrumbs (#12296)
fix: Fix types export order (#12404)
fix(astro): Ensure server-side exports work correctly (#12453)
fix(aws-serverless): Add op to Otel-generated lambda function root span (#12430)
fix(aws-serverless): Only auto-patch handler in CJS when loading awslambda-auto (#12392)
fix(aws-serverless): Only start root span in Sentry wrapper if Otel didn't wrap handler (#12407)
fix(browser): Fix INP span creation & transaction tagging (#12372)
fix(nextjs): correct types conditional export ordering (#12355)
fix(replay): Fix guard for exception event (#12441)
fix(vue): Handle span name assignment for nested routes in VueRouter (#12398)

Work in this release was contributed by @soch4n. Thank you for your contribution!

8.9.0

published 8.9.0 • 5 months ago

Changelog

8.9.0

This release failed to publish correctly, please use 8.9.1 instead.

8.8.0

published 8.8.0 • 5 months ago

Changelog

8.8.0

feat: Upgrade OTEL dependencies (#12388)

This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use import-in-the-middle v1.8.0. This should fix numerous issues with using OTEL instrumentation with ESM.

High level issues fixed with OTEL + ESM:

incompatibilities with using multiple loaders, commonly encountered while using tsx or similar libraries.
incompatibilities with libraries that use duplicate namespace exports like date-fns.
incompatibilities with libraries that use self-referencing namespace imports like openai.
incompatibilities with dynamic export patterns like exports with function calls.
ENOENT: no such file or directory bugs that libraries like discord.js surface.

If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.

deps: Bump Sentry bundler plugins to version 2.18.0 (#12381)
feat: Add thirdPartyErrorFilterIntegration (#12267)
feat(core): Filter out error events with exception values and no stacktraces, values, or types (#12387)
feat(core): Ignore additional common but inactionable errors (#12384)
feat(deps): Bump @opentelemetry/propagator-aws-xray from 1.3.1 to 1.24.1 (#12333)
feat(deps): Bump @sentry/cli from 2.31.2 to 2.32.1 (#12332)
feat(redis): Support mget command in caching functionality (#12380)
feat(vercel-edge): Export core integrations from Vercel edge SDK (#12308)
fix(browser): Fix idle span ending (#12306)
fix(browser): Fix parenthesis parsing logic for chromium (#12373)
fix(browser): Fix types export path for CJS (#12305)
fix(feedback): Override TriggerLabel Option (#12316)
fix(feedback): Wait for document to be ready before doing autoinject (#12294)
fix(nextjs): Fix memory leak (#12335)
fix(nextjs): Fix version detection and option insertion logic for clientTraceMetadata option (#12323)
fix(nextjs): Update argument name in log message about sentry property on Next.js config object (#12366)
fix(node): Do not manually finish / update root Hapi spans. (#12287)
fix(node): Fix virtual parent span ID handling & update create-next-app E2E test (#12368)
fix(node): Skip capturing Hapi Boom responses v8. (#12288)
fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true (#12360)
fix(replay): Avoid infinite loop of logs (#12309)
fix(replay): Ignore old events when manually starting replay (#12349)
ref(browser): Ensure idle span ending is consistent (#12310)
ref(profiling): unref timer (#12340)

Work in this release contributed by @dohooo, @mohd-akram, and @ykzts. Thank you for your contributions!

8.7.0

published 8.7.0 • 6 months ago

Changelog

8.7.0

Important Changes

feat(react): Add TanStack Router integration (#12095)

This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the @sentry/react SDK:

import * as Sentry from '@sentry/react';
import { createRouter } from '@tanstack/react-router';

const router = createRouter({
  // Your router options...
});

Sentry.init({
  dsn: '___PUBLIC_DSN___',
  integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
  tracesSampleRate: 1.0,
});

Other Changes

fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set (#12278)

8.6.0

published 8.6.0 • 6 months ago

Changelog

8.6.0

Important Changes

feat(metrics): Add timings method to metrics (#12226)

This introduces a new method, metrics.timing(), which can be used in two ways:
1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:
```
Sentry.metrics.timing('myMetric', 100);
```
1. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
```
const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);
```

feat(react): Add Sentry.reactErrorHandler (#12147)

This PR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

import * as Sentry from '@sentry/react';
import { hydrateRoot } from 'react-dom/client';

ReactDOM.hydrateRoot(
  document.getElementById('root'),
  <React.StrictMode>
    <App />
  </React.StrictMode>,
  {
    onUncaughtError: Sentry.reactErrorHandler(),
    onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
      // optional callback if users want custom config.
    }),
  },
);

For more details, take a look at the PR. Our documentation will be updated soon!

Other Changes

feat(sveltekit): Add request data to server-side events (#12254)
fix(core): Pass in cron monitor config correctly (#12248)
fix(nextjs): Don't capture suspense errors in server components (#12261)
fix(tracing): Ensure sent spans are limited to 1000 (#12252)
ref(core): Use versioned carrier on global object (#12206)

8.5.0

published 8.5.0 • 6 months ago

Changelog

8.5.0

Important Changes

feat(react): Add React 19 to peer deps (#12207)

This release adds support for React 19 in the @sentry/react SDK package.

feat(node): Add @sentry/node/preload hook (#12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

const express = require('express');
const Sentry = require('@sentry/node');

const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the PR Description of the new feature. Our docs will be updated soon with a new guide.

Other Changes

feat(browser): Do not include metrics in base CDN bundle (#12230)
feat(core): Add startNewTrace API (#12138)
feat(core): Allow to pass custom scope to captureFeedback() (#12216)
feat(core): Only allow SerializedSession in session envelope items (#11979)
feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#12133)
feat(node): Ensure manual OTEL setup works (#12214)
fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#12232)
fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#12233)
fix(browser): Improve browser extension error message check (#12146)
fix(browser): Remove optional chaining in INP code (#12196)
fix(nextjs): Don't report React postpone errors (#12194)
fix(nextjs): Use global scope for generic event filters (#12205)
fix(node): Add origin to redis span (#12201)
fix(node): Change import of @prisma/instrumentation to use default import (#12185)
fix(node): Only import inspector asynchronously (#12231)
fix(replay): Update matcher for hydration error detection to new React docs (#12209)
ref(profiling-node): Add warning when using non-LTS node (#12211)

8.4.0

published 8.4.0 • 6 months ago

Changelog

8.4.0

Important Changes

feat(nextjs): Trace pageloads in App Router (#12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like Error: An error occurred in the Server Components render., which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component.

feat(angular): Add Support for Angular 18 (#12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

feat(deps): Bump @opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.41.1 (#12078)
fix(metrics): Ensure string values are interpreted for metrics (#12165)

8.3.0

published 8.3.0 • 6 months ago

Changelog