Not sure I understand what you mean by 'next on workers'. Our CLI generates a worker which is deploy

AAnay-208 I've a nextjs app hosted with pages. Now, I've an api route which basically sen...

N

Nob•7/8/24, 5:03 PM

KV or Durable Objects seem good for that

AAnay-208 read the last line. On price estimation, it seemed to be too high

N

Nob•7/8/24, 5:04 PM

KV is very cheap

N

Nob•7/8/24, 5:04 PM

so it should not be that expensive just to check a value in kv

AAnay-208 I’ll be writing on every read

N

Nob•7/8/24, 5:06 PM

once the guy exceeds the limit you don't have to write anymore

N

Nob•7/8/24, 5:09 PM

5$/million is not that much

N

Nob•7/8/24, 5:09 PM

and cloudflare cdn already protects you before workers

N

Nob•7/8/24, 5:12 PM

so max 5 write per day per user on kv

AAnay-208 And I’m obv looking to scale

N

Nob•7/8/24, 5:13 PM

you can go up to 200,000 users with the free writes in the paid plan

N

Nob•7/8/24, 5:14 PM

but like if you want to scale you will have to pay

N

Nob•7/8/24, 5:14 PM

you can't scale while having 5$/month hosting

AAnay-208 Yes, I can surely do that, but $5.5/million is just too much

N

Nob•7/8/24, 5:16 PM

use DO then

N

Nob•7/8/24, 5:17 PM

its 0.15$/million

AAnay-208 I’ll check it out soon

N

Nob•7/8/24, 5:17 PM

https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/

Cloudflare Docs

Build a rate limiter · Cloudflare Durable Objects docs

This example shows how to build a rate limiter using Durable Objects and Workers that can be used to protect upstream resources, including third-party …

J

JamesOP•7/8/24, 6:18 PM

D1 is also an option if you wanted

JJames Not sure I understand what you mean by 'next on workers'. Our CLI generates a wo...

L

LH•7/8/24, 6:22 PM

Hey @James ! I havent double checked, but I'm assuming it generates Pages functions, not pure Workers (because it's hosted as Pages, not Workers on Cloudflare). Is that the case?

Pages support is substantially less than Workers on Cloudflare, for example, it does not support

logpush

logpush

logpush

logpush (https://community.cloudflare.com/t/logpush-support/597684) or

cron

cron

cron

cron. Discovered this when I tried to add

logpush=true

logpush=true

logpush=true

logpush=true to the

wrangler.yaml

wrangler.yaml

wrangler.yaml

wrangler.yaml file.

So my question is essentially around how to deploy my app that uses

next-on-pages

next-on-pages

directly as a Workers app on CF, instead of a Pages app so that I can use

logpush

logpush

logpush

logpush

LLH Hey <@94508156243161088> ! I havent double checked, but I'm assuming it generate...

J

JamesOP•7/8/24, 6:30 PM

It's what Pages functions refers to as an advanced mode, although it's actually just a regular worker way of doing things.

If you wanted to deploy your nextjs app as a completely normal worker (which doesnt sound like the best idea to me), you'll need to come up with a way to manage how you would still expose assets to env.ASSETS.fetch('/{assetPath}'). You'll also end up getting billed a lot more since the _next/static files will all have worker invocations, and you're going to be paying for either KV or R2 to store and serve all your site's assets.

Doesn't sound very fun. You're essentially going to be operating what used to be referred to as a Workers Sites deployment. Something Cloudflare have been trying to discourage and get away from people doing, and to instead use Pages.

You could still have a worker for crons that is separate to your nextjs app. You could also modify the worker file created by next-on-pages to capture logs and dispatch them to a queue or something if you wanted

D

divrawat•7/9/24, 7:51 AM

Cloudflare Pages invoking functions on request to static assets in Next.js - I have deployed a fully static next.js website (pages directory of next.js) to cloudflare pages and I have added _routes.json file to root of my project excluding static assets from function invocation.

But still my Dashboard is showing the requests made , but it is a fully static site.

Is functions directory creating compalsory since all my website is static. Here is my github repo - https://github.com/divrawat/One-Blog

GitHub

GitHub - divrawat/One-Blog

Contribute to divrawat/One-Blog development by creating an account on GitHub.

V

villainy•7/9/24, 1:48 PM

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️      The following routes were not configured to run with the Edge Runtime:
⚡️        - /favicon.ico

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️      The following routes were not configured to run with the Edge Runtime:
⚡️        - /favicon.ico

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️      The following routes were not configured to run with the Edge Runtime:
⚡️        - /favicon.ico

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️      The following routes were not configured to run with the Edge Runtime:
⚡️        - /favicon.ico

right....

M

Muzzamil•7/9/24, 1:57 PM

how to fix this error

message.txt7.47KB

W

Walshy•7/9/24, 2:50 PM

env var -

YARN_VERSION

YARN_VERSION

YARN_VERSION

YARN_VERSION = 1

v2 defaults to yarn v3 which tries to change the lock file from v1 and then violates it's own rule against modifying the lock file

Vvillainy ```console ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project...

J

JamesOP•7/9/24, 4:07 PM

do you have a favicon.ico inside app dir? if so, move it to a public dir instead

JJames do you have a favicon.ico inside app dir? if so, move it to a public dir instead

V

villainy•7/9/24, 4:42 PM

yeah but why would it out of the blue fail deployment.

V

villainy•7/9/24, 4:43 PM

when i never updated any package

V

villainy•7/9/24, 4:43 PM

CF doing changes it prod that breaks our app?

J

JamesOP•7/9/24, 4:49 PM

You know we don't generate that function. It's the Vercel/Next CLIs that wrongly generate an ISR function for a favicon.ico file placed inside the app directory instead of just moving it to the static assets directory

J

JamesOP•7/9/24, 4:50 PM

If they didn't, it wouldn't be an issue and it would be treated like the static asset that it is

. So you should put it in the public dir instead of the app dir

JJames do you have a favicon.ico inside app dir? if so, move it to a public dir instead

M

Matthew•7/9/24, 11:07 PM

this fixed it for me. but just fyi the standard npm create cloudflare@latest framework next will fail build until you make this change.

J

JamesOP•7/10/24, 12:11 AM

ugh

J

JamesOP•7/10/24, 12:11 AM

i just saw someone made an issue for it as well and it's because of a new vercel cli release

J

JamesOP•7/10/24, 12:11 AM

will make a pr to try and account for it

C

Cat Socks•7/10/24, 1:26 AM

import { EmailMessage } from "cloudflare:email";
import { createMimeMessage } from "mimetext";

export default {
 async fetch(request, env) {
   const msg = createMimeMessage();
   msg.setSender({ name: "GPT-4", addr: "<SENDER>@example.com" });
   msg.setRecipient("<RECIPIENT>@example.com");
   msg.setSubject("An email generated in a worker");
   msg.addMessage({
       contentType: 'text/plain',
       data: `Congratulations, you just sent an email from a worker.`
   });

   var message = new EmailMessage(
     "<SENDER>@example.com",
     "<RECIPIENT>@example.com",
     msg.asRaw()
   );
   try {
     await env.SEB.send(message);
   } catch (e) {
     return new Response(e.message);
   }

   return new Response("Hello Send Email World!");
 },
};

import { EmailMessage } from "cloudflare:email";
import { createMimeMessage } from "mimetext";

export default {
 async fetch(request, env) {
   const msg = createMimeMessage();
   msg.setSender({ name: "GPT-4", addr: "<SENDER>@example.com" });
   msg.setRecipient("<RECIPIENT>@example.com");
   msg.setSubject("An email generated in a worker");
   msg.addMessage({
       contentType: 'text/plain',
       data: `Congratulations, you just sent an email from a worker.`
   });

   var message = new EmailMessage(
     "<SENDER>@example.com",
     "<RECIPIENT>@example.com",
     msg.asRaw()
   );
   try {
     await env.SEB.send(message);
   } catch (e) {
     return new Response(e.message);
   }

   return new Response("Hello Send Email World!");
 },
};

import { EmailMessage } from "cloudflare:email";
import { createMimeMessage } from "mimetext";

export default {
 async fetch(request, env) {
   const msg = createMimeMessage();
   msg.setSender({ name: "GPT-4", addr: "<SENDER>@example.com" });
   msg.setRecipient("<RECIPIENT>@example.com");
   msg.setSubject("An email generated in a worker");
   msg.addMessage({
       contentType: 'text/plain',
       data: `Congratulations, you just sent an email from a worker.`
   });

   var message = new EmailMessage(
     "<SENDER>@example.com",
     "<RECIPIENT>@example.com",
     msg.asRaw()
   );
   try {
     await env.SEB.send(message);
   } catch (e) {
     return new Response(e.message);
   }

   return new Response("Hello Send Email World!");
 },
};

import { EmailMessage } from "cloudflare:email";
import { createMimeMessage } from "mimetext";

export default {
 async fetch(request, env) {
   const msg = createMimeMessage();
   msg.setSender({ name: "GPT-4", addr: "<SENDER>@example.com" });
   msg.setRecipient("<RECIPIENT>@example.com");
   msg.setSubject("An email generated in a worker");
   msg.addMessage({
       contentType: 'text/plain',
       data: `Congratulations, you just sent an email from a worker.`
   });

   var message = new EmailMessage(
     "<SENDER>@example.com",
     "<RECIPIENT>@example.com",
     msg.asRaw()
   );
   try {
     await env.SEB.send(message);
   } catch (e) {
     return new Response(e.message);
   }

   return new Response("Hello Send Email World!");
 },
};

Has anyone been able to bind email workers to an next on pages api route?

P

powermikee1•7/10/24, 3:04 AM

Hi guys has anyone managed to get durable objects running with next pages?

First i get an error mentioning migrations. Then it requires a worker name which is usually auto generated.

Any help would be awesome.

D

Donnager•7/10/24, 3:58 PM

n00b Q: when navigating

workers.api.error.script_too_large

workers.api.error.script_too_large

workers.api.error.script_too_large

workers.api.error.script_too_large the idea is that the

_worker.js

_worker.js

~~file~~ *folder in

output/static/

output/static/

output/static/

output/static/ should be less than 1mib (free) or less than how much for paid? the workers documentation says 10mib, and in pages it says 25mib but i think thats referencing static assets only. in discord i have seen conversations referencing 5mib

is it safest to check the

_worker.js

_worker.js

folder or to check the

/output/static/

/output/static/

/output/static/

/output/static/ folder itself (minus what is excluded from

_routes.json

_routes.json

?

Not sure I understand what you mean by 'next on workers'. Our CLI generates a worker which is deploy

Similar Threads

Similar Threads

Similar Threads