is the variable plain text or secret? if it's plain text, if you convert it to secret and re-deploy,
is the variable plain text or secret? if it's plain text, if you convert it to secret and re-deploy, does it work?
CIt’s in secret
GHi all, my Server Actions are hitting the error
This ReadableStream is disturbed (has already been read from), and cannot be used as a body.I'd understand why this would/could happen in a Route Handler where we have access to
Request
JSounds like a potential bug
MHey what are some good solutions to reducing the bundle size? I've got maybe a small to medium sized dashboard in NextJS and we just hit the 25mb limit and now we are pretty stuck. Support didn't really help or tell me anything obvious.
I'm pretty stuck right now, it's rights on the limit. I'd easily pay the Pro plan price if that doubled or 4x that limit. I don't know what else I can do in the next config file to reduce imports, I've tried heaps with transpile and optimizePackageImports: [] to not avail
I'm pretty stuck right now, it's rights on the limit. I'd easily pay the Pro plan price if that doubled or 4x that limit. I don't know what else I can do in the next config file to reduce imports, I've tried heaps with transpile and optimizePackageImports: [] to not avail
SWould love help with same on how we can build and upload the files to cloudflare?
PI guess they are referring to their docs but not really helpful, yeah https://developers.cloudflare.com/pages/platform/limits/#file-size
Ndepends really on what kind of data you're bundling. Do you have more insights on what your app does and what the big sized stuff is?
DIs this being caused alone by the "
A similar conversation conversation was made around general-discussions which happened just about 2 hours before your message here, it sounds like you shouldn't be uploading the contents from "
Do you have a "
/webpack/A similar conversation conversation was made around general-discussions which happened just about 2 hours before your message here, it sounds like you shouldn't be uploading the contents from "
/webpack/Do you have a "
dist/build/
CWill react cache work on next-on-pages?
It is a server side function to cache results. Used in react server components.
It is a server side function to cache results. Used in react server components.
Cmy nextjs app works fine when running locally and on preview as well but when deployed it only shows "application error happened on client side" and theres nothing in console either
How do i debug this?
How do i debug this?
Tdid u manage to make this work? im trying to make a next on pages project with bun on a workspace, but it keeps using npm i
MSet bun as your package manager in your package.json and add bun install to your build step
Toh ok. thanks for replying
JBarrel files are normally a big offender
EHi, random question, is
__NEXT_INCREMENTAL_CACHE_IPC_KEY sensitive? It says "key" and looks random so I imagine it could be... but I'm not sure what it would be for. I don't see it documented anywhere but I see it in process.env
EActually, I assumed this was a Cloudflare Pages thing, but there's nothing indicating it is. It's probably just an internal next thing, so I'm asking in the wrong place.
PUsing Nextjs and defining route endpoints, I realized all these route endpoints need to be using the edge runtime. I can't seem to use the nodejs runtime like with workers when using next-on-pages. Is this correct? Can someone confirm? It seems like I need to separate my frontend and backend so next-on-pages mainly loads the nextjs frontend app and server actions whereas my backend needs to be written in my case in honojs and as a cloudflare worker deployment OUTSIDE of nextjs route endpoints (otherwise next-on-pages will try to build the route endpoints on pages and it'll require edge runtime). Is that correct?
Ptldr; cloudflare next-on-pages 100% needs edge runtime. There is no way to put nextjs route endpoints on cloudflare workers using nodejs runtime when using next-on-pages right?
JCorrect, next-on-pages only works with either prerendered routes or edge-runtime routes
RAnyone have a good way to make my preview deployments use a different .env file? So .env.production for production and .env.staging or .env.preview for preview?
VWe have just released @opennextjs/cloudflare 0.3.0 
Thanks to everybody who made that possible, from cloudflare and the community.
Kudos to @Dario @petebd @conico974 @James and everybody that submitted PRs and reported feeback
The docs have been updated for the released at https://opennext.js.org/cloudflare, including a migration guide from 0.2.
0.3 supports middleware, loading .env* files, ... It includes quite a few bug fixes and improvements.
Please test this new release and report feedback!
Happy holiday season
Check the Open Next discord for more info about Next on Workers https://discord.gg/opennextjs
Thanks to everybody who made that possible, from cloudflare and the community.
Kudos to @Dario @petebd @conico974 @James and everybody that submitted PRs and reported feeback
The docs have been updated for the released at https://opennext.js.org/cloudflare, including a migration guide from 0.2.
0.3 supports middleware, loading .env* files, ... It includes quite a few bug fixes and improvements.
Please test this new release and report feedback!
Happy holiday season
Check the Open Next discord for more info about Next on Workers https://discord.gg/opennextjs
NHello, i am looking for help,
I am making a website builder, and I made a "publish" button that deploys the users website into cloudflare but I am having issues.
Basically when I press Publish, I have a big function that turns my node tree of the builder into a next js project (creates component, creates app folder, src etc..), then I need it to automatically deploy that project to a new Pages or Worker. How can i proceed ? Thank you!
I am making a website builder, and I made a "publish" button that deploys the users website into cloudflare but I am having issues.
Basically when I press Publish, I have a big function that turns my node tree of the builder into a next js project (creates component, creates app folder, src etc..), then I need it to automatically deploy that project to a new Pages or Worker. How can i proceed ? Thank you!
NI have succeeded with wrangler, but I found that I can only upload a next project to a Pages is that true ? I cannot do it onto a Worker ?
DI successfully uploaded an AngularJS (yes, the really old one) project both with wrangler and drag/drop in the UI. I don't know anything about next.js. I had to build first and upload the output. Sounds like you might be trying to upload the source files?
NI succeeded . I build the next js internally then outputted the build files
KHello, will dynamic routes be supported in the near future?
BCongrats on the release!
Is there a v1 / version 1 roadmap and ETA for opennextjs-cloudflare?
Is there a v1 / version 1 roadmap and ETA for opennextjs-cloudflare?
VThe plan is to add more tests early January.
This will give us visibility on what remains to be done before we cut v1 - we will then publish an ETA.
Hopefully only a few weeks away.
This will give us visibility on what remains to be done before we cut v1 - we will then publish an ETA.
Hopefully only a few weeks away.
CHow do I make the image assets (static assets - inside public directory) load faster?
If you check my website - https://sendbetter.co
If you check my website - https://sendbetter.co
- you can see it took a second to load the hero images.
HFor me, the images load pretty quickly. Per Page-Speed Insights, you could resize images for different display sizes, and convert to more efficient formats, but your biggest issue seems to just be that your initial page load is slow
HThat and, you may be running your Functions in front of your assets?
CI am using next-on-pages. I am not running workers directly and I don't know how next-js logic translate to cf worker logic.
So I really don't know what you mean by "running your Functions in front of your assets". Sorry, can you tell me what you mean?
So I really don't know what you mean by "running your Functions in front of your assets". Sorry, can you tell me what you mean?
CTy, will add smaller assets and use the right sized image for different display sizes
HBasically, you can tell Pages to skip Next and serve your assets directly. Afaik for Next specifically, this can break pre-rendered pages, but for assets, it should
be fine
be fine
COh, how do I do that?
Cnext-on-pages automatically creates
(if this is what you mean)
link to docs - https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/static-assets/
_routes.json(if this is what you mean)
link to docs - https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/static-assets/
Cloudflare Docs
When you use a JavaScript framework like Next.js on Cloudflare Pages, the framework adapter (ex: @cloudflare/next-on-pages) automatically generates a _routes.json file, which defines specific paths of your app's static assets. This file tells Cloudflare, for these paths, don't run the Worker, you can just serve the static asset on this path (an ...
HYeah, then you should be good on that front
HCouldn’t remember whether Next did it automatically or not
PHi good afternoon, I wanted to know if there's a way we can cache node_modules and node as well for builds.
I have a NextJs app which I'm deploying as static. I have enabled build cache but that only optimizing next build and still installs deps on each build.
Thank you!
I have a NextJs app which I'm deploying as static. I have enabled build cache but that only optimizing next build and still installs deps on each build.
Thank you!
Sdoes next on pages allow you to have a /functions dir in the project root as well?
Ldoes a request to one of my static pages count against my worker invocations?
HNope, you have to use Next’s API Routes
HYes, as next-on-pages requires itself to be run on all Pages, regardless of whether they are pre-rendered or not
HLalright
Lty
Lis it possible to use customer domains with next-on-pages, and if so, how do i do it? like if i want to allow people to register their own domains to be used for my multi-tenant nextjs project
Sman thats a bummer okay i guess i make a seperate repo
