Maybe, though I should note that Assets is built primarily to serve HTML/JS/CSS, and while it can se

HHard@Work Maybe, though I should note that Assets is built primarily to serve HTML/JS/CSS,...

S

scruffy•2/18/25, 2:33 PM

good to know about the terms issue -- i was actually intending for the assets to be json rather than pngs, would that be any better in terms of being in keeping with the inteded use?

Sscruffy good to know about the terms issue -- i was actually intending for the assets to...

H

Hard@WorkOP•2/18/25, 2:35 PM

I wouldn't think so, though to be sure, I would probably talk with Support. Though note again that using R2/KV should definitely be simpler, and would avoid this terms issue, since it is allowed to serve any kind of assets, including images, json, etc, at any volume

S

scruffy•2/18/25, 2:36 PM

k, thanks for your help

HHard@Work Maybe, though I should note that Assets is built primarily to serve HTML/JS/CSS,...

S

scruffy•2/18/25, 3:41 PM

After some thought, seems that per-user HTML could fit my use case. With that in mind, would it be possible to use a single script as the user worker to enable static asset uploads to

example.my.worker.dev/users/:user-name/index.html

example.my.worker.dev/users/:user-name/index.html

? If so, do the API requests count against my account or the user? Apologies if the question seems bizarre, finding it a bit hard to get my head round things without poking code.

S

scruffy•2/18/25, 8:00 PM

If a Workers for Platforms "script" doesn't contain actually contain a user worker, i.e. it only holds user-specific static assets, does it still count towards the total count of user scripts?

W

Walshy•2/18/25, 8:05 PM

Yes, it is still a script for us

Sscruffy good to know about the terms issue -- i was actually intending for the assets to...

W

Walshy•2/18/25, 8:05 PM

json is fine

S

scruffy•2/18/25, 8:06 PM

cool, thanks

W

Walshy•2/18/25, 8:06 PM

A user Worker with JSON bindings may also be even easier

S

scruffy•2/18/25, 8:06 PM

not sure i follow

S

scruffy•2/18/25, 8:07 PM

(but sounds interesting)

W

Walshy•2/18/25, 8:08 PM

you could upload a user Worker that's literally just

export default {
  fetch(_, env) {
    // will return `{ "whatever": "data" }` as a Content-Type: application/json response
    return Response.json(env.JSON_DATA)
  }
}

export default {
  fetch(_, env) {
    // will return `{ "whatever": "data" }` as a Content-Type: application/json response
    return Response.json(env.JSON_DATA)
  }
}

export default {
  fetch(_, env) {
    // will return `{ "whatever": "data" }` as a Content-Type: application/json response
    return Response.json(env.JSON_DATA)
  }
}

export default {
  fetch(_, env) {
    // will return `{ "whatever": "data" }` as a Content-Type: application/json response
    return Response.json(env.JSON_DATA)
  }
}

And upload the Worker with

"bindings": [
  {
    "name": "JSON_DATA",
    "type": "json",
    "json": {
      "whatever": "data"
    }
  }
]

"bindings": [
  {
    "name": "JSON_DATA",
    "type": "json",
    "json": {
      "whatever": "data"
    }
  }
]

"bindings": [
  {
    "name": "JSON_DATA",
    "type": "json",
    "json": {
      "whatever": "data"
    }
  }
]

"bindings": [
  {
    "name": "JSON_DATA",
    "type": "json",
    "json": {
      "whatever": "data"
    }
  }
]

W

Walshy•2/18/25, 8:08 PM

Much easier than doing an asset upload flow

S

scruffy•2/18/25, 8:10 PM

that's cool, thanks for the tip!

D

darkpool•2/20/25, 9:20 PM

hi all probably a noob question but how do I exactly use WFP locally?

I see on first page of local development, it says

Support for Workers for Platforms with wrangler dev in local mode is experimental and may change in the future. Use the prerelease branch: wrangler@dispatch-namespaces-dev to try Workers for Platforms locally.

Support for Workers for Platforms with wrangler dev in local mode is experimental and may change in the future. Use the prerelease branch: wrangler@dispatch-namespaces-dev to try Workers for Platforms locally.

Support for Workers for Platforms with wrangler dev in local mode is experimental and may change in the future. Use the prerelease branch: wrangler@dispatch-namespaces-dev to try Workers for Platforms locally.

Support for Workers for Platforms with wrangler dev in local mode is experimental and may change in the future. Use the prerelease branch: wrangler@dispatch-namespaces-dev to try Workers for Platforms locally.

~~but im confused on how to actually enable it. Is there an experimental flag I have to use? do I need to download wrangler globally? or something else? Thanks!~~

EDIT: Im dumb. Just did:

        "wrangler": "dispatch-namespaces-dev"

        "wrangler": "dispatch-namespaces-dev"

However, now I got this error:

ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler dev path/to/script`) or the `main` config field.

ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler dev path/to/script`) or the `main` config field.

even though I have path specified in wrangler. I resolved by just adding the path to the dev script but seems like a regression.

EDIT 2: seems like experimental flag also ignores specified port for wrangler to listen to in wrangler.jsonc

D

darkpool•2/20/25, 10:47 PM

is this an error? I dont see any mention of

dispatch_namespace

dispatch_namespace

in https://developers.cloudflare.com/workers/wrangler/configuration/

Ddarkpool is this an error? I dont see any mention of `dispatch_namespace` in https://deve...

U

Unsmart•2/20/25, 10:50 PM

B

BD•2/20/25, 10:51 PM

Is anyone able to help me with a

request.cf.zoneName

request.cf.zoneName

issue? My website is hosted on CF Pages. I am using a CF Worker and want to limit the ability to make an api request to specific zoneName's. The issue I am running into is that

request.cf

request.cf

is always NULL. FWIW The code is below, but I have a feeling this might be a DNS or Routing issue. Any and all help would be appreciated.

    // Verify Cloudflare zone
    console.log(request.cf);
    console.log(allowedDomains);
    console.log(request.cf.zoneName);
    console.log(allowedDomains.includes(request.cf.zoneName));
    if (!request.cf || !allowedDomains.includes(request.cf.zoneName)) {
        console.log('[Security] Access denied: Invalid Cloudflare zone');
        return new Response(
            JSON.stringify({ error: 'Access denied' }),
            { status: 403, headers: { 'Content-Type': 'application/json' } }
        );
    }

    // Verify Cloudflare zone
    console.log(request.cf);
    console.log(allowedDomains);
    console.log(request.cf.zoneName);
    console.log(allowedDomains.includes(request.cf.zoneName));
    if (!request.cf || !allowedDomains.includes(request.cf.zoneName)) {
        console.log('[Security] Access denied: Invalid Cloudflare zone');
        return new Response(
            JSON.stringify({ error: 'Access denied' }),
            { status: 403, headers: { 'Content-Type': 'application/json' } }
        );
    }

    // Verify Cloudflare zone
    console.log(request.cf);
    console.log(allowedDomains);
    console.log(request.cf.zoneName);
    console.log(allowedDomains.includes(request.cf.zoneName));
    if (!request.cf || !allowedDomains.includes(request.cf.zoneName)) {
        console.log('[Security] Access denied: Invalid Cloudflare zone');
        return new Response(
            JSON.stringify({ error: 'Access denied' }),
            { status: 403, headers: { 'Content-Type': 'application/json' } }
        );
    }

    // Verify Cloudflare zone
    console.log(request.cf);
    console.log(allowedDomains);
    console.log(request.cf.zoneName);
    console.log(allowedDomains.includes(request.cf.zoneName));
    if (!request.cf || !allowedDomains.includes(request.cf.zoneName)) {
        console.log('[Security] Access denied: Invalid Cloudflare zone');
        return new Response(
            JSON.stringify({ error: 'Access denied' }),
            { status: 403, headers: { 'Content-Type': 'application/json' } }
        );
    }

UUnsmart Click to see attachment

D

darkpool•2/20/25, 10:52 PM

that's the config for the dispatch worker no? Im following the local setup guide and it says to add dispatch_namespace to customer-worker-1

Ddarkpool that's the config for the dispatch worker no? Im following the local setup guide...

U

Unsmart•2/20/25, 10:55 PM

Didnt see the initial message about the tutorial. The reason it wouldnt be defined in the wrangler docs is because its not an option in wrangler config its part of the dispatch namespaces dev

UUnsmart Didnt see the initial message about the tutorial. The reason it wouldnt be defin...

D

darkpool•2/20/25, 11:08 PM

So eve though i get - "Unexpected fields found in top-level field: "dispatch_namespace"" it's ok?

U

Unsmart•2/20/25, 11:09 PM

Yeah should be fine

UUnsmart Yeah should be fine

D

darkpool•2/20/25, 11:14 PM

Thank you for your help. Another problem is it seems my wrangler.jsonc is not being picked up? I can get arount by just specifying the path in the script but seems like the

dispatch_namespaces

dispatch_namespaces

config is not being picked up either?

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g.

wrangler dev path/to/script

wrangler dev path/to/script

) or the

main

main

config field.

W

Walshy•2/20/25, 11:53 PM

have you specified

main

main

?

W

Walshy•2/20/25, 11:54 PM

If you're using the

dispatch-namespaces-dev

dispatch-namespaces-dev

branch I'm not sure that supports wrangler.json by default yet..

W

Walshy•2/20/25, 11:55 PM

I don't like these branches for these reasons :/

W

Walshy•2/20/25, 11:55 PM

There should be a flag for it

D

darkpool•2/20/25, 11:56 PM

ok awesome going to try toml now and get back to you

W

Walshy•2/20/25, 11:56 PM

Looks like

--x-json-config

--x-json-config

but yeah, toml will work too

D

darkpool•2/20/25, 11:57 PM

one thing I'm a bit confused on how the version works. like just to confirm this is what wrangler should be in package.json? I honestly didn't know you could have a name for versioning haha

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

WWalshy Looks like `--x-json-config` but yeah, toml will work too

D

darkpool•2/21/25, 12:44 AM

Fixed previous issue with toml but now running into this ;/

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

EDIT: got it to work finally. I kept getting spammed "Failed to get worker definitions TypeError: fetch" but after restarting machine erorr went away which fixed the above error. I'm using turbo repo with 6 workers and I there is a lot of problems with port collisions. I was specifying inspector_ports but just restarting machine seems to work.

Cchristianklotz I followed [the guide](https://developers.cloudflare.com/cloudflare-for-platform...

D

darkpool•2/21/25, 12:45 AM

Hi @christianklotz did you figure this out?

I

Ian Schenck•2/21/25, 1:46 AM

Are service bindings inside a namespace, among services in that namespace, possible? I'm getting errors from the API saying the script doesn't exist.

IIan Schenck Are service bindings inside a namespace, among services in that namespace, possi...

P

Payello•2/21/25, 12:58 PM

Service bindings are for your regular workers only. You must use a dispatch binding to access workers in namespaces.

D

Drew•2/24/25, 7:23 PM

I setup a simple worker and api call to add a hostname and setup ssl. Got the message about contacting for enterprise. Wondering if workers for platforms will let me make that call without going through the full process and getting the message. Any upfront advice welcome!

DDrew I setup a simple worker and api call to add a hostname and setup ssl. Got the m...

D

Drew•2/24/25, 7:27 PM

Nevermind

I found it!

D

darkpool•2/27/25, 1:17 AM

how do we access the args object from dispatcher in a user worker? I am trying it locallly following the guide but cant figure it out.
From the types

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

I want to be able to do something like:

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

EDIT: looks like args is not implemented yet so going to try RPC.

DDmitry this worked!! ```ts import { WorkerEntrypoint } from 'cloudflare:workers' expor...

D

darkpool•2/27/25, 3:09 PM

Hi @Dmitry I did you get this working locally? I keep getting error: "worker.sum is not a function"

T

TDat•3/5/25, 10:52 AM

Hi, when uploading static assets with a normal worker, after deploying the worker, I'm automatically directed to the uploaded index.html file with js and css. However, if I deploy a platform worker and route to it with a dispatch worker, I can't get the app to be displayed. Is there any way serve files from platform worker to dispatch worker?

W

Walshy•3/5/25, 10:59 AM

Can you provide more info? It'll work the same way

T

TDat•3/5/25, 11:41 AM

@Walshy | Workers/Pages thanks for the response but I figured it out. I accidently passed the wrong subdomain.

S

Silvan•3/5/25, 12:37 PM

I honestly have a hard time understanding all use cases for platforms

lets say i sell unique websites to customers while also owning the domain. does this product still make sense? because so far normal workers can do the things i need

SSilvan I honestly have a hard time understanding all use cases for platforms lets say ...

A

Acе•3/5/25, 2:10 PM

No, that wouldn’t make sense for workers for platforms. It is more for giving the users of your website the ability to create their own workers, that usually extends the functionality of your website/app. For example, Shopify can use it to enable developers to create plugins for the checkout page, such as collecting additional information related to an order (e.g. a loyalty card number).

E

EinsiTang•3/7/25, 9:41 AM

hello , have someone here , I have same question about worker dev , fetch request always pending and I have no idea to fix it

E

EinsiTang•3/7/25, 9:53 AM

I can provide the warehouse and demonstration code to describe the problem. Is there anyone available to help me with code review?

D

Dagy•3/7/25, 9:06 PM

Hello community,

I’m trying to deploy a nuxt site to cloudflare. I used the nuxt starter from the cli.

But I haven’t been able to use the workers for the /server/api together with the hono library.
I get internal server error. And not functionality for the server/api

I haven’t this in my nuxt.config
export default defineNuxtConfig({
compatibilityDate: "2024-11-01",
devtools: { enabled: true },

nitro: {
preset: "cloudflare-module", // ← Correct preset here
},

modules: ["nitro-cloudflare-dev"],
vite: {
optimizeDeps: {
include: ["hono"],
},
},
});

I have this in my wrangler

{
"$schema": "node_modules/wrangler/config-schema.json",
"name": "test-1",
"compatibility_date": "2025-03-03",
"compatibility_flags": ["nodejs_compat"], // ← Required
"main": "./.output/server/index.mjs",
"assets": {
"binding": "ASSETS",
"directory": "./.output/public/"
},
"r2_buckets": [{ "binding": "BUCKET", "bucket_name": "your-bucket-name" }],
"kv_namespaces": [{ "binding": "KV", "id": "your-kv-id" }],
"d1_databases": [
{
"binding": "DB",
"database_name": "your-db-name",
"database_id": "your-db-id"
}
],
"ai": { "binding": "AI" },
"observability": { "enabled": true }
}

This my workers code:

// server/api/workers.js
import { Hono } from "hono";

const app = new Hono();

app.get("/", (c) => {
const name = c.req.query("name") || "World";
return c.json({ greeting:

Hello, ${name}!

Hello, ${name}!

Hello, ${name}!

Hello, ${name}! });
});

export default app;

R

rob•3/9/25, 1:34 PM

Pages or workers ?

C

cosbgn•3/9/25, 5:04 PM

Does worker for platform supports cron triggers?

T

thomasjiangcy•3/10/25, 3:45 PM

is there anyway to query bandwidth usage on a worker level within a dispatch namespace? e.g. want to charge for bandwidth as part of pricing

W

Walshy•3/10/25, 4:25 PM

Workers has no concept of bandwidth usage so no, not through our side

Maybe, though I should note that Assets is built primarily to serve HTML/JS/CSS, and while it can se

Similar Threads

Similar Threads

Similar Threads