getsentry/sentry-javascript (@sentry/node)
### [`v8.4.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#840)
[Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.3.0...8.4.0)
##### Important Changes
- **feat(nextjs): Trace pageloads in App Router ([#12157](https://togithub.com/getsentry/sentry-javascript/issues/12157))**
If you are using Next.js version `14.3.0-canary.64` or above, the Sentry Next.js SDK will now trace clientside pageloads
with React Server Components. This means, that client-side errors like
`Error: An error occurred in the Server Components render.`, which previously didn't give you much information on how
that error was caused, can now be traced back to a specific error in a server component.
- **feat(angular): Add Support for Angular 18 ([#12183](https://togithub.com/getsentry/sentry-javascript/issues/12183))**
This release guarantees support for Angular 18 with `@sentry/angular`.
##### Other Changes
- feat(deps): Bump [@opentelemetry/instrumentation-aws-lambda](https://togithub.com/opentelemetry/instrumentation-aws-lambda) from 0.41.0 to 0.41.1 ([#12078](https://togithub.com/getsentry/sentry-javascript/issues/12078))
- fix(metrics): Ensure string values are interpreted for metrics ([#12165](https://togithub.com/getsentry/sentry-javascript/issues/12165))
### [`v8.3.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#830)
[Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.2.1...8.3.0)
##### Important Changes
- **Better Node Framework Span Data**
This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.
- feat(node): Ensure connect spans have better data ([#12130](https://togithub.com/getsentry/sentry-javascript/issues/12130))
- feat(node): Ensure express spans have better data ([#12107](https://togithub.com/getsentry/sentry-javascript/issues/12107))
- feat(node): Ensure fastify spans have better data ([#12106](https://togithub.com/getsentry/sentry-javascript/issues/12106))
- feat(node): Ensure hapi spans have better data ([#12140](https://togithub.com/getsentry/sentry-javascript/issues/12140))
- feat(node): Ensure koa spans have better data ([#12108](https://togithub.com/getsentry/sentry-javascript/issues/12108))
- feat(node): Ensure Nest.js spans have better data ([#12139](https://togithub.com/getsentry/sentry-javascript/issues/12139))
- feat(deps): Bump [@opentelemetry/instrumentation-express](https://togithub.com/opentelemetry/instrumentation-express) from 0.38.0 to 0.39.0 ([#12079](https://togithub.com/getsentry/sentry-javascript/issues/12079))
- **feat(node): No-code init via `--import=@sentry/node/init` ([#11999](https://togithub.com/getsentry/sentry-javascript/issues/11999))**
When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:
```bash
SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@sentry/node/init app.mjs
```
When using CommonJS, you can do:
```bash
SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@sentry/node/init app.js
```
##### Other Changes
- chore: Align and update MIT license dates ([#12143](https://togithub.com/getsentry/sentry-javascript/issues/12143))
- chore: Resolve or postpone a random assortment of TODOs ([#11977](https://togithub.com/getsentry/sentry-javascript/issues/11977))
- doc(migration): Add entry for runWithAsyncContext ([#12153](https://togithub.com/getsentry/sentry-javascript/issues/12153))
- docs: Add migration docs to point out that default import does not work ([#12100](https://togithub.com/getsentry/sentry-javascript/issues/12100))
- docs(sveltekit): process.env.SENTRY_AUTH_TOKEN ([#12118](https://togithub.com/getsentry/sentry-javascript/issues/12118))
- feat(browser): Ensure `browserProfilingIntegration` is published to CDN ([#12158](https://togithub.com/getsentry/sentry-javascript/issues/12158))
- feat(google-cloud): Expose ESM build ([#12149](https://togithub.com/getsentry/sentry-javascript/issues/12149))
- feat(nextjs): Ignore Prisma critical dependency warnings ([#12144](https://togithub.com/getsentry/sentry-javascript/issues/12144))
- feat(node): Add app.free_memory info to events ([#12150](https://togithub.com/getsentry/sentry-javascript/issues/12150))
- feat(node): Do not create GraphQL resolver spans by default ([#12097](https://togithub.com/getsentry/sentry-javascript/issues/12097))
- feat(node): Use `node:` prefix for node built-ins ([#11895](https://togithub.com/getsentry/sentry-javascript/issues/11895))
- feat(replay): Use unwrapped `setTimeout` to avoid e.g. angular change detection ([#11924](https://togithub.com/getsentry/sentry-javascript/issues/11924))
- fix(core): Add dsn to span envelope header ([#12096](https://togithub.com/getsentry/sentry-javascript/issues/12096))
- fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked ([#12126](https://togithub.com/getsentry/sentry-javascript/issues/12126))
- fix(feedback): Set optionOverrides to be optional in TS definition ([#12125](https://togithub.com/getsentry/sentry-javascript/issues/12125))
- fix(nextjs): Don't put `undefined` values in props ([#12131](https://togithub.com/getsentry/sentry-javascript/issues/12131))
- fix(nextjs): Fix legacy configuration method detection for emitting warning ([#12136](https://togithub.com/getsentry/sentry-javascript/issues/12136))
- fix(node): Ensure fetch/http breadcrumbs are created correctly ([#12137](https://togithub.com/getsentry/sentry-javascript/issues/12137))
- fix(node): Update `@prisma/instrumentation` from 5.13.0 to 5.14.0 ([#12081](https://togithub.com/getsentry/sentry-javascript/issues/12081))
- ref(node): Add log for running in ESM/CommonJS mode ([#12134](https://togithub.com/getsentry/sentry-javascript/issues/12134))
- ref(node): Handle failing hook registration gracefully ([#12135](https://togithub.com/getsentry/sentry-javascript/issues/12135))
- ref(node): Only show instrumentation warning when tracing is enabled ([#12141](https://togithub.com/getsentry/sentry-javascript/issues/12141))
Work in this release contributed by [@pboling](https://togithub.com/pboling). Thank you for your contribution!
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
8.2.1->8.4.0Release Notes
getsentry/sentry-javascript (@sentry/node)
### [`v8.4.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#840) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.3.0...8.4.0) ##### Important Changes - **feat(nextjs): Trace pageloads in App Router ([#12157](https://togithub.com/getsentry/sentry-javascript/issues/12157))** If you are using Next.js version `14.3.0-canary.64` or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like `Error: An error occurred in the Server Components render.`, which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component. - **feat(angular): Add Support for Angular 18 ([#12183](https://togithub.com/getsentry/sentry-javascript/issues/12183))** This release guarantees support for Angular 18 with `@sentry/angular`. ##### Other Changes - feat(deps): Bump [@opentelemetry/instrumentation-aws-lambda](https://togithub.com/opentelemetry/instrumentation-aws-lambda) from 0.41.0 to 0.41.1 ([#12078](https://togithub.com/getsentry/sentry-javascript/issues/12078)) - fix(metrics): Ensure string values are interpreted for metrics ([#12165](https://togithub.com/getsentry/sentry-javascript/issues/12165)) ### [`v8.3.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#830) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.2.1...8.3.0) ##### Important Changes - **Better Node Framework Span Data** This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi. - feat(node): Ensure connect spans have better data ([#12130](https://togithub.com/getsentry/sentry-javascript/issues/12130)) - feat(node): Ensure express spans have better data ([#12107](https://togithub.com/getsentry/sentry-javascript/issues/12107)) - feat(node): Ensure fastify spans have better data ([#12106](https://togithub.com/getsentry/sentry-javascript/issues/12106)) - feat(node): Ensure hapi spans have better data ([#12140](https://togithub.com/getsentry/sentry-javascript/issues/12140)) - feat(node): Ensure koa spans have better data ([#12108](https://togithub.com/getsentry/sentry-javascript/issues/12108)) - feat(node): Ensure Nest.js spans have better data ([#12139](https://togithub.com/getsentry/sentry-javascript/issues/12139)) - feat(deps): Bump [@opentelemetry/instrumentation-express](https://togithub.com/opentelemetry/instrumentation-express) from 0.38.0 to 0.39.0 ([#12079](https://togithub.com/getsentry/sentry-javascript/issues/12079)) - **feat(node): No-code init via `--import=@sentry/node/init` ([#11999](https://togithub.com/getsentry/sentry-javascript/issues/11999))** When using Sentry in ESM mode, you can now use Sentry without manually calling init like this: ```bash SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@sentry/node/init app.mjs ``` When using CommonJS, you can do: ```bash SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@sentry/node/init app.js ``` ##### Other Changes - chore: Align and update MIT license dates ([#12143](https://togithub.com/getsentry/sentry-javascript/issues/12143)) - chore: Resolve or postpone a random assortment of TODOs ([#11977](https://togithub.com/getsentry/sentry-javascript/issues/11977)) - doc(migration): Add entry for runWithAsyncContext ([#12153](https://togithub.com/getsentry/sentry-javascript/issues/12153)) - docs: Add migration docs to point out that default import does not work ([#12100](https://togithub.com/getsentry/sentry-javascript/issues/12100)) - docs(sveltekit): process.env.SENTRY_AUTH_TOKEN ([#12118](https://togithub.com/getsentry/sentry-javascript/issues/12118)) - feat(browser): Ensure `browserProfilingIntegration` is published to CDN ([#12158](https://togithub.com/getsentry/sentry-javascript/issues/12158)) - feat(google-cloud): Expose ESM build ([#12149](https://togithub.com/getsentry/sentry-javascript/issues/12149)) - feat(nextjs): Ignore Prisma critical dependency warnings ([#12144](https://togithub.com/getsentry/sentry-javascript/issues/12144)) - feat(node): Add app.free_memory info to events ([#12150](https://togithub.com/getsentry/sentry-javascript/issues/12150)) - feat(node): Do not create GraphQL resolver spans by default ([#12097](https://togithub.com/getsentry/sentry-javascript/issues/12097)) - feat(node): Use `node:` prefix for node built-ins ([#11895](https://togithub.com/getsentry/sentry-javascript/issues/11895)) - feat(replay): Use unwrapped `setTimeout` to avoid e.g. angular change detection ([#11924](https://togithub.com/getsentry/sentry-javascript/issues/11924)) - fix(core): Add dsn to span envelope header ([#12096](https://togithub.com/getsentry/sentry-javascript/issues/12096)) - fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked ([#12126](https://togithub.com/getsentry/sentry-javascript/issues/12126)) - fix(feedback): Set optionOverrides to be optional in TS definition ([#12125](https://togithub.com/getsentry/sentry-javascript/issues/12125)) - fix(nextjs): Don't put `undefined` values in props ([#12131](https://togithub.com/getsentry/sentry-javascript/issues/12131)) - fix(nextjs): Fix legacy configuration method detection for emitting warning ([#12136](https://togithub.com/getsentry/sentry-javascript/issues/12136)) - fix(node): Ensure fetch/http breadcrumbs are created correctly ([#12137](https://togithub.com/getsentry/sentry-javascript/issues/12137)) - fix(node): Update `@prisma/instrumentation` from 5.13.0 to 5.14.0 ([#12081](https://togithub.com/getsentry/sentry-javascript/issues/12081)) - ref(node): Add log for running in ESM/CommonJS mode ([#12134](https://togithub.com/getsentry/sentry-javascript/issues/12134)) - ref(node): Handle failing hook registration gracefully ([#12135](https://togithub.com/getsentry/sentry-javascript/issues/12135)) - ref(node): Only show instrumentation warning when tracing is enabled ([#12141](https://togithub.com/getsentry/sentry-javascript/issues/12141)) Work in this release contributed by [@pboling](https://togithub.com/pboling). Thank you for your contribution!Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.