Or restructure into a monorepo
Or restructure into a monorepo
Rhey
Ri am unable to deploy next app
RGitHub
next-on-pages environment related information System: Platform: win32 Arch: x64 Version: Windows 10 Pro CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Memory: 32 GB Shell: C:\Program Files\G...
Rfacing this issue
CIt is recommended you use Linux or MacOS
As per the docs - link
As per the docs - link
@cloudflare/next-on-pages can be run on Linux, Mac OS and Windows but its usage under the latter is discouraged as we've noticed that one of the CLI's dependencies, the Vercel CLI (used to build the Next.js application) seems not to work reliably on Windows. If you need to run @cloudflare/next-on-pages on Windows we advise you to run it under the Windows Subsystem for Linux.
Awe have deployed our website in pages and it is working fine in pages dynamic URL, After mapping a custom domain to the dynamic URL. website static page is getting loaded, but the dynamic pages are not getting loaded.
CDo you mean dynamic routes ?
What I understand is:
What I understand is:
- Your next js app works in production with a url like this
, right?https://project-name.pages.dev/ - You added a custom domain for this project - cool
https://project-name.pages.dev/project-name.com
SHi there, I would like to add _middleware.js for the new next.js project. Could someone help to explain where should I put this file?
Ayes, i mention my url
pages url: dev-poorvika-ecom.pages.dev
custom domain: https://dev-cf.poorvika.com/
kindly check this url
pages url: dev-poorvika-ecom.pages.dev
custom domain: https://dev-cf.poorvika.com/
kindly check this url
Best Online Shopping for Mobiles, Laptops, Home Appliances & more in India
CHm, I don't know what the issue might be here without access to the code. Please try doing the following
- Check if the production build works locally
- Try creating a minimal reproducible example and post a question on pages-help
Ahttps://github.com/cloudflare/next-on-pages/blob/c2b173ce89c82dd1566474191691bb5d62d01e67/packages/next-on-pages/templates/_worker.js/utils/fetch.ts#L20 <-- somehow i have an outbound POST request thats getting cached and its not making a lot of sense
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
Rhey, did you find any solution or you are trying with restructuring
VHaven’t found anything nope
VProbably going to end up having to restructure into a Pages app, cron worker, and shared utilities
HThis. Pages itself does not support any handlers other than fetch, so Crons have to be in a separate Worker
VSigh aw well
VThanks!
VFor some reason R2 just flat out doesn't work anymore. My production code (same code) works just fine, but when I attempt to pass in Headers objects to portions of r2.get or object.writeHttpMetadata, as is supported or at least was, it errors out with cannot stringify arbitrary non-POJO's. Then, if I remove all usage of that, the instant r2.get returns an object the body is read already so it's impossible for me to actually read what's inside the object and do anything with it.
VIs this a known issue or something new or?
VLike R2 just flat out doesn't work locally anymore which isn't the greatest
SgenerateStaticParams
Jit tells you in the next sentence how you can use it
SNow I get it. Dang. And btw does
This is my
/apiThis is my
api/revalidate/route.ts
Nadd export const runtime = 'edge'
GIs it possible to turn off minification somehow? Attempting to port an existing next app over to cloudflare pages but we're running into some issues and it's not clear where this is originating from
Nyes for every page/api that should run on the edge
Napi should always run on the edge
IActually, just adding it to the root layout worked fine for us, but we don't use API endpoints but a binding to an actual worker.
IThis error means that somewhere within your SSR code you're probably passing a relative path to an URL constructor
J--disable-worker-minificationWhere do you pass this to? Google shows 0 results searching for this option
GAh sourcegraph is a lifesaver, found it: https://sourcegraph.com/github.com/cloudflare/next-on-pages/-/blob/packages/next-on-pages/src/cli.ts?L47
GAre there any tricks to catch uncaught errors, ideally globally somewhere? Some errors don't come with stack traces at all, which makes it a nightmare to track down where they might come from
Jinternal errors means something went wrong inside cloudflare pages/workers
GYeah, but most likely because of some bad input? With the non-descript error + no stack trace it's a needle in a haystack problem. We dumped a ton of try/catch into our app and eventually found something. In a worker it's a bit easier to debug as you can just wrap at the entrypoint and catch any uncaught errors
Jits something going legitimately wrong on cloudflare's end if you get just 'Error: internal error', you will normally need an employee to check if they can see something for the deployment id
GHmm okay, is there anything we can check if this happens locally running with wrangler/workerd?
GWe're just running this locally while trying to get it working, haven't setup any deployments yet
Jmaybe something throwing an exception in workerd locally
GNothing visible in the output. I'll hit up our cloudflare support contacts to see if we can get someone from CF to take a look. Thanks for your help!
RHas anyone done work to optimize the bundle size of their Next.js build?
RWith the App Router, it seems that pretty much everything gets bundled together, regardless of whether it's client or server side.
SHello everyone, Do you guys build nextjs pages project using nx project.json?
FHey does someone have a good idea for how to set up your API_URL environment variables?
I am currently setting them in my wrangler.toml file and then using getRequestContext().env.API_URL to access them. This works both locally and in deployment for my functions in api/route/..
However when i try to access my apis at ”api/route” (using fetch in my page.tsx component) it works locally but seems to break in production:/
Thanks for any respons!
I am currently setting them in my wrangler.toml file and then using getRequestContext().env.API_URL to access them. This works both locally and in deployment for my functions in api/route/..
However when i try to access my apis at ”api/route” (using fetch in my page.tsx component) it works locally but seems to break in production:/
Thanks for any respons!
AIs there any way to make some built-in environment variables public?
I'm trying to access
I've looked into
UPDATE: The solution is using the env config option to map them to
I'm trying to access
CF_PAGES_BRANCHCF_PAGES_URLNEXT_PUBLIC_*I've looked into
getRequestContextUPDATE: The solution is using the env config option to map them to
NEXT_PUBLIC_*