@sentry/browser - npm Package Versions

published 9.11.0 • 3 weeks ago

Changelog

9.11.0

feat(browser): Add http.redirect_count attribute to browser.redirect span (#15943)
feat(core): Add consoleLoggingIntegration for logs (#15955)
feat(core): Don't truncate error messages (#15818)
feat(nextjs): Add release injection in Turbopack (#15958)
feat(nextjs): Record turbopack as tag (#15928)
feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#15859)
feat(react-router): Add sentryHandleRequest (#15787)
fix(node): Use module instead of require for CJS check (#15927)
fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#15930)
ref(browser): Temporarily add sentry.previous_trace span attribute (#15957)
ref(browser/core): Move all log flushing logic into clients (#15831)
ref(core): Improve URL parsing utilities (#15882)

9.10.1

published 9.10.1 • 4 weeks ago

Changelog

9.10.1

fix: Correct @sentry-internal/feedback docs to match the code (#15874)
deps: Bump bundler plugins to version 3.2.4 (#15909)

9.10.0

published 9.10.0 • 4 weeks ago

Changelog

9.10.0 Important Changes

feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)
feat(core): Add support for beforeSendLog (#15814)
feat(core): Add support for parameterizing logs (#15812)
fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.

Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});

const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;

trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });

// Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.

info(fmt(`Updated profile for user ${userId}`));
warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.

const { info, warn } = Sentry.logger;

info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });

To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.
```
const result = await Sentry.diagnoseSdkConnectivity();
```
The result will be an object with the following properties:
- "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
- "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
- undefined: The SDK is working as expected.
SDK Tracing Performance Improvements for Node SDKs
- feat: Stop using dropUndefinedKeys (#15796)
- feat(node): Only add span listeners for instrumentation when used (#15802)
- ref: Avoid dropUndefinedKeys for spanToJSON calls (#15792)
- ref: Avoid using SentryError for PromiseBuffer control flow (#15822)
- ref: Stop using dropUndefinedKeys in SpanExporter (#15794)
- ref(core): Avoid using SentryError for event processing control flow (#15823)
- ref(node): Avoid dropUndefinedKeys in Node SDK init (#15797)
- ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
We've been hard at work making performance improvements to the Sentry Node SDKs (@sentry/node, @sentry/aws-serverless, @sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes

chore(deps): Bump rrweb to 2.35.0 (#15825)
deps: Bump bundler plugins to 3.2.3 (#15829)
feat: Always truncate stored breadcrumb messages to 2kb (#15819)
feat(nextjs): Disable server webpack-handling for static builds (#15751)
fix(nuxt): Don't override Nuxt options if undefined (#15795)

9.9.0

published 9.9.0 • last month

Changelog

9.9.0 Important Changes

feat(nextjs): Support instrumentation-client.ts (#15705)

Next.js recently added a feature to support client-side (browser) instrumentation via the experimental.clientInstrumentationHook flag and the instrumentation-client.ts file.

To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles. It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

feat(browser): Add previous_trace span links (#15569)

The @sentry/browser SDK and SDKs based on @sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

Sentry.init({
  dsn: 'your-dsn-here'
  integrations: [
    Sentry.browserTracingIntegration({
      // Available settings:
      // - 'in-memory' (default): Stores previous trace information in memory
      // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
      // - 'off': Disable storing and sending previous trace information
      linkPreviousTrace: 'in-memory',
    }),
  ],
});

feat(browser): Add logger.X methods to browser SDK (#15763)

For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.
```
Sentry.init({
  dsn: 'your-dsn-here',
  _experiments: {
    enableLogs: true, // This is required to use the logging features
  },
});

Sentry.logger.info('This is a trace message', { userId: 123 });
// See PR for better documentation
```
Please note that the logs product is still in early access. See the link above for more information.

Other Changes

feat(browser): Attach host as part of error message to "Failed to fetch" errors (#15729)
feat(core): Add parseStringToURL method (#15768)
feat(core): Optimize dropUndefinedKeys (#15760)
feat(node): Add fastify shouldHandleError (#15771)
fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
perf(nestjs): Remove usage of addNonEnumerableProperty (#15766)
ref: Avoid some usage of dropUndefinedKeys() (#15757)
ref: Remove some usages of dropUndefinedKeys() (#15781)
ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)

9.8.0

published 9.8.0 • last month

Changelog

9.8.0

feat(node): Implement new continuous profiling API spec (#15635)
feat(profiling): Add platform to chunk envelope (#15758)
feat(react): Export captureReactException method (#15746)
fix(node): Check for res.end before passing to Proxy (#15776)
perf(core): Add short-circuits to eventFilters integration (#15752)
perf(node): Short circuit flushing on Vercel only for Vercel (#15734)

9.7.0

published 9.7.0 • last month

Changelog

9.7.0

feat(core): Add captureLog method (#15717)
feat(remix/cloudflare): Export sentryHandleError (#15726)
fix(node): Always flush on Vercel before Lambda freeze (#15602)
fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
fix(node): Use fatal level for unhandled rejections in strict mode (#15720)
fix(nuxt): Delete Nuxt server template injection (#15749)

9.7.0-alpha.0

published 9.7.0-alpha.0 • last month

9.6.1

published 9.6.1 • last month

Changelog