Serve static assets from root path, then handle /api/ requests with my worker?

I was hoping the "Static assets" feature could help me simplify my setup (currently Pages + Workers). I'm having trouble with

wrangler dev

wrangler dev

currently. I want to serve static assets (stored in

public

public

directory on filesystem) for every request except for

/api/

/api/

requests, which my worker should handle.

aleclarsonOP•3/13/25, 7:01 PM

I tried these things together:
- pass

--route "xyz.example.com/api/*"

--route "xyz.example.com/api/*"

to wrangler dev
- set

directory = "public"

directory = "public"

in the

[assets]

[assets]

section of my wrangler.toml

But my worker is still being invoked for non

/api/

/api/

requests.

aleclarsonOP•3/13/25, 7:05 PM

This part is a bit confusing:

In the event a request does not match a static asset, and there is no Worker script (or that Worker script calls
fetch()
fetch()
on the assets binding),
not_found_handling
not_found_handling
determines how Cloudflare will construct a response.

It says "…and there is no Worker script". But doesn't a worker script always exist when using the Static Assets feature?

aleclarsonOP•3/13/25, 7:18 PM

Aww, I was really hoping this would work:

routes = [
  "xyz.example.com/api/*",
  { pattern = "xyz.example.com/*", zone_name = "assets.local" }
]

routes = [
  "xyz.example.com/api/*",
  { pattern = "xyz.example.com/*", zone_name = "assets.local" }
]

aleclarsonOP•3/13/25, 7:18 PM

(in

wrangler dev

wrangler dev

)

aleclarsonOP•3/13/25, 7:32 PM

Am I forced to deploy two workers for this use case?

aleclarsonOP•3/13/25, 7:32 PM

Might as well use Pages at that point, I suppose..

Aaleclarson I was hoping the "Static assets" feature could help me simplify my setup (curren...

Chaika•3/13/25, 7:34 PM

By default, anything that matches a static asset skips your worker, and everything else hits it
So you don't pay for static asset hits/they don't invoke your worker, but you can have your worker api as well

Chaika•3/13/25, 7:36 PM

you can pass the request to the static assets binding in your worker if it doesn't match a static asset and invokes it, to invoke the default 404 behavior:
return await env.ASSETS.fetch(request);

CChaika By default, anything that matches a static asset skips your worker, and everythi...

aleclarsonOP•3/13/25, 7:36 PM

Right, yet I'm using

single-page-application

single-page-application

setting, so HTML pages other than

end up hitting the worker first, sadly.

aleclarsonOP•3/13/25, 7:36 PM

Yeah I'm trying to avoid the worker invocation for static assets

aleclarsonOP•3/13/25, 7:37 PM

I'm thinking of using Pages and Pages Functions instead of Workers

Chaika•3/13/25, 7:37 PM

It's a long way off but eventually Pages will be moved to Workers Assets (and with a solid migration plan)

aleclarsonOP•3/13/25, 7:38 PM

Please see if my use case is being tracked internally. Thank you

aleclarsonOP•3/13/25, 7:38 PM

For now, I'll go with Pages. Thanks for the help!

awkweb•4/5/25, 12:16 AM

I want to serve static assets (stored in
public
public
directory on filesystem) for every request except for
/api/
/api/
requests, which my worker should handle.

Is this something that static assets might support?

love static assets concept, but doesn't work when i need to handle an oauth callback (e.g.

/api/callback

/api/callback

) since the worker won't be hit (unless i turn on

run_worker_first

run_worker_first

- which i want to avoid).

awkweb•4/5/25, 12:23 AM

maybe this is the issue https://github.com/cloudflare/workers-sdk/issues/8430

GitHub

🐛 BUG: @cloudflare/vite-plugin ignore `run_worker_first` · Issu...

Which Cloudflare product(s) does this pertain to? Vite Plugin What versions are you using? 0.1.9 [@cloudflare/vite-plugin] What operating system and version are you using? Mac Sequoia 15.3.1 Please...

Aaleclarson For now, I'll go with Pages. Thanks for the help!

Chaika•4/5/25, 1:13 AM

They did eventually add a fix for this: https://github.com/cloudflare/workers-sdk/pull/8443/files, which I believe is active now if your compat date is greater then April 1st. Basically leveraging a header browsers have supported since 2023, and if you have the spa not found mode on, it'll just work

Aawkweb > I want to serve static assets (stored in `public` directory on filesystem) for...

Chaika•4/5/25, 1:14 AM

Doesn't sound like his issue, that should just work, he wanted it the other way around

CChaika Doesn't sound like his issue, that should just work, he wanted it the other way ...

awkweb•4/5/25, 1:44 AM

Might be doing something wrong, but just following this example https://developers.cloudflare.com/workers/static-assets/

trying to hit http://localhost:5173/api/ in the browser shows the react app, not

{ name: "Cloudflare" }

{ name: "Cloudflare" }

Cloudflare Docs

Static Assets · Cloudflare Workers docs

Create full-stack applications deployed to Cloudflare Workers.

Aawkweb Might be doing something wrong, but just following this example https://develope...

Chaika•4/5/25, 1:48 AM

Sounds like you're running vite/not wrangler. It'd be easier if you made your own thread for help. I tried the same simple docs setup, with a single index.html, and it serves as expected

Serve static assets from root path, then handle /api/ requests with my worker?

Similar Threads

Similar Threads

Similar Threads