JI would have to put the build step in the dashboard then? Can it do a cargo build?
JI 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 file, instead of the expected /functions/_worker.js.
KI’d probably just
&& mv it in my build commandJUnlucky me, I thought I had tried everything. I need to know whether this'll do it now.
JAh, I found the issue. This doesn't work with
wrangler2 pages dev
HYou could import shim from _worker.js
JThese are all great ideas, I am experimenting
JI am getting the wildest behaviour. I right now have the following build command:
When doing
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:
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.
When doing
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.
JEven more wildly, if I delete the
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.JI believe this is caused by some form of live-reloading that cannot be disabled. If I replace my build command with a
sleep 60, at no point does CloudFlare try to build the worker until the sleep is over. However, if I add a && sleep 60 to my build command, cloudflare will try to build my worker before the sleep has even started.JBasically, cloudflare is trying to bundle my worker while it is being built, which causes errors
HIs this in your
wrangler.tomlyep
Jbasically 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
JAny other way wrangler will try to bundle my worker and routes while the files are being produced still
HThat might be the issue. It is a bug that
wranglerI 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
HIIRC it is because it shares a good bit of its code with
wrangler dev
JWell, I assume some of it should be read, such as key-value namespaces?
HNo, bindings are configured via CLI flags
JI see, got it
JAlright, 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.
JI 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?
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?
HThe
shim.mjs shouldn't be in the output directory at all. Maybe try moving it somewhere else?J@HardlyHolidayin’ If I upload manually, I can only upload the output directory.
JAnd cloudflare's built-in build process doesn't work as it doesn't support cargo compiling.
Jwrangler2 doesn't seem to have any parameters that allow me to set the "public" directory to a subfolder.HAre you uploading via
wrangleryep!
HCan you give a folder structure, and your
deploy commandJHWhat if you move
worker out of dist, and then update the import in _worker.jsThen how do I upload it?
HIf it is imported by
_worker.jswell, it certainly is producing some sort of behaviour... I need to debug this a bit more clearly.
JI figured it out. Deploying with
wranglerah! I got it, the old standalone worker was still running and interfering, all good, all works!
JAn amazingly big thank you for the awesome help!
DThis 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?
DHi everyone, I want to Integrate Sentry with Page function, And I follow this docs
DThe Sentry Pages Plugin captures and logs all exceptions which occur below it in the execution chain of your Pages Functions. It is therefore …
DI have one question. What type of Sentry support for page function. I don't know which type is suitable. Please help,
D
DHi all - I'm confused, and struggling to understand how functions actually fit in.
I've used C3 to create a simple vue3 app with vue router and pina store.
After the fact, I've added a functions folder, with a simple helloworld.js as a function.
For the life of me, I cannot get the function to fire. At best I can get it to return the actual function itself, but invoking the function from within the app escapes me.
Any help or simple guides would be great! I know there is a guide for create-react-app, but I think vue router might be doing something weird.
UPDATE: I literally cannot get it to fire. The lack of decent documentation + the fact that wrangler throws a workerd error every 2 seconds has made me give up. Supabase Edge functions it is then.
I've used C3 to create a simple vue3 app with vue router and pina store.
After the fact, I've added a functions folder, with a simple helloworld.js as a function.
For the life of me, I cannot get the function to fire. At best I can get it to return the actual function itself, but invoking the function from within the app escapes me.
Any help or simple guides would be great! I know there is a guide for create-react-app, but I think vue router might be doing something weird.
UPDATE: I literally cannot get it to fire. The lack of decent documentation + the fact that wrangler throws a workerd error every 2 seconds has made me give up. Supabase Edge functions it is then.
Shey folks! maybe dumb question... In my repository I added the
functions folder taken from a tutorial I am following. Is that the only thing I need to do? I cannot see the functionality from the functions folder. I am following this: https://dev.to/charca/password-protection-for-cloudflare-pages-8ma . Does the functions folder need to be part of the build as well as in build/functions?
VIs the max Worker CPU time feature out yet? If so, is it available for Pages Functions?
KIs the max Worker CPU time feature out yet?Yes.
If so, is it available for Pages Functions?Yes.
KYou will need your usage model set to Standard, and it will appear below the usage model.
K