I'm using the Cloudflare Adapter but const { env } = Astro.locals.runtime;env is of type any

[rich escarp]

Hi @viral estuary. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

The behavior you’re seeing—where Astro.locals.runtime.env (or context.locals.runtime.env) is typed as any—is expected unless you explicitly type the runtime object using the types generated by wrangler types. The Astro documentation for the Cloudflare adapter explains that you can type the runtime object by extending your global types and using the Runtime type from @astrojs/cloudflare, parameterized with your Env type. However, you must ensure that the Env type is actually defined and imported from your generated worker-configuration.d.ts file.

Here’s what you should do:

1. Import the generated Env type
   The worker-configuration.d.ts file generated by wrangler types should export an Env type that matches your environment variables and bindings.

2. Reference the correct Env type in your env.d.ts
   Update your env.d.ts to import the Env type from the generated file and use it with the Runtime type.

For example:

// src/env.d.ts or your global types file

// Import the Env type from the generated file
import type { Env } from "../worker-configuration"; // Adjust the path if needed

type Runtime = import('@astrojs/cloudflare').Runtime<Env>;

declare namespace App {
  interface Locals extends Runtime {
    // ... your other locals
  }
}

This will ensure that Astro.locals.runtime.env is properly typed according to your Cloudflare environment variables and bindings, rather than being anyCloudflare runtime docs.

Note:
If you do not import and use the generated Env type, TypeScript will not know the shape of your environment and will default to any. Make sure the import path to worker-configuration.d.ts is correct and that the file is included in your tsconfig.json's include array if necessary.

If you follow these steps and still see any, double-check that:

• The worker-configuration.d.ts file actually exports an Env type.
• Your env.d.ts is being picked up by TypeScript (check your tsconfig.json).
• There are no conflicting types or module resolution issues.

For more details, see the Astro Cloudflare adapter documentation on typing.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@viral estuary Kapa.ai is still learning and improving, please let me know how I did by reacting below.

[viral estuary]

@rich escarp I looked inside worker-configuration.d.ts and I don't see anything exporting env

[rich escarp]

Let me check the knowledge base for you again. One moment! :books:

---

Thank you for checking inside your worker-configuration.d.ts. According to the official Astro documentation, after running wrangler types, you should get TypeScript types for your Cloudflare bindings, and you can use these to type the runtime object by extending your global types. The documentation provides this example:

type Runtime = import('@astrojs/cloudflare').Runtime<Env>;
declare namespace App {
  interface Locals extends Runtime {
    otherLocals: {
      test: string;
    };
  }
}

However, the documentation does not specify the exact structure of the generated worker-configuration.d.ts file, nor does it guarantee that an Env type will be exported by default. It only states that wrangler provides a types command to generate TypeScript types for the bindings, and you should refer to the Cloudflare documentation for more information. If your generated file does not export an Env type, the Astro documentation does not provide further guidance on how to proceed in this case.

Therefore, based on the knowledge sources, if worker-configuration.d.ts does not export an Env type, there is no official Astro guidance on how to resolve this, and you may need to consult the Cloudflare Wrangler documentation or community resources for further assistance Cloudflare runtime docs.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: