It kind of does though, if you work on it locally you can deploy the worker with wrangler and I beli

It kind of does though, if you work on it locally you can deploy the worker with wrangler and I believe it will use the commit description that you last used on it. You can also then go to the dashboard and see that history and rollback to whatever deployment you had

DDahoom It kind of does though, if you work on it locally you can deploy the worker with...

tozz•8/31/23, 5:42 AM

Sure and that works well for a single dev, but if I had multiple people working on it and perhaps mulitple workers (I'm currently looking at having just one for now and do routing) I'd prefer everyone not having to deploy from their machines

tozz•8/31/23, 5:43 AM

But it's a minor thing really, for now I just want to get more clarity on when to use what

DahoomOP•8/31/23, 7:34 AM

Apparently from what I've learnt it's ok to have 1 worker containing everything you need since it only really affects cold start times, and as long as it's warm it should be instant I think

DahoomOP•8/31/23, 7:35 AM

Just make sure any new npm packages don't bloat your worker, I had some random packages I didn't even use much load entire 7MB json files into the worker

DDahoom Just make sure any new npm packages don't bloat your worker, I had some random p...

tozz•8/31/23, 9:16 AM

The dangers of npm, I'm a frequent user of bundlephobia.com for that reason

Altrius•8/31/23, 1:54 PM

could be a compression issue

Altrius•8/31/23, 1:54 PM

im having a similar sort of problem with a specific deployment of my site, but every other deployment is fine

Altrius•8/31/23, 1:57 PM

I have not managed to fix it

Altrius•8/31/23, 1:57 PM

it seems to only happen on my own network which is weird

Mmaximilliangeorge Okay, I'm going nuts. I've logged just about everything to narrow it down. The...

James•8/31/23, 3:03 PM

I'm going to escalate this for you - we've seen this happening quite a bit recently.

James•8/31/23, 3:29 PM

Thanks Matt

yatheesh•9/1/23, 3:30 AM

Hi , i am trying to run pages functions locally and getting error "✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above." Wrangler is compiling the pages function to worker successfully . My env is Ubuntu 23.04 + node v20.5.1 + npm 10.0.0 +Vite - React . Am i missing something ?

simpson•9/1/23, 3:17 PM

If you load an SSR page that has 20 static assets (jpgs, etc...) does every time that page loads for a new user get counted as 21 function invocations against your total (page + all assets) as seen in the real-time logs?

Ssimpson If you load an SSR page that has 20 static assets (jpgs, etc...) does every time...

Hello, I’m Allie!•9/1/23, 7:05 PM

It depends on how good you/your framework is at generating a _routes.json. If done correctly, you could do it in a single Functions request

HHello, I’m Allie!It depends on how good you/your framework is at generating a _routes.json. If do...

simpson•9/1/23, 7:42 PM

i'm using next-on-pages, I don't think it generates a _routes.json file

simpson•9/1/23, 7:53 PM

is there documentation on _routes.json?

Ssimpson i'm using next-on-pages, I don't think it generates a _routes.json file

Hello, I’m Allie!•9/1/23, 7:54 PM

Oh yeah, I remember chatting with one of the people that works on NOP, and they said something along the lines of implementing _routes.json might break how Next’s routing works, even for static assets

Ssimpson is there documentation on _routes.json?

Hello, I’m Allie!•9/1/23, 7:55 PM

Docs

Routing · Cloudflare Pages docs

Functions utilize file-based routing. Your /functions directory structure determines the designated routes that your Functions will run on. You can …

James•9/1/23, 7:58 PM

Yeah so I secretly added support for

_routes.json

_routes.json

a while ago but it's an area that I didn't add documentation about because, well, it should be reserved for advanced use cases where people absolutely know what they're doing and that excluding a file won't cause issues. e.g., favicon.ico would be safe to put in _routes.json, but the problem would be when people try to put actual routes in it - that would most likely lead to notable issues.

simpson•9/2/23, 1:37 AM

I moved all of our static assets within our public folder to a new subfolder and added a wildcard pattern (/static/*) and so far it seems to work perfect

Ricky U•9/2/23, 4:22 PM

how would i install a npm dependency for a pages function? i.e stripe

Ricky U•9/2/23, 5:12 PM

can find anywhere in the pages functions docs where i can install depdencies : https://developers.cloudflare.com/pages/platform/functions/local-development/

kian•9/2/23, 5:14 PM

Same as any other JS project

kian•9/2/23, 5:14 PM

Install it with a package manager of choice & import it in your Functions files

Erisa•9/2/23, 7:56 PM

Yeah, you can

export async function onRequestPost(ctx) {

export async function onRequestPost(ctx) {

Erisa•9/2/23, 7:57 PM

Documented here https://developers.cloudflare.com/pages/platform/functions/api-reference/

VVillage And it won't invoke the Function at all on a GET, just route right through to st...

Erisa•9/2/23, 8:05 PM

Correct, it wont invoke the function for GETs if you do that

EErisa Correct, it wont invoke the function for GETs if you do that

Hello, I’m Allie!•9/2/23, 9:17 PM

It does still bill you though, right?

Hello, I’m Allie!•9/2/23, 9:18 PM

Since routes are by URL, not by method

Ricky U•9/3/23, 3:27 AM

@kian in a /fuctions folders i have all the endpoints like helloworld.js, so im guessing your saying i npm ini the entire functions folder? and import xx from 'xxx' -- cf pages still says cannot find module xxx.

Ricky U•9/3/23, 4:47 AM

get this error when calling the stripe module :

12:43:50.447    ✘ [ERROR] Could not resolve "stripe"
12:43:50.447    
12:43:50.447        checkout.js:4:19:
12:43:50.447          4 │ import Stripe from 'stripe';
12:43:50.448            ╵                    ~~~~~~~~
12:43:50.448    
12:43:50.448      You can mark the path "stripe" as external to exclude it from the bundle, which will remove this error.
12:43:50.448    
12:43:50.448    
12:43:50.450    ✘ [ERROR] Build failed with 1 error:
12:43:50.451    
12:43:50.451      checkout.js:4:19: ERROR: Could not resolve "stripe"

12:43:50.447    ✘ [ERROR] Could not resolve "stripe"
12:43:50.447    
12:43:50.447        checkout.js:4:19:
12:43:50.447          4 │ import Stripe from 'stripe';
12:43:50.448            ╵                    ~~~~~~~~
12:43:50.448    
12:43:50.448      You can mark the path "stripe" as external to exclude it from the bundle, which will remove this error.
12:43:50.448    
12:43:50.448    
12:43:50.450    ✘ [ERROR] Build failed with 1 error:
12:43:50.451    
12:43:50.451      checkout.js:4:19: ERROR: Could not resolve "stripe"

emvh•9/8/23, 7:49 AM

I'm using

wrangler pages deploy

wrangler pages deploy

to deploy static files and Pages Functions. I would like to deploy only the Pages Functions, without deploying the static files. I.e. I'm using

wrangler pages deploy ./build-output ...

wrangler pages deploy ./build-output ...

, which deploys the static files from

./build-output

./build-output

and also deploys

./functions

./functions

by the file-based routing convention.

So, can I use

wrangler pages deploy

wrangler pages deploy

to deploy only the pages functions? If I have an empty directory with only the functions directory, would wrangler pages deploy know to upload the functions but not delete the static files already uploaded?

For context: I'm migrating a Pages project to use other hosting of the static files because of 20K file limit, but would like to keep deploying the Pages Functions

12:43:50.447 ✘ [ERROR] Could not resolve "stripe" 12:43:50.447 12:43:50.447 checkout.js:4:19: 12:43:50.447 4 │ import Stripe from 'stripe'; 12:43:50.448 ╵ ~~~~~~~~ 12:43:50.448 12:43:50.448 You can mark the path "stripe" as external to exclude it from the bundle, which will remove this error. 12:43:50.448 12:43:50.448 12:43:50.450 ✘ [ERROR] Build failed with 1 error: 12:43:50.451 12:43:50.451 checkout.js:4:19: ERROR: Could not resolve "stripe"

It kind of does though, if you work on it locally you can deploy the worker with wrangler and I beli

Similar Threads

Similar Threads

Similar Threads