feat(nextjs): Add cloudflare `waitUntil` detection by logaretm · Pull Request #18336 · getsentry/sentry-javascript

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm · 2025-11-26T09:55:39Z

This is part of the work done for supporting Next.js on cloudflare workers in #14931, one of the issues is our flusher didn't take cloudflare into account and the events were being cut off due to early shutdowns by the worker environment.

We cannot use our core's flushIfServerless because it requires explicit cloudflareWaitUntil to be passed down to it.

Also The symbol we are grabbing here is specific to opennext and isn't something that is globally available on the worker environment. I had initially created #18330 because I mistook it for a worker environment API thing.

So this PR adds that detection to Next.js since it is relevant here and will use it if available, local tests show flushing is done correctly and events aren't being cut off.

JPeer264

To verify. This would only work with OpenNext, right?

JPeer264 · 2025-11-26T12:25:24Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


super-l: Since this is Opennext specific we could theoretically rename it to make it more obvious.

I though the comments would suffice, but you are right, it should be clearer with the naming. I will do that 👍

JPeer264 · 2025-11-26T12:25:56Z

+ * https://github.com/opennextjs/opennextjs-cloudflare/blob/b53a046bd5c30e94a42e36b67747cefbf7785f9a/packages/cloudflare/src/cli/templates/init.ts#L17
+ */
+function _getCloudflareContext(): MinimalCloudflareContext | undefined {
+ const cfContextSymbol = Symbol.for('__cloudflare-context__');


l: Do you think it would be possible to add this Symbol somehow in our Cloudflare SDK so we don't have to rely 100% on opennext?

I think our SDK can do something similar by putting the context on the global scope, so that we don't have to toss it around. But yes this is 100% opennext specific.
Will be very useful for SDKs that do use cloudflare SDK setup I suppose, but not necessarily the Next.js one at its current state with Opennext adapters.

chargome

LGTM!

I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions. This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official [OpenNext adapter](https://opennext.js.org/cloudflare). During [my investigation](getsentry/sentry-javascript#14931 (comment)) of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support `https.request` module [until recently](cloudflare/workerd#3820) which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues. So I wanted to document this information so users are able to find it more easily. My findings can be verified by checking out [this repo](https://github.com/logaretm/nextjs-cloudflare-demo) and try setting the `compat` date to anything below August 16th. You don't need a cloudflare account, just `wranger dev` should give you a similar environment locally to verify that. --- **Question for reviewers**: Should this live in special guides like I did here? or maybe add it to the manual setup? --------- Co-authored-by: Sarah Mischinger <sarah@codingwriter.com>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`10.27.0` -> `10.28.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/10.27.0/10.28.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/10.28.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/10.27.0/10.28.0?slim=true) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/react)</summary> ### [`v10.28.0`](https://github.com/getsentry/sentry-javascript/releases/tag/10.28.0) [Compare Source](getsentry/sentry-javascript@10.27.0...10.28.0) ##### Important Changes - **feat(core): Make `matcher` parameter optional in `makeMultiplexedTransport` ([#10798](getsentry/sentry-javascript#10798 The `matcher` parameter in `makeMultiplexedTransport` is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration. **Before:** ```javascript import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser'; const EXTRA_KEY = 'ROUTE_TO'; const transport = makeMultiplexedTransport(makeFetchTransport, args => { const event = args.getEvent(); if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) { return event.extra[EXTRA_KEY]; } return []; }); Sentry.init({ transport, // ... other options }); // Capture events with routing info Sentry.captureException(error, { extra: { [EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` **After:** ```javascript import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser'; // Just pass the transport generator - the default matcher handles the rest! Sentry.init({ transport: makeMultiplexedTransport(makeFetchTransport), // ... other options }); // Capture events with routing info using the exported constant Sentry.captureException(error, { extra: { [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [ { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' }, { dsn: 'https://key2@sentry.io/project2' }, ], }, }); ``` The default matcher looks for routing information in `event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]`. You can still provide a custom matcher function for advanced use cases. - **feat(nextjs): Support cacheComponents on turbopack ([#18304](getsentry/sentry-javascript#18304 This release adds support for `cacheComponents` on turbopack builds. We are working on adding support for this feature in webpack builds as well. ##### Other Changes - feat: Publish AWS Lambda Layer for Node 24 ([#18327](getsentry/sentry-javascript#18327)) - feat(browser): Expose langchain instrumentation ([#18342](getsentry/sentry-javascript#18342)) - feat(browser): Expose langgraph instrumentation ([#18345](getsentry/sentry-javascript#18345)) - feat(cloudflare): Allow specifying a custom fetch in Cloudflare transport options ([#18335](getsentry/sentry-javascript#18335)) - feat(core): Add `isolateTrace` option to `Sentry.withMonitor()` ([#18079](getsentry/sentry-javascript#18079)) - feat(deps): bump [@sentry/webpack-plugin](https://github.com/sentry/webpack-plugin) from 4.3.0 to 4.6.1 ([#18272](getsentry/sentry-javascript#18272)) - feat(nextjs): Add cloudflare `waitUntil` detection ([#18336](getsentry/sentry-javascript#18336)) - feat(node): Add LangChain v1 support ([#18306](getsentry/sentry-javascript#18306)) - feat(remix): Add parameterized transaction naming for routes ([#17951](getsentry/sentry-javascript#17951)) - fix(cloudflare): Keep http root span alive until streaming responses are consumed ([#18087](getsentry/sentry-javascript#18087)) - fix(cloudflare): Wait for async events to finish ([#18334](getsentry/sentry-javascript#18334)) - fix(core): `continueTrace` doesn't propagate given trace ID if active span exists ([#18328](getsentry/sentry-javascript#18328)) - fix(node-core): Handle custom scope in log messages without parameters ([#18322](getsentry/sentry-javascript#18322)) - fix(opentelemetry): Ensure Sentry spans don't leak when tracing is disabled ([#18337](getsentry/sentry-javascript#18337)) - fix(react-router): Use underscores in trace origin values ([#18351](getsentry/sentry-javascript#18351)) - chore(tanstackstart-react): Export custom inits from tanstackstart-react ([#18369](getsentry/sentry-javascript#18369)) - chore(tanstackstart-react)!: Remove empty placeholder implementations ([#18338](getsentry/sentry-javascript#18338)) <details> <summary>Internal Changes</summary> - chore: Allow URLs as issue ([#18372](getsentry/sentry-javascript#18372)) - chore(changelog): Add entry for [#18304](getsentry/sentry-javascript#18304) ([#18329](getsentry/sentry-javascript#18329)) - chore(ci): Add action to track all PRs as issues ([#18363](getsentry/sentry-javascript#18363)) - chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review ([#18352](getsentry/sentry-javascript#18352)) - ci: Add action to create issue on gitflow merge conflicts ([#18319](getsentry/sentry-javascript#18319)) - ci(deps): bump actions/checkout from 5 to 6 ([#18268](getsentry/sentry-javascript#18268)) - ci(deps): bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 ([#18361](getsentry/sentry-javascript#18361)) - test(cloudflare): Add typechecks for cloudflare-worker e2e test ([#18321](getsentry/sentry-javascript#18321)) </details> #### Bundle size 📦 | Path | Size | | ----------------------------------------------------------------------------------------------------- | --------- | | [@sentry/browser](https://github.com/sentry/browser) | 24.22 KB | | [@sentry/browser](https://github.com/sentry/browser) - with treeshaking flags | 22.76 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing) | 40.57 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Profiling) | 45.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) | 78.08 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay) - with treeshaking flags | 68.05 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay with Canvas) | 82.65 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Tracing, Replay, Feedback) | 94.61 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. Feedback) | 40.51 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. sendFeedback) | 28.8 KB | | [@sentry/browser](https://github.com/sentry/browser) (incl. FeedbackAsync) | 33.66 KB | | [@sentry/react](https://github.com/sentry/react) | 25.9 KB | | [@sentry/react](https://github.com/sentry/react) (incl. Tracing) | 42.72 KB | | [@sentry/vue](https://github.com/sentry/vue) | 28.56 KB | | [@sentry/vue](https://github.com/sentry/vue) (incl. Tracing) | 42.32 KB | | [@sentry/svelte](https://github.com/sentry/svelte) | 24.24 KB | | CDN Bundle | 26.57 KB | | CDN Bundle (incl. Tracing) | 41.22 KB | | CDN Bundle (incl. Tracing, Replay) | 76.9 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) | 82.23 KB | | CDN Bundle - uncompressed | 78.09 KB | | CDN Bundle (incl. Tracing) - uncompressed | 122.4 KB | | CDN Bundle (incl. Tracing, Replay) - uncompressed | 235.71 KB | | CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 248.17 KB | | [@sentry/nextjs](https://github.com/sentry/nextjs) (client) | 44.88 KB | | [@sentry/sveltekit](https://github.com/sentry/sveltekit) (client) | 40.92 KB | | [@sentry/node-core](https://github.com/sentry/node-core) | 50.06 KB | | [@sentry/node](https://github.com/sentry/node) | 155.7 KB | | [@sentry/node](https://github.com/sentry/node) - without tracing | 90.67 KB | | [@sentry/aws-serverless](https://github.com/sentry/aws-serverless) | 105.61 KB | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.foxden.network/foxCaves/foxCaves/pulls/12 Co-authored-by: Renovate <renovate@foxden.network> Co-committed-by: Renovate <renovate@foxden.network>

BREAKING CHANGE: Replace @sentry/browser and @sentry/cloudflare with unified @sentry/nextjs SDK Key Changes: - Install @sentry/nextjs@10.34.0 (replaces @sentry/browser and @sentry/cloudflare) - Add Next.js instrumentation for automatic Sentry initialization - src/instrumentation.ts: Main entry point with onRequestError hook - src/sentry.edge.config.ts: Edge runtime config (Cloudflare Workers) - src/sentry.server.config.ts: Node.js runtime config (local dev) - Update server.ts and client.ts to use @sentry/nextjs imports - Update all tests to mock @sentry/nextjs instead of individual SDKs Benefits: - ✅ Automatic error flushing on Cloudflare Workers (v10.28.0+) - No manual flush() calls needed - Detects OpenNext's waitUntil context automatically - See: getsentry/sentry-javascript#18336 - ✅ onRequestError hook captures Server Component/middleware errors - ✅ Unified SDK reduces bundle size and complexity - ✅ Official Next.js + Cloudflare Workers support Documentation: - Updated docs/SENTRY_SETUP.md with new architecture - Added references to v10.28.0 flushing fixes - Documented instrumentation.ts initialization flow Testing: - ✅ All 353 unit tests passing - ✅ Build successful (Next.js + Cloudflare) - ✅ Lint checks passing Resolves: getsentry/sentry-javascript#14931 Implements: getsentry/sentry-javascript#18336

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

logaretm added 2 commits November 26, 2025 11:21

feat: add cloudflare waitUntil util
85bb357

tests: added unit tests
c174908

logaretm requested review from JPeer264 and chargome November 26, 2025 09:55

logaretm mentioned this pull request Nov 26, 2025
Support Next.js on Cloudflare Workers (OpenNext) #14931
Closed
3 tasks

JPeer264 reviewed Nov 26, 2025
View reviewed changes

refactor: rename cf stuff to opennext
740cf85

JPeer264 approved these changes Nov 26, 2025
View reviewed changes

chargome approved these changes Nov 26, 2025
View reviewed changes

logaretm merged commit b306a35 into developNov 26, 2025
67 checks passed

logaretm deleted the awad/nextjs-cloudflare-flush branch November 26, 2025 16:51

logaretm mentioned this pull request Nov 27, 2025
docs(nextjs): added guide for Cloudlfare OpenNext support getsentry/sentry-docs#15652
Merged

hideokamoto mentioned this pull request Jan 25, 2026
Migrate Sentry from dual SDKs to unified @sentry/nextjs hideokamoto/hidetaka.dev.2023#157
Merged

coderabbitaiBot mentioned this pull request Feb 3, 2026
Cloudflare Workers環境でのサーバーサイドSentry統合を完全実装する hideokamoto/hidetaka.dev.2023#145
Closed

Uh oh!

Uh oh!

Conversation

logaretm commented Nov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

logaretmNov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chargome left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

logaretm commented Nov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

logaretmNov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chargome left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

logaretm commented Nov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

logaretmNov 26, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

logaretm commented Nov 26, 2025•
edited
Loading

logaretmNov 26, 2025•
edited
Loading

logaretm commented Nov 26, 2025•
edited
Loading

logaretmNov 26, 2025•
edited
Loading

logaretm commented Nov 26, 2025•
edited
Loading

logaretmNov 26, 2025•
edited
Loading

logaretm commented Nov 26, 2025•
edited
Loading

logaretmNov 26, 2025•
edited
Loading