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

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

H

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

You could import shim from _worker.js

J

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

These are all great ideas, I am experimenting

J

JeroenOP•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 )"

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

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.

J

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

Even more wildly, if I delete the

frontend/dist

frontend/dist

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.

J

JeroenOP•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

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

&& sleep 60

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

J

JeroenOP•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...

H

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

Is this in your

wrangler.toml

wrangler.toml

?

J

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

yep

J

JeroenOP•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

J

JeroenOP•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

H

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

J

JeroenOP•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...

H

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...

J

JeroenOP•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?

H

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

No, bindings are configured via CLI flags

J

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

I see, got it

J

JeroenOP•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

J

JeroenOP•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...

H

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

The

shim.mjs

shim.mjs

shim.mjs

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

J

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

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

J

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

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

J

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

wrangler2

wrangler2

wrangler2

wrangler2 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.

H

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

Are you uploading via

wrangler

wrangler

?

J

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

yep!

JJeroen yep!

H

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

Can you give a folder structure, and your

deploy

deploy

deploy

deploy command

J

JeroenOP•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

❯ 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

wrangler2 pages deploy dist --project-name=project

wrangler2 pages deploy dist --project-name=project

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

H

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

What if you move

worker

worker

worker

worker out of dist, and then update the import in

_worker.js

_worker.js

_worker.js

_worker.js?

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

J

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

Then how do I upload it?

JJeroen Then how do I upload it?

H

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

If it is imported by

_worker.js

_worker.js

_worker.js

_worker.js, it should be bundled automatically

J

JeroenOP•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

J

JeroenOP•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?

J

JeroenOP•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

J

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

An amazingly big thank you for the awesome help!

D

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?

D

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

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

D

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 …

D

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,

D

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

D

deathpenguin122•11/20/23, 9:20 AM

Hi 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.

S

ssbarbee•11/20/23, 10:55 AM

hey folks! maybe dumb question... In my repository I added the

functions

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

functions

folder. I am following this: https://dev.to/charca/password-protection-for-cloudflare-pages-8ma . Does the

functions

functions

folder need to be part of the build as well as in

build/functions

build/functions

build/functions

build/functions?

V

Village (Josef)•11/21/23, 3:55 AM

Is the max Worker CPU time feature out yet? If so, is it available for Pages Functions?

K

kian•11/21/23, 3:57 AM

Is the max Worker CPU time feature out yet?

Yes.

If so, is it available for Pages Functions?

Yes.

K

kian•11/21/23, 3:57 AM

You will need your usage model set to Standard, and it will appear below the usage model.

K

kian•11/21/23, 3:57 AM

V

Village (Josef)•11/21/23, 4:01 AM

Ahhh

V

Village (Josef)•11/21/23, 4:02 AM

Thank you!

A

ALMHERICH😊•11/21/23, 4:14 AM

Hello

A

ALMHERICH😊•11/21/23, 4:16 AM

How can i recieve my cashout in paid2play thanks

K

kian•11/21/23, 4:16 AM

That isn't related to Cloudflare, you would have to contact the site owners.

L

Leon338•11/21/23, 7:16 PM

Anyone know why I can't access my local KV?
Start Command

wrangler pages dev --kv=MY_KV --compatibility-date=2023-10-30 --proxy 3000 -- npm run dev

wrangler pages dev --kv=MY_KV --compatibility-date=2023-10-30 --proxy 3000 -- npm run dev

wrangler pages dev --kv=MY_KV --compatibility-date=2023-10-30 --proxy 3000 -- npm run dev

wrangler pages dev --kv=MY_KV --compatibility-date=2023-10-30 --proxy 3000 -- npm run dev

Function

export default defineEventHandler(({ context }) => {
  return context;
});

export default defineEventHandler(({ context }) => {
  return context;
});

export default defineEventHandler(({ context }) => {
  return context;
});

export default defineEventHandler(({ context }) => {
  return context;
});

Context

{
  "_nitro": {
    "routeRules": {}
  },
  "nitro": {
    "errors": []
  },
  "matchedRoute": {
    "path": "/api/hello",
    "handlers": {}
  },
  "params": {}
}

{
  "_nitro": {
    "routeRules": {}
  },
  "nitro": {
    "errors": []
  },
  "matchedRoute": {
    "path": "/api/hello",
    "handlers": {}
  },
  "params": {}
}

{
  "_nitro": {
    "routeRules": {}
  },
  "nitro": {
    "errors": []
  },
  "matchedRoute": {
    "path": "/api/hello",
    "handlers": {}
  },
  "params": {}
}

{
  "_nitro": {
    "routeRules": {}
  },
  "nitro": {
    "errors": []
  },
  "matchedRoute": {
    "path": "/api/hello",
    "handlers": {}
  },
  "params": {}
}

It's nuxt. And if I try to access it like in the Docs context.cloudflare.env.MY_KV; I get cloudflare isn't defined

Error

[proxy]: [nuxt] [request error] [unhandled] [500] Cannot read properties of undefined (reading 'env')

[proxy]: [nuxt] [request error] [unhandled] [500] Cannot read properties of undefined (reading 'env')

[proxy]: [nuxt] [request error] [unhandled] [500] Cannot read properties of undefined (reading 'env')

[proxy]: [nuxt] [request error] [unhandled] [500] Cannot read properties of undefined (reading 'env')

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

Similar Threads

Similar Threads

Similar Threads