I would be very surprised if it isn't planned. This is an often-requested feature. It seems like the

I would be very surprised if it isn't planned. This is an often-requested feature. It seems like there are just other features that are prioritised over it

zegevlierOP•11/15/23, 10:13 PM

You can always deploy a worker with a cron trigger or use DO alarms.

Zzegevlier I would be very surprised if it isn't planned. This is an often-requested featur...

Hello, I’m Allie!•11/15/23, 10:41 PM

I’m guessing this is a why bother, it will work in convergence situation

Dfodor•11/16/23, 7:32 AM

So, is there a good way to prevent CSRF attacks on pages with forms? I figured that I could have javascript request a form from a worker after the webpage has been loaded, but I'm uncertain that would work.

Jeroen•11/16/23, 9:21 PM

Does the workers-rs library also work for Pages Functions?

kian•11/17/23, 12:40 AM

It'd probably work with https://developers.cloudflare.com/pages/platform/functions/advanced-mode/

Kkian It'd probably work with <https://developers.cloudflare.com/pages/platform/functi...

Jeroen•11/17/23, 4:01 AM

I would have to put the build step in the dashboard then? Can it do a cargo build?

Kkian It'd probably work with <https://developers.cloudflare.com/pages/platform/functi...

Jeroen•11/19/23, 3:06 PM

I looked into this, but I do not think this will work. The wasm-pack wrapper is hard-coded to always put the worker in the

/build/worker/shim.mjs

/build/worker/shim.mjs

file, instead of the expected

/functions/_worker.js

/functions/_worker.js

kian•11/19/23, 3:07 PM

I’d probably just

&& mv

&& mv

it in my build command

Jeroen•11/19/23, 3:09 PM

Unlucky me, I thought I had tried everything. I need to know whether this'll do it now.

Kkian I’d probably just `&& mv` it in my build command

Jeroen•11/19/23, 3:20 PM

Ah, I found the issue. This doesn't work with

wrangler2 pages dev

wrangler2 pages dev

JJeroen Ah, I found the issue. This doesn't work with `wrangler2 pages dev`

Hello, I’m Allie!•11/19/23, 3:23 PM

You could import shim from _worker.js

Jeroen•11/19/23, 3:23 PM

These are all great ideas, I am experimenting

Jeroen•11/19/23, 3:48 PM

I am getting the wildest behaviour. I right now have the following build command:

command = "( cd backend && cargo install -q worker-build && worker-build --release ) && ( cd frontend && yarn run build )"

command = "( cd backend && cargo install -q worker-build && worker-build --release ) && ( cd frontend && yarn run build )"

When doing

wrangler2 pages dev frontend/dist

wrangler2 pages dev frontend/dist

, I get an error:

✘ [ERROR] Could not validate _routes.json at /home/jeroen/project/frontend/dist: Error: ENOENT: no such file or directory, open '/home/jeroen/project/frontend/dist/_routes.json'

However, this error occurs while yarn is still building the frontend, as in, it'll be in the middle of the build logs. Not sure what is going on there. I get a similar error from the worker:

✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.

▲ [WARNING] Failed to bundle _worker.js. Error: Build failed with 1 error:

../../.wrangler/tmp/bundle-sGxLQ0/middleware-insertion-facade.js:1:43: ERROR: Could not resolve
"/home/jeroen/project/frontend/dist/_worker.js"
at failureErrorWithLog
(/usr/lib/node_modules/wrangler/node_modules/esbuild/lib/main.js:1636:15)
at /usr/lib/node_modules/wrangler/node_modules/esbuild/lib/main.js:1048:25
at /usr/lib/node_modules/wrangler/node_modules/esbuild/lib/main.js:1512:9
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
errors: [
{
detail: undefined,
id: '',
location: [Object],
notes: [],
pluginName: '',
text: 'Could not resolve
"/home/jeroen/project/frontend/dist/_worker.js"'
}
],
warnings: []
}

Compiled Worker successfully

As you can see, despite CloudFlare alleging the worker doesn't exist, it compiles successfully and actually runs. All of this output is produced while the build command is still running.

Jeroen•11/19/23, 3:50 PM

Even more wildly, if I delete the

frontend/dist

frontend/dist

directory, my worker will not work. It won't even be detected. So CloudFlare seems to insist my worker already exists before the build command is ran, and then compiles it while the build command runs.

Jeroen•11/19/23, 4:34 PM

I believe this is caused by some form of live-reloading that cannot be disabled. If I replace my build command with a

sleep 60

sleep 60

, at no point does CloudFlare try to build the worker until the sleep is over. However, if I add a

&& sleep 60

&& sleep 60

to my build command, cloudflare will try to build my worker before the sleep has even started.

Jeroen•11/19/23, 4:34 PM

Basically, cloudflare is trying to bundle my worker while it is being built, which causes errors

JJeroen I am getting the wildest behaviour. I right now have the following build command...

Hello, I’m Allie!•11/19/23, 4:35 PM

Is this in your

wrangler.toml

wrangler.toml

Jeroen•11/19/23, 4:35 PM

yep

Jeroen•11/19/23, 4:36 PM

basically the only way I can get it to work is:

Comment out command = in my wrangler.toml.
Run the command manually
Run wrangler pages dev frontend/dist

Jeroen•11/19/23, 4:37 PM

Any other way wrangler will try to bundle my worker and routes while the files are being produced still

JJeroen yep

Hello, I’m Allie!•11/19/23, 4:37 PM

That might be the issue. It is a bug that

wrangler

wrangler

reads your config when using Pages

Jeroen•11/19/23, 4:38 PM

I see, I was under the impression it was intended behaviour so tried to get it to work nicely. That also explains why some values in the wrangler.toml are seemingly ignored such as the compatibility date

JJeroen I see, I was under the impression it was intended behaviour so tried to get it t...

Hello, I’m Allie!•11/19/23, 4:39 PM

IIRC it is because it shares a good bit of its code with

wrangler dev

wrangler dev

, so it unintentionally reads the config, even though it shouldn't

HHello, I’m Allie!IIRC it is because it shares a good bit of its code with `wrangler dev`, so it u...

Jeroen•11/19/23, 4:40 PM

Well, I assume some of it should be read, such as key-value namespaces?

JJeroen Well, I assume some of it _should_ be read, such as key-value namespaces?

Hello, I’m Allie!•11/19/23, 4:41 PM

No, bindings are configured via CLI flags

Jeroen•11/19/23, 4:42 PM

I see, got it

Jeroen•11/19/23, 5:19 PM

Alright, my only final hurdle is that I now need to deploy it, which requires building it. I assume building it on the cloud is not the way to go here.

HHello, I’m Allie!No, bindings are configured via CLI flags

Jeroen•11/19/23, 6:46 PM

I got it to work this way! I did have to disable Cloudflare's built-in build process though, and upload manually with wrangler.

One side-effect is that all my backend code is accessible through the web now, as people can navigate to ./shim.mjs etc. Is there a way to stop that? I am thinking of making a redirect rule, but perhaps something more elegant works?

JJeroen I got it to work this way! I did have to disable Cloudflare's built-in build pro...

Hello, I’m Allie!•11/19/23, 6:48 PM

The

shim.mjs

shim.mjs

shouldn't be in the output directory at all. Maybe try moving it somewhere else?

Jeroen•11/19/23, 6:49 PM

@HardlyHolidayin’ If I upload manually, I can only upload the output directory.

Jeroen•11/19/23, 6:49 PM

And cloudflare's built-in build process doesn't work as it doesn't support cargo compiling.

Jeroen•11/19/23, 6:50 PM

wrangler2wrangler2 doesn't seem to have any parameters that allow me to set the "public" directory to a subfolder.

JJeroen @HardlyHolidayin’ If I upload manually, I can only upload the output directory.

Hello, I’m Allie!•11/19/23, 6:50 PM

Are you uploading via

wrangler

wrangler

Jeroen•11/19/23, 6:50 PM

yep!

JJeroen yep!

Hello, I’m Allie!•11/19/23, 6:52 PM

Can you give a folder structure, and your deploydeploy command

Jeroen•11/19/23, 6:52 PM

❯ tree dist                 
dist
├── _astro
│   └── index.efe4faea.css
├── favicon.svg
├── index.html
├── _routes.json
├── worker
│   ├── index.wasm
│   └── shim.mjs
└── _worker.js

❯ tree dist                 
dist
├── _astro
│   └── index.efe4faea.css
├── favicon.svg
├── index.html
├── _routes.json
├── worker
│   ├── index.wasm
│   └── shim.mjs
└── _worker.js

wrangler2 pages deploy dist --project-name=project

wrangler2 pages deploy dist --project-name=project

JJeroen ``` ❯ tree dist dist ├── _astro │ └── index.efe4faea.css ├── ...

Hello, I’m Allie!•11/19/23, 6:53 PM

What if you move workerworker out of dist, and then update the import in _worker.js_worker.js?

HHello, I’m Allie!What if you move `worker` out of dist, and then update the import in `_worker.js...

Jeroen•11/19/23, 6:54 PM

Then how do I upload it?

JJeroen Then how do I upload it?

Hello, I’m Allie!•11/19/23, 6:55 PM

If it is imported by _worker.js_worker.js, it should be bundled automatically

Jeroen•11/19/23, 7:01 PM

well, it certainly is producing some sort of behaviour... I need to debug this a bit more clearly.

HHello, I’m Allie!If it is imported by `_worker.js`, it should be bundled automatically

Jeroen•11/19/23, 7:48 PM

I figured it out. Deploying with

wrangler

wrangler

does not deploy to any connected domains. Any clues on this?

Jeroen•11/19/23, 7:50 PM

ah! I got it, the old standalone worker was still running and interfering, all good, all works!

HHello, I’m Allie!If it is imported by `_worker.js`, it should be bundled automatically

Jeroen•11/19/23, 7:50 PM

An amazingly big thank you for the awesome help!

Dave P•11/20/23, 12:18 AM

This might be a stupid question. If I make a full stack app on Pages using Svektekit, where do I place the backend logic? If it's page specific, can I place it in +page.server? If I have complex logic, should I place it in /functions? Or does it matter? Can I place it in /api, for example?

David Charles•11/20/23, 6:58 AM

Hi everyone, I want to Integrate Sentry with Page function, And I follow this docs

David Charles•11/20/23, 6:58 AM

https://developers.cloudflare.com/pages/platform/functions/plugins/sentry

Sentry · Cloudflare Pages docs

The Sentry Pages Plugin captures and logs all exceptions which occur below it in the execution chain of your Pages Functions. It is therefore …

David Charles•11/20/23, 6:59 AM

I have one question. What type of Sentry support for page function. I don't know which type is suitable. Please help,

I would be very surprised if it isn't planned. This is an often-requested feature. It seems like the

Similar Threads