Skip to content

Bump @sentry/nextjs from 8.39.0 to 8.42.0

DependabotFichesTerritoriales requested to merge dependabot-npm_and_yarn-sentry-nextjs-8.42.0 into main

Bumps @sentry/nextjs from 8.39.0 to 8.42.0.

Release notes

Sourced from @​sentry/nextjs's releases.

8.42.0

Important Changes

Deprecations

  • feat: Warn about source-map generation (#14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
import * as Sentry from '@sentry/nuxt';
Sentry.init({
// ...
integrations: [
Sentry.vueIntegration({
tracingOptions: {
trackComponents: true,
},
}),
],
});

Other Changes

  • feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
  • feat(nuxt): Expose vueIntegration (#14526)
  • fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

8.42.0

Important Changes

Deprecations

  • feat: Warn about source-map generation (#14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
import * as Sentry from '@sentry/nuxt';
Sentry.init({
// ...
integrations: [
Sentry.vueIntegration({
tracingOptions: {
trackComponents: true,
},
}),
],
});

Other Changes

  • feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
  • feat(nuxt): Expose vueIntegration (#14526)
  • fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Commits

Merge request reports