Skip to content

Bump @sentry/nextjs from 7.99.0 to 8.27.0

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

Bumps @sentry/nextjs from 7.99.0 to 8.27.0.

Release notes

Sourced from @​sentry/nextjs's releases.

8.27.0

Important Changes

  • fix(nestjs): Exception filters in main app module are not being executed (#13278)

    With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

  • feat: Add options for passing nonces to feedback integration (#13347)
  • feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
  • feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
  • feat(feedback): Improve error message for 403 errors (#13441)
  • fix(deno): Don't rely on Deno.permissions.querySync (#13378)
  • fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

8.26.0

Important Changes

  • feat(node): Add fsInstrumentation (#13291)

    This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

    This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:

    Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});

    WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

Other Changes

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

8.27.0

Important Changes

  • fix(nestjs): Exception filters in main app module are not being executed (#13278)

    With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

  • feat: Add options for passing nonces to feedback integration (#13347)
  • feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
  • feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
  • feat(feedback): Improve error message for 403 errors (#13441)
  • fix(deno): Don't rely on Deno.permissions.querySync (#13378)
  • fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

8.26.0

Important Changes

  • feat(node): Add fsInstrumentation (#13291)

    This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

    This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:

    Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});

    WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

... (truncated)

Commits

Merge request reports