Looks like there's a good amount of trimming I'd need to do to get this project able to run on the e
Looks like there's a good amount of trimming I'd need to do to get this project able to run on the edge
Nwas pretty easy for me
NSome of my configs rely on
node:urlnode:fsmaybe if you have some unsupported dependencies you might have to find workarounds
NHow do you find out which package is incompatible?
LHi! Does anyone have experience or a guide on how to migrate from Next on Pages to a barebones "Next on Workers" implementation? Logs and Cron requirements are making things a bit impossible to continue.
JNot sure I understand what you mean by 'next on workers'. Our CLI generates a worker which is deployed as part of your pages deployment. if you wanted, you could modify the worker we generate if that's the kind of thing you want to do?
NKV or Durable Objects seem good for that
NKV is very cheap
Nso it should not be that expensive just to check a value in kv
Nonce the guy exceeds the limit you don't have to write anymore
N5$/million is not that much
Nand cloudflare cdn already protects you before workers
Nso max 5 write per day per user on kv
Nyou can go up to 200,000 users with the free writes in the paid plan
Nbut like if you want to scale you will have to pay
Nyou can't scale while having 5$/month hosting
Nuse DO then
Nits 0.15$/million
NCloudflare 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 …
JD1 is also an option if you wanted
LHey @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
So my question is essentially around how to deploy my app that uses
Pages support is substantially less than Workers on Cloudflare, for example, it does not support
logpush (https://community.cloudflare.com/t/logpush-support/597684) or cron. Discovered this when I tried to add logpush=true to the wrangler.yaml file.So my question is essentially around how to deploy my app that uses
next-on-pageslogpush JIt'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
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
DCloudflare 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
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
Contribute to divrawat/One-Blog development by creating an account on GitHub.
Vright....
Mhow to fix this error
message.txt7.47KB
Wenv var -
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
YARN_VERSIONv2 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
Jdo you have a favicon.ico inside app dir? if so, move it to a public dir instead
Vyeah but why would it out of the blue fail deployment.
Vwhen i never updated any package
VCF doing changes it prod that breaks our app?
JYou 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
JIf 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
. So you should put it in the public dir instead of the app dir
Mthis fixed it for me. but just fyi the standard npm create cloudflare@latest framework next will fail build until you make this change.