I don't understand how I can bind static assets to a path without invoking a billed Worker; what am

Ddave I don't understand how I can bind static assets to a path without invoking a bil...

H

Hard@Work•3/31/25, 8:52 PM

Just set a Route?

Cloudflare Docs

Configuration - Wrangler · Cloudflare Workers docs

Use a configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.

HHard@Work Just set a [Route](https://developers.cloudflare.com/workers/wrangler/configurat...

D

daveOP•3/31/25, 8:53 PM

but then I am paying per request like a normal Worker, no?

Ddave but then I am paying per request like a normal Worker, no?

H

Hard@Work•3/31/25, 8:53 PM

Not if you don't have a

main

main

H

Hard@Work•3/31/25, 8:53 PM

Or if you set Assets to return assets first, instead of running your Worker code

HHard@Work Or if you set Assets to return assets first, instead of running your Worker code

D

daveOP•3/31/25, 8:54 PM

ah so it will look in the static folder first for like robots.txt, and if that's a miss, then invoke my Worker?

Ddave ah so it will look in the static folder first for like robots.txt, and if that's...

H

Hard@Work•3/31/25, 8:57 PM

Yep, that's what it does by default

S

Silvan•3/31/25, 9:00 PM

Also means that if you have an SPA any sub route that gets directly accessed. aka domain.com/blog will get billed because it will go through

env.ASSETS.fetch

env.ASSETS.fetch

right?

D

daveOP•3/31/25, 9:01 PM

oooo good question..

S

Silvan•3/31/25, 9:02 PM

yea i had that issue. when i refreshed a sub route i got a 404 so i had to add

app.get('/*', (c) => {
    return c.env.ASSETS.fetch(c.req.raw);
});

app.get('/*', (c) => {
    return c.env.ASSETS.fetch(c.req.raw);
});

app.get('/*', (c) => {
    return c.env.ASSETS.fetch(c.req.raw);
});

app.get('/*', (c) => {
    return c.env.ASSETS.fetch(c.req.raw);
});

at the end of the main aka server.ts

S

Silvan•3/31/25, 9:03 PM

this is also why im patiently waiting for sveltekit support with the vite plugin (id assume there i wouldnt run into this issue?)

F

fas3r_•3/31/25, 10:13 PM

can

selflare

selflare

selflare

selflare to dev locally for pages ?

W

Walshy•3/31/25, 10:14 PM

what is selfflare?

F

fas3r_•3/31/25, 10:14 PM

https://github.com/JacobLinCool/selflare

F

fas3r_•3/31/25, 10:14 PM

(local dev for cloudflare)

W

Walshy•3/31/25, 10:16 PM

err no

W

Walshy•3/31/25, 10:16 PM

you should use wrangler

B

Boop Dog•3/31/25, 10:24 PM

Hey all, I'm trying to access my kv table but I keep getting

Cannot read properties of undefined (reading 'get')

Cannot read properties of undefined (reading 'get')

Cannot read properties of undefined (reading 'get')

Cannot read properties of undefined (reading 'get')

name = "correct-worker-name"
main = "worker.js"
compatibility_date = "2023-08-23"

kv_namespaces = [
  { binding = "WORKER_KV", id = "correctid-123" }
]

name = "correct-worker-name"
main = "worker.js"
compatibility_date = "2023-08-23"

kv_namespaces = [
  { binding = "WORKER_KV", id = "correctid-123" }
]

name = "correct-worker-name"
main = "worker.js"
compatibility_date = "2023-08-23"

kv_namespaces = [
  { binding = "WORKER_KV", id = "correctid-123" }
]

name = "correct-worker-name"
main = "worker.js"
compatibility_date = "2023-08-23"

kv_namespaces = [
  { binding = "WORKER_KV", id = "correctid-123" }
]

export default {
  async fetch(request, env, ctx) {
    const value = await env.WORKER_KV.get("thecorrectkey-123");
    return new Response(value);
  },
};

export default {
  async fetch(request, env, ctx) {
    const value = await env.WORKER_KV.get("thecorrectkey-123");
    return new Response(value);
  },
};

export default {
  async fetch(request, env, ctx) {
    const value = await env.WORKER_KV.get("thecorrectkey-123");
    return new Response(value);
  },
};

export default {
  async fetch(request, env, ctx) {
    const value = await env.WORKER_KV.get("thecorrectkey-123");
    return new Response(value);
  },
};

B

Boop Dog•3/31/25, 10:24 PM

I'm not really sure why I keep getting it?

B

Boop Dog•3/31/25, 10:24 PM

If it means anything I'm just using the web dashboard to write something quick

W

Walshy•3/31/25, 10:26 PM

dash doesn't read wrangler.toml

W

Walshy•3/31/25, 10:26 PM

so you'll want to add the binding in the dash too

B

Boop Dog•3/31/25, 10:26 PM

ah that's annoying

B

Boop Dog•3/31/25, 10:26 PM

I was able to get it to show but it sucks it doesn't just read it alr

B

Boop Dog•3/31/25, 10:27 PM

thank you!

F

fas3r_•3/31/25, 10:41 PM

so if I understand correct, if I have a folder

functions

functions

functions

functions in my (react) pages project, this folder will be use for the "backend" (receive request) where I can safely import my

Secrets

Secrets

Secrets

Secrets (using env).
( assumed from https://developers.cloudflare.com/pages/tutorials/build-an-api-with-pages-functions/#2-build-your-api )

D

danawoodman•4/1/25, 12:34 AM

question about logging: I have observability on and a head sampling set to 1 (verified in wrangler.jsonc and UI) but I am seeing very infrequent logging. With "live" on I don't seen any requests despite many logs that should be firing. The app in question is using Astro using Cloudflare Workers deploy/CI.

Ffas3r_so if I understand correct, if I have a folder `functions` in my (react) pages ...

I

Isaac McFadyen•4/1/25, 12:54 AM

React: what kind of React is this? If it's a framework like Next.js you need to use the framework's version of Functions, you can't use the functions folder directly.

H

HereToHelp•4/1/25, 1:06 AM

I've been using Cloudflare to set up a url-accessible web build of a game I contribute to (R2 Bucket for the game's files, connected to a Worker to serve it to users). Since I'm pretty inexperienced when it comes to web infrastructure, I want to check my work security-wise.
There are no sensitive files in our build, so we're not worried about reading, but we obviously don't want users to be able to modify the contents of our R2 Bucket. The worker is coded to return 403 (or 400) for any requests that aren't

GET

GET

or

HEAD

HEAD

HEAD

HEAD. As best I can tell, this should make it impossible for users to modify our files, unless they can somehow modify the code of the worker itself (I assume they can't). Is that correct, or is there something else I need to do to make sure our web build is secure?

HHereToHelp I've been using Cloudflare to set up a url-accessible web build of a game I cont...

H

Hello, I’m Allie!•4/1/25, 1:11 AM

Assuming that you never call any functions that write/delete from the bucket, it doesn’t matter what requests they send to your Worker

H

Hello, I’m Allie!•4/1/25, 1:11 AM

They could send all of the POSTs they want, and it wouldn’t do anything

H

HereToHelp•4/1/25, 1:11 AM

Awesome, thanks for the confirmation!

く

くもりにくもったクラウドサービスlocaler•4/1/25, 6:40 AM

When I use Cloudflare Pages by calling wasm, I get

CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder

CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder

CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder

CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder.
Any guidance on how to resolve this would be appreciated.

G

glncy•4/1/25, 7:40 AM

Hi Everyone. New to cloudflare. I am trying to access AI via Curl and also using bindings but i am getting this error. thank you

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 7010,
      "message": "Service unavailable"
    }
  ],
  "messages": [
    
  ]
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 7010,
      "message": "Service unavailable"
    }
  ],
  "messages": [
    
  ]
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 7010,
      "message": "Service unavailable"
    }
  ],
  "messages": [
    
  ]
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 7010,
      "message": "Service unavailable"
    }
  ],
  "messages": [
    
  ]
}

B

Barry•4/1/25, 9:34 AM

When using the Browser Rendering API, has anyone encountered issues with transformed elements? I have some skewed elements on my website but they are not rendered, just an empty space. It's just a skewY(10deg) en the text is skewY(-deg), is that because it uses GPU or somethign? Can we tweak the API to force it?

くくもりにくもったクラウドサービスlocaler When I use Cloudflare Pages by calling wasm, I get `CompileError: WebAssembly.in...

S

Silvan•4/1/25, 12:13 PM

the wasm needs to be inside ur bundle. as mentioned here workers-and-pages-discussions

S

Silvan•4/1/25, 12:14 PM

Do i understand this right.

if i want to deploy a pure static page with worker assets i just need

  "assets": {
    "directory": "./dist",
    "binding": "ASSETS"
  }

  "assets": {
    "directory": "./dist",
    "binding": "ASSETS"
  }

  "assets": {
    "directory": "./dist",
    "binding": "ASSETS"
  }

  "assets": {
    "directory": "./dist",
    "binding": "ASSETS"
  }

and no main?

S

Silvan•4/1/25, 12:16 PM

nvm i dont need the binding either ofc

く

くもりにくもったクラウドサービスlocaler•4/1/25, 12:55 PM

Does this mean that Wasm with Base64-encoded Data URLs does not work with Cloudflare Pages?

くくもりにくもったクラウドサービスlocaler Does this mean that Wasm with Base64-encoded Data URLs does not work with Cloudf...

I

Isaac McFadyen•4/1/25, 12:58 PM

Correct, any dynamic code (code that is compiled or constructed during runtime) is disallowed on Cloudflare Workers and Cloudflare Pages for security reasons

I

Isaac McFadyen•4/1/25, 12:58 PM

https://developers.cloudflare.com/workers/runtime-apis/web-standards/#javascript-standards

I

Isaac McFadyen•4/1/25, 1:01 PM

If you're interested there's a good talk on the security model of Workers from the engineering lead on the Workers team: https://www.infoq.com/presentations/cloudflare-v8/

LLemon hey, did anyone tried to display `CF_PAGES_COMMIT_SHA` within a Vite React proje...

L

Lemon•4/1/25, 4:07 PM

if any other peep bashing their head with this trash documentation here is the solution

edit your

vite.config.ts

vite.config.ts

like so (or add these lines)

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vite.dev/config/
export default defineConfig({
  plugins: [react()],
  define: {
    "import.meta.env.CF_PAGES": JSON.stringify(process.env.CF_PAGES || "1"),
    "import.meta.env.CF_PAGES_URL": JSON.stringify(process.env.CF_PAGES_URL || "unresolved"),
    "import.meta.env.CF_PAGES_BRANCH": JSON.stringify(process.env.CF_PAGES_BRANCH || "unresolved"),
    "import.meta.env.CF_PAGES_COMMIT_SHA": JSON.stringify(process.env.CF_PAGES_COMMIT_SHA || "unknown"),
  },
})

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vite.dev/config/
export default defineConfig({
  plugins: [react()],
  define: {
    "import.meta.env.CF_PAGES": JSON.stringify(process.env.CF_PAGES || "1"),
    "import.meta.env.CF_PAGES_URL": JSON.stringify(process.env.CF_PAGES_URL || "unresolved"),
    "import.meta.env.CF_PAGES_BRANCH": JSON.stringify(process.env.CF_PAGES_BRANCH || "unresolved"),
    "import.meta.env.CF_PAGES_COMMIT_SHA": JSON.stringify(process.env.CF_PAGES_COMMIT_SHA || "unknown"),
  },
})

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vite.dev/config/
export default defineConfig({
  plugins: [react()],
  define: {
    "import.meta.env.CF_PAGES": JSON.stringify(process.env.CF_PAGES || "1"),
    "import.meta.env.CF_PAGES_URL": JSON.stringify(process.env.CF_PAGES_URL || "unresolved"),
    "import.meta.env.CF_PAGES_BRANCH": JSON.stringify(process.env.CF_PAGES_BRANCH || "unresolved"),
    "import.meta.env.CF_PAGES_COMMIT_SHA": JSON.stringify(process.env.CF_PAGES_COMMIT_SHA || "unknown"),
  },
})

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vite.dev/config/
export default defineConfig({
  plugins: [react()],
  define: {
    "import.meta.env.CF_PAGES": JSON.stringify(process.env.CF_PAGES || "1"),
    "import.meta.env.CF_PAGES_URL": JSON.stringify(process.env.CF_PAGES_URL || "unresolved"),
    "import.meta.env.CF_PAGES_BRANCH": JSON.stringify(process.env.CF_PAGES_BRANCH || "unresolved"),
    "import.meta.env.CF_PAGES_COMMIT_SHA": JSON.stringify(process.env.CF_PAGES_COMMIT_SHA || "unknown"),
  },
})

C

crossbeau•4/1/25, 4:08 PM

if I were to create say 3 pages projects:
my-app-dev=====\
my-app-stage========== single-project-repo. (dev branch, stage branch, main branch)
my-app-prod ===/

how could I handle indepedent variables for each with a single wrangler file? can I have global values for all and then manually set values for each using api ? or would api settings overwrite values set by wrangler ?

C

crossbeau•4/1/25, 4:08 PM

I know I can do this with workers, but just unsure of how to handle this for pages

LLemon if any other peep bashing their head with this trash documentation here is the s...

I

Isaac McFadyen•4/1/25, 4:09 PM

Per Vite docs, only variables prefixed with

VITE_

VITE_

will be exposed to the build without that config change, yes https://vite.dev/guide/env-and-mode.html#env-variables

IIsaac McFadyen Per Vite docs, only variables prefixed with `VITE_` will be exposed to the build...

L

Lemon•4/1/25, 4:13 PM

Nah bro I agree to disagree It took me 3 hours to debug this.
You have to put these variables into your config without this the import.meta.env wont see the Cloudflare injected variables and noone talks about this.
Without the config.ts there is nothing CF related in the import.meta.env https://38625370.trash-vars.pages.dev/
With the config.ts CF populates and injects the variables as should be by default https://2d4b43b9.trash-vars.pages.dev/

LLemon Nah bro I agree to disagree It took me 3 hours to debug this. You have to put th...

I

Isaac McFadyen•4/1/25, 4:14 PM

Yes I understand that, but that's because Vite only puts variables that start with the

VITE_

VITE_

prefix into import.meta.env, which is why that config change is required

I

Isaac McFadyen•4/1/25, 4:15 PM

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA doesn't start with

VITE_

VITE_

and so Vite hides it because it assumes you don't want to expose it to client code

L

Lemon•4/1/25, 4:16 PM

Yeah I get it, but it would be nice to put these comments/precautions in to the CF docs (https://developers.cloudflare.com/pages/framework-guides/deploy-a-vite3-project/)
Could you push stuff like this to the CF team?

Cloudflare Docs

Vite 3 · Cloudflare Pages docs

Vite is a next-generation build tool for front-end developers. With the release of Vite 3, developers can make use of new command line (CLI) improvements, starter templates, and more to help build their front-end applications.

I don't understand how I can bind static assets to a path without invoking a billed Worker; what am

Similar Threads

Similar Threads

Similar Threads