Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@sentry-internal/browser-utils

Package Overview
Dependencies
Maintainers
9
Versions
63
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@sentry-internal/browser-utils - npm Package Compare versions

Comparing version 8.18.0 to 8.19.0

8

build/cjs/metrics/browserMetrics.js

@@ -242,3 +242,9 @@ Object.defineProperty(exports, '__esModule', { value: true });

const startTime = utils.msToSec(entry.startTime);
const duration = utils.msToSec(entry.duration);
const duration = utils.msToSec(
// Inexplicibly, Chrome sometimes emits a negative duration. We need to work around this.
// There is a SO post attempting to explain this, but it leaves one with open questions: https://stackoverflow.com/questions/23191918/peformance-getentries-and-negative-duration-display
// The way we clamp the value is probably not accurate, since we have observed this happen for things that may take a while to load, like for example the replay worker.
// TODO: Investigate why this happens and how to properly mitigate. For now, this is a workaround to prevent transactions being dropped due to negative duration spans.
Math.max(0, entry.duration),
);

@@ -245,0 +251,0 @@ if (op === 'navigation' && transactionStartTime && timeOrigin + startTime < transactionStartTime) {

@@ -240,3 +240,9 @@ import { getActiveSpan, startInactiveSpan, spanToJSON, setMeasurement, SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN } from '@sentry/core';

const startTime = msToSec(entry.startTime);
const duration = msToSec(entry.duration);
const duration = msToSec(
// Inexplicibly, Chrome sometimes emits a negative duration. We need to work around this.
// There is a SO post attempting to explain this, but it leaves one with open questions: https://stackoverflow.com/questions/23191918/peformance-getentries-and-negative-duration-display
// The way we clamp the value is probably not accurate, since we have observed this happen for things that may take a while to load, like for example the replay worker.
// TODO: Investigate why this happens and how to properly mitigate. For now, this is a workaround to prevent transactions being dropped due to negative duration spans.
Math.max(0, entry.duration),
);

@@ -243,0 +249,0 @@ if (op === 'navigation' && transactionStartTime && timeOrigin + startTime < transactionStartTime) {

8

package.json
{
"name": "@sentry-internal/browser-utils",
"version": "8.18.0",
"version": "8.19.0",
"description": "Browser Utilities for all Sentry JavaScript SDKs",

@@ -42,5 +42,5 @@ "repository": "git://github.com/getsentry/sentry-javascript.git",

"dependencies": {
"@sentry/core": "8.18.0",
"@sentry/types": "8.18.0",
"@sentry/utils": "8.18.0"
"@sentry/core": "8.19.0",
"@sentry/types": "8.19.0",
"@sentry/utils": "8.19.0"
},

@@ -47,0 +47,0 @@ "scripts": {

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc