Bump the mvnpm group with 38 updates

[dependabot]

Bumps the mvnpm group with 38 updates:

Package	From	To
org.mvnpm.at.babel:runtime	7.23.6	7.23.8
org.mvnpm.at.restart:hooks	0.4.7	0.4.11
org.mvnpm.at.sentry-internal:tracing	7.63.0	7.91.0
org.mvnpm.at.sentry:browser	7.63.0	7.89.0
org.mvnpm.at.sentry:core	7.63.0	7.91.0
org.mvnpm.at.sentry:replay	7.63.0	7.91.0
org.mvnpm.at.sentry:types	7.63.0	7.91.0
org.mvnpm.at.sentry:utils	7.63.0	7.91.0
org.mvnpm.at.stdlib:array-float32	0.0.6	0.1.1
org.mvnpm.at.stdlib:array-uint16	0.0.6	0.1.1
org.mvnpm.at.stdlib:assert-has-uint16array-support	0.0.8	0.1.1
org.mvnpm.at.stdlib:assert-has-uint8array-support	0.0.8	0.1.1
org.mvnpm.at.stdlib:assert-is-buffer	0.0.8	0.1.1
org.mvnpm.at.stdlib:assert-is-object-like	0.0.8	0.1.1
org.mvnpm.at.stdlib:assert-tools-array-function	0.0.7	0.1.1
org.mvnpm.at.stdlib:cli-ctor	0.0.3	0.1.1
org.mvnpm.at.stdlib:constants-float64-high-word-sign-mask	0.0.1	0.1.1
org.mvnpm.at.stdlib:constants-float64-min-base2-exponent-subnormal	0.0.8	0.1.1
org.mvnpm.at.stdlib:math-base-assert-is-infinite	0.0.9	0.1.1
org.mvnpm.at.stdlib:number-float64-base-from-words	0.0.6	0.1.1
org.mvnpm.at.stdlib:number-float64-base-to-words	0.0.7	0.1.1
org.mvnpm.at.stdlib:process-cwd	0.0.8	0.1.1
org.mvnpm.at.stdlib:utils-get-prototype-of	0.0.7	0.1.1
org.mvnpm.at.stdlib:utils-global	0.0.7	0.1.1
org.mvnpm.at.stdlib:utils-noop	0.0.14	0.1.1
org.mvnpm.at.stdlib:utils-type-of	0.0.8	0.1.1
org.mvnpm.at.types:react	18.2.0	18.2.39
org.mvnpm:core-js	3.34.0	3.35.1
org.mvnpm:debug	2.6.9	4.3.4
org.mvnpm:js-cookie	3.0.1	3.0.5
org.mvnpm:js-tokens	4.0.0	8.0.2
org.mvnpm:ms	2.0.0	2.1.3
org.mvnpm:node-fetch	2.7.0	3.3.2
org.mvnpm:react-hotkeys-hook	4.4.1	4.4.4
org.mvnpm:react-is	16.13.1	18.2.0
org.mvnpm:regenerator-runtime	0.14.0	0.14.1
org.mvnpm:tr46	0.0.3	4.1.1
org.mvnpm:webidl-conversions	3.0.1	7.0.0

Updates org.mvnpm.at.babel:runtime from 7.23.6 to 7.23.8

Release notes

Sourced from org.mvnpm.at.babel:runtime's releases.

v7.23.8 (2024-01-08)

🐛 Bug Fix

• babel-preset-env
  • #16181 fix: preset-env throws exception for export * as x (@​liuxingbaoyu)
• babel-helpers, babel-plugin-proposal-decorators
  • #16201 fix: decorator binds getter/setter to ctx.access for public fields (@​liuxingbaoyu)
  • #16199 fix: Class decorator correctly passes return value (@​liuxingbaoyu)

↩️ Revert

• #16202 Revert "chore: Update artifact tools (#16184)" (@​JLHwung)

🔬 Output optimization

• babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-classes, babel-plugin-transform-function-name, babel-plugin-transform-parameters, babel-plugin-transform-react-jsx, babel-plugin-transform-runtime, babel-plugin-transform-spread, babel-plugin-transform-typescript, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #16194 Improve output of super() (@​liuxingbaoyu)

Committers: 3

• Huáng Jùnliàng (@​JLHwung)
• @​liuxingbaoyu
• coderaiser (@​coderaiser)

v7.23.7 (2023-12-29)

🐛 Bug Fix

• babel-traverse
  • #16191 fix: Crash when removing without Program (@​liuxingbaoyu)
• babel-helpers, babel-plugin-proposal-decorators
  • #16180 fix: Class decorator ctx.kind is wrong (@​liuxingbaoyu)
• babel-plugin-proposal-decorators
  • #16170 Fix decorator initProto usage in derived classes (@​JLHwung)
• babel-core
  • #16167 Avoid unpreventable unhandledRejection events (@​nicolo-ribaudo)

🏠 Internal

• babel-helper-create-class-features-plugin
  • #16186 chore: Update deps (@​liuxingbaoyu)
• babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • #16177 Merge decorators into class features (@​JLHwung)

Committers: 4

• Babel Bot (@​babel-bot)
• Huáng Jùnliàng (@​JLHwung)
• Nicolò Ribaudo (@​nicolo-ribaudo)
• @​liuxingbaoyu

Changelog

Sourced from org.mvnpm.at.babel:runtime's changelog.

v7.23.8 (2024-01-08)

🐛 Bug Fix

• babel-preset-env
  • #16181 fix: preset-env throws exception for export * as x (@​liuxingbaoyu)
• babel-helpers, babel-plugin-proposal-decorators
  • #16201 fix: decorator binds getter/setter to ctx.access for public fields (@​liuxingbaoyu)
  • #16199 fix: Class decorator correctly passes return value (@​liuxingbaoyu)

↩️ Revert

• #16202 Revert "chore: Update artifact tools (#16184)" (@​JLHwung)

🔬 Output optimization

• babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-classes, babel-plugin-transform-function-name, babel-plugin-transform-parameters, babel-plugin-transform-react-jsx, babel-plugin-transform-runtime, babel-plugin-transform-spread, babel-plugin-transform-typescript, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #16194 Improve output of super() (@​liuxingbaoyu)

v7.23.7 (2023-12-29)

🐛 Bug Fix

• babel-traverse
  • #16191 fix: Crash when removing without Program (@​liuxingbaoyu)
• babel-helpers, babel-plugin-proposal-decorators
  • #16180 fix: Class decorator ctx.kind is wrong (@​liuxingbaoyu)
• babel-plugin-proposal-decorators
  • #16170 Fix decorator initProto usage in derived classes (@​JLHwung)
• babel-core
  • #16167 Avoid unpreventable unhandledRejection events (@​nicolo-ribaudo)

🏠 Internal

• babel-helper-create-class-features-plugin
  • #16186 chore: Update deps (@​liuxingbaoyu)
• babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • #16177 Merge decorators into class features (@​JLHwung)

Commits

• 80c554f v7.23.8
• b4ce46a Use BABEL_BOT token to push types updates to babel/website
• 8666ee0 fix: preset-env throws exception for export * as x (#16181)
• 1e4777b fix: Husky automatic installation (#16206)
• d1088dc fix: @babel/core peerDependency in @babel/eslint-parser (#16175)
• 7840c54 Improve output of super() (#16194)
• 0427910 Decorator binds get/set to ctx.access for public fields (#16201)
• d7f8401 Revert "chore: Update artifact tools (#16184)" (#16202)
• 5c81253 fix: Class decorator correctly passes return value (#16199)
• bc503cc Add v7.23.7 to CHANGELOG.md [skip ci]
• Additional commits viewable in compare view

Updates org.mvnpm.at.restart:hooks from 0.4.7 to 0.4.11

Changelog

Sourced from org.mvnpm.at.restart:hooks's changelog.

0.4.11 (2023-07-17)

Bug Fixes

• useIsInitialRenderRef: clarify usage and fix ordering (437c417)

0.4.10 (2023-07-13)

Features

• useFocusManager: fire focused change immediately (#92) (7bb6d5a)

0.4.9 (2023-02-10)

Features

• add exports field in package.json (#88) (1c325b0)

0.4.8 (2023-01-25)

Bug Fixes

• useDebouncedCallback: fix return type (#85) (f2e26a0)

Commits

• 2464d25 Publish v0.4.11
• 437c417 fix(useIsInitialRenderRef): clarify usage and fix ordering
• 427cef8 Publish v0.4.10
• e84ef60 Bump all the things, and remove enzyme (#93)
• 7bb6d5a feat(useFocusManager): fire focused change immediately (#92)
• 5470145 Publish v0.4.9
• 1c325b0 feat: add exports field in package.json (#88)
• b6a3320 Publish v0.4.8
• f2e26a0 fix(useDebouncedCallback): fix return type (#85)
• See full diff in compare view

Updates org.mvnpm.at.sentry-internal:tracing from 7.63.0 to 7.91.0

Release notes

Sourced from org.mvnpm.at.sentry-internal:tracing's releases.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});

Other Changes

• feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry-internal:tracing's changelog.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
</tr></table>

... (truncated)

Commits

• 4c19ee3 release: 7.91.0
• cf412d9 fix(core): Rethrow caught promise rejections in startSpan, `startSpanManual...
• 948e7d3 feat(sveltekit): Add options to configure fetch instrumentation script for CS...
• 7f8eca7 feat: Add server runtime metrics aggregator (#9894)
• 5d16aae chore(biome): enable noUnusedImports rule (#9895)
• f819d81 feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)
• 9a2570b feat(replay): Send component names in replay breadcrumbs (#9947)
• f433a55 feat(tracing): Send component name on interaction spans (#9948)
• de6d41a Merge pull request #9949 from getsentry/feat/react-send-component-name-on-spans
• b6a7cef feat(core): Ensure startSpan & startSpanManual fork scope (#9955)
• Additional commits viewable in compare view

Updates org.mvnpm.at.sentry:browser from 7.63.0 to 7.89.0

Release notes

Sourced from org.mvnpm.at.sentry:browser's releases.

7.89.0

Important Changes

Deprecations

• feat(core): Deprecate configureScope (#9887)
• feat(core): Deprecate pushScope & popScope (#9890)

This release deprecates configureScope, pushScope, and popScope, which will be removed in the upcoming v8 major release.

Hapi Integration

• feat(node): Add Hapi Integration (#9539)

This release adds an integration for Hapi. It can be used as follows:

const Sentry = require('@sentry/node');
const Hapi = require('@hapi/hapi');
const init = async () => {
const server = Hapi.server({
// your server configuration ...
});
Sentry.init({
  dsn: '__DSN__',
  tracesSampleRate: 1.0,
  integrations: [
    new Sentry.Integrations.Hapi({ server }),
  ],
});
server.route({
// your route configuration ...
});
await server.start();

};

SvelteKit 2.0

• chore(sveltekit): Add SvelteKit 2.0 to peer dependencies (#9861)

This release adds support for SvelteKit 2.0 in the @sentry/sveltekit package. If you're upgrading from SvelteKit 1.x to 2.x and already use the Sentry SvelteKit SDK, no changes apart from upgrading to this (or a newer) version are necessary.

Other Changes

• feat(core): Add type & utility for function-based integrations (#9818)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry:browser's changelog.

7.89.0

Important Changes

Deprecations

• feat(core): Deprecate configureScope (#9887)
• feat(core): Deprecate pushScope & popScope (#9890)

This release deprecates configureScope, pushScope, and popScope, which will be removed in the upcoming v8 major release.

Hapi Integration

• feat(node): Add Hapi Integration (#9539)

This release adds an integration for Hapi. It can be used as follows:

const Sentry = require('@sentry/node');
const Hapi = require('@hapi/hapi');
const init = async () => {
const server = Hapi.server({
// your server configuration ...
});
Sentry.init({
dsn: 'DSN',
tracesSampleRate: 1.0,
integrations: [new Sentry.Integrations.Hapi({ server })],
});
server.route({
// your route configuration ...
});
await server.start();
};

SvelteKit 2.0

• chore(sveltekit): Add SvelteKit 2.0 to peer dependencies (#9861)

This release adds support for SvelteKit 2.0 in the @sentry/sveltekit package. If you're upgrading from SvelteKit 1.x to 2.x and already use the Sentry SvelteKit SDK, no changes apart from upgrading to this (or a newer) version are necessary.

Other Changes

... (truncated)

Commits

• 5e9a4f4 release: 7.89.0
• cf773fc fix(sveltekit): Avoid capturing 404 errors on client side (#9902)
• cef3621 ref(sveltekit): Improve SvelteKit 2.0 404 server error handling (#9901)
• 31c769c test(sveltekit): Add SvelteKit 2.0 E2E test app (#9873)
• a856913 fix(remix): Do not capture thrown redirect responses. (#9909)
• 6d32228 fix(sveltekit): Add conditional exports (#9872)
• 4e0c460 chore(sveltekit): Add SvelteKit 2.0 to peer dependencies (#9861)
• c9552a4 ref(node): Refactor LocalVariables integration to avoid setupOnce (#9897)
• 91a6b4e ref(browser): Refactor browser integrations to avoid setupOnce (#9898)
• 32f4bf0 ref(deno): Refactor deno integration to avoid setupOnce (#9900)
• Additional commits viewable in compare view

Updates org.mvnpm.at.sentry:core from 7.63.0 to 7.91.0

Release notes

Sourced from org.mvnpm.at.sentry:core's releases.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});

Other Changes

• feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry:core's changelog.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
</tr></table>

... (truncated)

Commits

• 4c19ee3 release: 7.91.0
• cf412d9 fix(core): Rethrow caught promise rejections in startSpan, `startSpanManual...
• 948e7d3 feat(sveltekit): Add options to configure fetch instrumentation script for CS...
• 7f8eca7 feat: Add server runtime metrics aggregator (#9894)
• 5d16aae chore(biome): enable noUnusedImports rule (#9895)
• f819d81 feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)
• 9a2570b feat(replay): Send component names in replay breadcrumbs (#9947)
• f433a55 feat(tracing): Send component name on interaction spans (#9948)
• de6d41a Merge pull request #9949 from getsentry/feat/react-send-component-name-on-spans
• b6a7cef feat(core): Ensure startSpan & startSpanManual fork scope (#9955)
• Additional commits viewable in compare view

Updates org.mvnpm.at.sentry:replay from 7.63.0 to 7.91.0

Release notes

Sourced from org.mvnpm.at.sentry:replay's releases.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});

Other Changes

• feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry:replay's changelog.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
</tr></table>

... (truncated)

Commits

• 4c19ee3 release: 7.91.0
• 17f490e Merge pull request #9965 from getsentry/prepare-release/7.91.0
• f08bec8 meta(changelog): Update changelog for 7.91.0
• cf412d9 fix(core): Rethrow caught promise rejections in startSpan, `startSpanManual...
• 948e7d3 feat(sveltekit): Add options to configure fetch instrumentation script for CS...
• f56219a build: Fix size limit (#9967)
• 7f8eca7 feat: Add server runtime metrics aggregator (#9894)
• 5d16aae chore(biome): enable noUnusedImports rule (#9895)
• f819d81 feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)
• 9a2570b feat(replay): Send component names in replay breadcrumbs (#9947)
• Additional commits viewable in compare view

Updates org.mvnpm.at.sentry:types from 7.63.0 to 7.91.0

Release notes

Sourced from org.mvnpm.at.sentry:types's releases.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});

Other Changes

• feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry:types's changelog.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
</tr></table>

... (truncated)

Commits

• 4c19ee3 release: 7.91.0
• cf412d9 fix(core): Rethrow caught promise rejections in startSpan, `startSpanManual...
• 948e7d3 feat(sveltekit): Add options to configure fetch instrumentation script for CS...
• 7f8eca7 feat: Add server runtime metrics aggregator (#9894)
• 5d16aae chore(biome): enable noUnusedImports rule (#9895)
• f819d81 feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)
• 9a2570b feat(replay): Send component names in replay breadcrumbs (#9947)
• f433a55 feat(tracing): Send component name on interaction spans (#9948)
• de6d41a Merge pull request #9949 from getsentry/feat/react-send-component-name-on-spans
• b6a7cef feat(core): Ensure startSpan & startSpanManual fork scope (#9955)
• Additional commits viewable in compare view

Updates org.mvnpm.at.sentry:utils from 7.63.0 to 7.91.0

Release notes

Sourced from org.mvnpm.at.sentry:utils's releases.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named valuable.ids
Sentry.metrics.set('valuable.ids', 2);

• feat(node): Rework ANR to use worker script via an integration (#9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@sentry/node';
Sentry.init({
dsn: 'https://[email protected]/1337',
integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});

Other Changes

• feat(breadcrumbs): Send component names on UI breadcrumbs (#9946)

... (truncated)

Changelog

Sourced from org.mvnpm.at.sentry:utils's changelog.

7.91.0

Important Changes

• feat: Add server runtime metrics aggregator (#9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with type: "a"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });
// Add 4.6 to a distribution named response_time with unit seconds
Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
...
Description has been truncated