cloudflare workerEntryPoint not working

[taojoe]

Astro Info

Astro                    v5.14.5
Vite                     v6.4.0
Node                     v22.19.0
System                   Linux (x64)
Package Manager          npm
Output                   static
Adapter                  @astrojs/cloudflare (v12.6.10)
Integrations             @astrojs/mdx (v4.3.7)
                         @astrojs/sitemap (v3.6.0)

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

i followed the cloudflare integration guide, the workerEntryPoint part. it's not working.

the project is created by 'pnpm create cloudflare@latest --platform=pages' command.

i simply changed the src/worker.ts, it throws error, but nothing happend.

import type { SSRManifest } from 'astro';
import { App } from 'astro/app';
import { handle } from '@astrojs/cloudflare/handler'
import { DurableObject } from 'cloudflare:workers';

class MyDurableObject extends DurableObject<Env> {
  constructor(ctx: DurableObjectState, env: Env) {
    super(ctx, env)
  }
}

export function createExports(manifest: SSRManifest) {
  throw 'aaa';
  const app = new App(manifest);
  return {
    default: {
      async fetch(request, env, ctx) {
        return handle(manifest, app, request, env, ctx);
      },
      async queue(batch, _env) {
        let messages = JSON.stringify(batch.messages);
        console.log(`consumed from our queue: ${messages}`);
      }
    } satisfies ExportedHandler<Env>,
    MyDurableObject: MyDurableObject,
  }
}

the astro.config.mjs

// @ts-check

import mdx from '@astrojs/mdx';
import sitemap from '@astrojs/sitemap';
import { defineConfig } from 'astro/config';

import cloudflare from '@astrojs/cloudflare';

// https://astro.build/config
export default defineConfig({
  site: 'https://example.com',
  integrations: [mdx(), sitemap()],
  adapter: cloudflare({
    workerEntryPoint: {
      path: 'src/worker.ts',
      namedExports: ['MyDurableObject']
    },
    platformProxy: {
      enabled: true
    },

    imageService: "cloudflare"
  }),
});

What's the expected result?

the code in worker.ts should affect the pnpm dev command result, but it's not.

Link to Minimal Reproducible Example

https://github-wj8trigk.stackblitz.io

Participation

• I am willing to submit a pull request for this issue.

[ShawnTalbert]

OK weird. Take back my previous comment. I swear I saw missing declarations the other day, but I'm still interested in getting this working. If I find anything I'll report back.

[Yeehawlerz101]

I'm trying to deploy to Cloudflare right now and all I get is a [object Object] on the page. with doing nothing but configuring the deployment to be used on Cloudflare. :/ Here in a bit ill make the codebase public

[ShawnTalbert]

One notable thing is the example passes the request type through to the handle() function but they are not compatible types:

[matthewp]

@ShawnTalbert are you saying it's working now?

[ShawnTalbert]

I think the compile time error is an error, but if you accept casting blindly as any, @yuvadm was kind enough to provide an example repo that seems to work https://github.com/yuvadm/hello-astro-cf-workers for local development (I haven't tried deploying)

[matthewp]

Awesome! Can we consider this resolved in that case?

[ShawnTalbert]

Can we perhaps resolve the compile-time errors, like shown above? I would attempt it myself but I don't understand enough on how the two different request types are supposed to fit together.

i.e. the [type] difference between the request passed in to fetch() vs. the request expected by handle()

  default: {
      async fetch(request, env, ctx) {
        return handle(manifest, app, request, env, ctx);
      },

For reference, @yuvadm 's repo just took the sledgehammer approach and cast that request to type any (not typesafe):

[taojoe]

Can we perhaps resolve the compile-time errors, like shown above? I would attempt it myself but I don't understand enough on how the two different request types are supposed to fit together.

i.e. the [type] difference between the request passed in to fetch() vs. the request expected by handle()

default: {
async fetch(request, env, ctx) {
return handle(manifest, app, request, env, ctx);
},
For reference, @yuvadm 's repo just took the sledgehammer approach and cast that request to type any (not typesafe):

it's js, so there is no compile-time error. you can use the following code to make the error gone.

// @ts-expect-error

the line that throw error is the key point. because i should fail, you cannot see the error, and the code is working when pnpm dev

[yuvadm]

The type mismatch is tracked in #14038

You can workaround it with any or with ts-expect-error.

[alexanderniebuhr]

If I understand the OP correct, they talk about missing support during development. This feature is not support with astro dev yet, only with astro build for production workflows.

[taojoe]

If I understand the OP correct, they talk about missing support during development. This feature is not support with astro dev yet, only with astro build for production workflows.

so howto debug it locally? use the following script defined in package.json?
"preview": "astro build && wrangler dev",

[alexanderniebuhr]

That would be how you can check it locally for now yes. We are already working on bringing support for native astro dev.