@sentry/tracing - npm Package Compare versions

Comparing version 7.116.0 to 7.117.0

package.json

		{
		"name": "@sentry/tracing",
		"version": "7.116.0",
		"version": "7.117.0",
		"description": "Sentry Performance Monitoring Package",
		@@ -33,10 +33,10 @@ "repository": "git://github.com/getsentry/sentry-javascript.git",
		"dependencies": {
		"@sentry-internal/tracing": "7.116.0"
		"@sentry-internal/tracing": "7.117.0"
		},
		"devDependencies": {
		"@sentry-internal/integration-shims": "7.116.0",
		"@sentry/browser": "7.116.0",
		"@sentry/core": "7.116.0",
		"@sentry/types": "7.116.0",
		"@sentry/utils": "7.116.0",
		"@sentry-internal/integration-shims": "7.117.0",
		"@sentry/browser": "7.117.0",
		"@sentry/core": "7.117.0",
		"@sentry/types": "7.117.0",
		"@sentry/utils": "7.117.0",
		"@types/express": "^4.17.14"
		@@ -43,0 +43,0 @@ },

README.md

		@@ -7,3 +7,5 @@ <p align="center">

		> ⚠️ Deprecation Notice: From SDK versions >= `7.47.0` onwards, the `@sentry/tracing` package is officially deprecated. This package will be removed in a future major release. More details can be found in the [migration docs](https://github.com/getsentry/sentry-javascript/blob/7.47.0/MIGRATION.md/#remove-requirement-for-sentrytracing-package-since-7460).
		> ⚠️ Deprecation Notice: From SDK versions >= `7.47.0` onwards, the `@sentry/tracing` package is officially
		> deprecated. This package will be removed in a future major release. More details can be found in the
		> [migration docs](https://github.com/getsentry/sentry-javascript/blob/7.47.0/MIGRATION.md/#remove-requirement-for-sentrytracing-package-since-7460).

		@@ -16,2 +18,8 @@ # Sentry Tracing Extensions

		## Package Discontinued

		This package was discontinued with version 8.0.0 of the Sentry JavaScript SDKs. Instead, exports from this package are
		exported directly from the main SDK packages like `@sentry/react` or `@sentry/node`. For more information have a look at
		the [Migration Guide](https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md#sentrytracing).

		## Links
		@@ -24,13 +32,13 @@

		This package contains extensions to the `@sentry/hub` to enable Sentry AM related functionality. It also provides integrations for Browser and Node that provide a good experience out of the box.
		This package contains extensions to the `@sentry/hub` to enable Sentry AM related functionality. It also provides
		integrations for Browser and Node that provide a good experience out of the box.

		## Migrating from @sentry/apm to @sentry/tracing

		The tracing integration for JavaScript SDKs has moved from
		[`@sentry/apm`](https://www.npmjs.com/package/@sentry/apm) to
		[`@sentry/tracing`](https://www.npmjs.com/package/@sentry/tracing). While the
		two packages are similar, some imports and APIs have changed slightly.
		The tracing integration for JavaScript SDKs has moved from [`@sentry/apm`](https://www.npmjs.com/package/@sentry/apm) to
		[`@sentry/tracing`](https://www.npmjs.com/package/@sentry/tracing). While the two packages are similar, some imports and
		APIs have changed slightly.

		The old package `@sentry/apm` is deprecated in favor of `@sentry/tracing`.
		Future support for `@sentry/apm` is limited to bug fixes only.
		The old package `@sentry/apm` is deprecated in favor of `@sentry/tracing`. Future support for `@sentry/apm` is limited
		to bug fixes only.

		@@ -41,4 +49,3 @@ ## Migrating from @sentry/apm to @sentry/tracing

		If you were using the Browser CDN bundle, switch from the old
		`bundle.apm.min.js` to the new tracing bundle:
		If you were using the Browser CDN bundle, switch from the old `bundle.apm.min.js` to the new tracing bundle:

		@@ -64,4 +71,4 @@ ```html

		If you were using automatic instrumentation, update the import statement and
		update `Sentry.init` to use the new `BrowserTracing` integration:
		If you were using automatic instrumentation, update the import statement and update `Sentry.init` to use the new
		`BrowserTracing` integration:

		@@ -81,16 +88,13 @@ ```diff

		If you were using the `beforeNavigate` option from the `Tracing` integration,
		the API in `BrowserTracing` has changed slightly. Instead of passing in a
		location and returning a string representing transaction name, `beforeNavigate`
		now accepts a transaction context and is expected to return a transaction
		context. You can now add extra tags or change the `op` based on different
		parameters. If you want to access the location like before, you can get it from
		If you were using the `beforeNavigate` option from the `Tracing` integration, the API in `BrowserTracing` has changed
		slightly. Instead of passing in a location and returning a string representing transaction name, `beforeNavigate` now
		accepts a transaction context and is expected to return a transaction context. You can now add extra tags or change the
		`op` based on different parameters. If you want to access the location like before, you can get it from
		`window.location`.

		For example, if you had a function like so that computed a custom transaction
		name:
		For example, if you had a function like so that computed a custom transaction name:

		```javascript
		import * as Sentry from "@sentry/browser";
		import { Integrations } from "@sentry/apm";
		import * as Sentry from '@sentry/browser';
		import { Integrations } from '@sentry/apm';

		@@ -111,4 +115,4 @@ Sentry.init({
		```javascript
		import * as Sentry from "@sentry/browser";
		import { Integrations } from "@sentry/tracing";
		import * as Sentry from '@sentry/browser';
		import { Integrations } from '@sentry/tracing';

		@@ -157,4 +161,4 @@ Sentry.init({

		If you were using the Express integration for automatic instrumentation, the
		only necessary change is to update the import statement:
		If you were using the Express integration for automatic instrumentation, the only necessary change is to update the
		import statement:

		@@ -161,0 +165,0 @@ ```diff

@sentry/tracing - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Dependency changes