thanks - maybe that is is my issue - I dont have the local one created. Is there any way to connect
thanks - maybe that is is my issue - I dont have the local one created. Is there any way to connect to the remote one while working locally?
Dusing just
you probably already saw this but the internal github doc:
that says it generates from miniflare, so i feel like you may not need it locally, but can't remember how i set it up last time hehe
next devyou probably already saw this but the internal github doc:
that says it generates from miniflare, so i feel like you may not need it locally, but can't remember how i set it up last time hehe
SI'm having some trouble with exceptions getting logged in Sentry and I think it is related to how Cloudflare Pages is bundling the application, but I'm not certain. basically if an error occurs locally, then it gets logged correctly as an exception to Sentry. but when deployed on Cloudflare Pages, it is getting logged as a console error message and not an exception.
we are still using NextJS 13 and the old version of next-on-pages
I tried adding a custom _error.js file like here but then it gave an error when building and said I need to specify that as an edge route, which I don't think is what I'm wanting to do?
we are still using NextJS 13 and the old version of next-on-pages
I tried adding a custom _error.js file like here but then it gave an error when building and said I need to specify that as an edge route, which I don't think is what I'm wanting to do?
JgetInitialProps can probably run on the server i imagine, so it will try to generate an node.js function I would assume. It's also a legacy API so your mileage may vary.
I don't know how sentry works, but the error it's logging could be the one that we catch and then log via console.error after running an edge function, but I'm not sure how sentry works so unsure if that's what's intercepting
I don't know how sentry works, but the error it's logging could be the one that we catch and then log via console.error after running an edge function, but I'm not sure how sentry works so unsure if that's what's intercepting
DHello, I'm new to cloudflare and want to contact with someone using cloudflare worker with next js application can anyone help me?! ~ty.
JCan you write your question please?
Sthe exceptions that should be getting logged are happening in the browser, but they seem to get swallowed up 
DMy question is Do we use next api routes If we're creating next js application with cloudflare or we are using workers?!
JYes you use next.js API routes if you want to deploy a full stack next.js app to cloudflare
JWould something like react-error-boundary help here perhaps?
DWhat about workers what's the use case of it in Next js application, sorry If it seems basic questions but as I said I'm totally new to cloudflare
JWhen you use
@cloudflare/next-on-pages
Di need to use Cloudflare API routes nested of next API routes, how to do it and access my end point inside functions directory
JThe functions directory doesn't work with next-on-pages as we generate our own worker for your route. You should be using next.js API routes if you're using next-on-pages
Dok, should i add export const runtime = "edge" in the top level of my routes in next API routes to make it run on the edge servers
DYes, every api routes must have a export const runtime = "edge" in order to make it work on Cloudflare pages
MDoes the Wrangler cli work in next-on-pages?
I create a project with next and cloudflare,
Added the wrangler.toml file in the root after installing Wrangler cli and trying to run the local host development server but it doesn't.
I use the command
Wrangler pages dev
I create a project with next and cloudflare,
Added the wrangler.toml file in the root after installing Wrangler cli and trying to run the local host development server but it doesn't.
I use the command
Wrangler pages dev
Mso in the next-on-pages we don't use the Functions directory for API routes nested we use Next API routes but adding at the top level
export const runtime="edge"
export const runtime="edge"
DYes, functions directory doesn't work when using next-on-pages.
DIt uses vercel to build your app and generates a _worker.js based on your routes if I am not wrong.
MNo I need to use cloudflare pages not vercel..
Explain it more please
Explain it more please
MYou mean next-on-pages use vercel to build the app ?
MSo where is the cloudflare role in it ??
Just hosting ??
I tried to understand it from the documentation but I feel something is missing.
Just hosting ??
I tried to understand it from the documentation but I feel something is missing.
Dnext-on-pages uses vercel-cli to build next.js application for the edge runtime and then do some extra tasks internally to make it compatible with Cloudflare pages.
Mso you mean when I use
npm create cloudflare@latest -- --framework=next
It uses vercel to build the project and make it compatible with cloudflare ??
npm create cloudflare@latest -- --framework=next
It uses vercel to build the project and make it compatible with cloudflare ??
DYou can read more here:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
MDoes wrangler work with 'next-on-pages' ??
or should I use the next localhost development server as usual
or should I use the next localhost development server as usual
HIt does work, in the sense that you can build your project then run it with Wrangler. But, if you want live changes to show up, run it with the
nextwhen i'm trying to start development server with wrangler "wrangler pages dev" it gives me an error of static directory doesn't specified but I ensured that i build the application before and exported it's static to an Out directory and specified the out directory in the wrangler.toml file,
so can any one explain that to me?
or should I use next development server "npm run dev" nested of using wrangler?
so can any one explain that to me?
or should I use next development server "npm run dev" nested of using wrangler?
HYou need to provide the output directory to the dev command, like so:
Dstill have an error
HRename the
wrangler.tomlI renamed it but still same error
HHow about if you delete it?
Dit gave me error of missing compatability date, should i add it to the command?
Danother thing, where to define my bindings?
DIn the command itself
MWhat command I don't get it
DA binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …
DFor
https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev
next devhttps://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
MYes, thanks
MMHow to access the KV storage with this worker from the next project.
HCheck out the example: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#example
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
HThey are actually all one Worker, though if you can add telemetry to the entire thing is outside my area of expertise
HAs for the config thing, I believe they are working on something better atm, plus the merger of Workers and Pages
HOr well, each deployment is its own Worker, but all routes within a deployment are bundled into a single Worker
JThere is only one entry point for the worker in the _worker.js directory. Feel free to wrap that entry point post-build if you want. I would advise against trying to wrap individual route functions or webpack chunks though, but wrapping the worker entrypoint should be perfectly fine.
