[sentry/cloudflare] Sentry import breaks Env type

[shmuli9]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/cloudflare

SDK Version

9.13.0

Framework Version

React Router 7.5.1, Vite 6.3.0, Wrangler 4.12.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

// worker file: ./workers/app.ts

import { getLoadContext } from "load-context";
import { createRequestHandler } from "react-router";
import * as Sentry from "@sentry/cloudflare"; // <-- this line breaks the Env types

const requestHandler = createRequestHandler(
  () => import("virtual:react-router/server-build"),
  import.meta.env.MODE
);

export default {
  async fetch(request, env, ctx) {
    const url = new URL(request.url);
    if (url.pathname.startsWith("/r2")) {
      const key = url.pathname.replace(/^\/r2\//, "");
      const object = await env.BUCKET.get(key);
      if (!object) {
        return new Response("Not found", { status: 404 });
      }
      return new Response(object.body, {
        headers: { "Content-Type": "image/jpeg" },
      });
    }

    const loadContext = getLoadContext({
      request,
      context: { cloudflare: { env, ctx } },
    });
    return requestHandler(request, loadContext);
  },
} satisfies ExportedHandler<Env>;

Steps to Reproduce

1. installed @sentry/cloudflare v9.13.0
2. added the import to workers/app.ts
import * as Sentry from "@sentry/cloudflare"; // <-- this line breaks the Env types
3. my env types break in when i typecheck
4. commenting out the import fixes the type errors
   // import * as Sentry from "@sentry/cloudflare";

Expected Result

Types should not be corrupted by import Sentry

Actual Result

Broken:

Working (when import is commented out):

[lforst]

I cannot reproduce this in the exact way you're describing. I am getting a type error on env.BUCKET however that is unrelated to Sentry and simply happens when I run npm run cf-typegen or wrangler types.

Commenting and uncommenting the import doesn't change anything for me. Would you mind sharing a reproduction example we can pull?

[SlexAxton]

I'm also experiencing this behavior. It exists when using the newest wrangler setup. In newer setups the root typescript does not include @cloudflare/workers-types but instead includes ./worker-configuration.d.ts. This file is generated with wrangler types.

Then my tsconfig has something like this in it:

         "compilerOptions": {
		"lib": ["DOM", "DOM.Iterable", "ES2023"],
		"types": ["./worker-configuration.d.ts", "vite/client"],
		"baseUrl": ".",
		"rootDirs": [".", "./.react-router/types"],
	}

I don't even have @cloudflare/workers-types installed at all.

So when I add import * as Sentry from @sentry/cloudflaresuddenly theEnvdefinition in my whole app is empty, and refers to the transitive dependency on@cloudflare/workers-typesin@sentry/cloudflare`.

If I use the new wrangler features for import { env } from 'cloudflare:workers'; and then i cmd-click on env - i am bought to the @cloudflare/workers-types definition in the sentry dependency now.

But if I remove the import to sentry, this no longer occurs.

My wrangler version is 4.13.1

My app is based on this template: https://github.com/cloudflare/templates/blob/staging/react-router-postgres-ssr-template

So that's likely a good spot to test an integration.