so anything that uses `fs` does not work within cloudflare pages?
so anything that uses
fs
Jcorrect, next.js won't actually let you build if you're trying to use fs and using the edge runtime.
Ftysm!
WWould it be a problem if I want to deploy a site that uses NextJs and Python?
VI'm starting a greenfield project and am wondering if it makes sense to use api routes in nextjs when i could just use the functions directory which seems to have better first class support with bindings and cloudflare compatible libraries. Does anyone have an opinion on this?
H
Jhow would you use python in nextjs?
JHave you tried creating your table? If this is when deployed, make sure you run your migrations against the remote DB. If this is local, make sure you run your migrations against your local db
WPython as backend
WWell, not the whole backend
WBut part of it
JBut Next.js needs to run in a javascript environment so I'm not sure how that could work if you wanted to deploy them to the same worker. They'd need to be separate
WWell uhh
WIt’s not like the whole NextJs project will be Python
WOnly a small folder
WAnd it works as an API
Wwhich means I fetch the data from the Python files to the js framework
Jyeah not sure how you'd run that
PMy next js website works with pages.dev domain but it's not working in custom domain what the hell
P
KI'm trying to user D1 with drizzle orm in next js, currently using next auth 5, and using drizzle adapter for that.. How to get the DB instance during build?
export const {
handlers: { GET, POST },
auth,
signIn,
signOut,
} = NextAuth({
adapter: DrizzleAdapter(getDBInstance()),
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_CLIENT_ID ?? "",
clientSecret: process.env.GOOGLE_CLIENT_SECRET ?? "",
}),
],
});
This is method to get db instance
export const getDBInstance = () => {
console.log("getRequestContext", getRequestContext);
const DB = getRequestContext().env.AI_FORM_GENERATOR_DB;
return drizzle(DB, { schema });
};
How to get access to Binding variable AI_FORM_GENERATOR_DB during build process?
export const {
handlers: { GET, POST },
auth,
signIn,
signOut,
} = NextAuth({
adapter: DrizzleAdapter(getDBInstance()),
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_CLIENT_ID ?? "",
clientSecret: process.env.GOOGLE_CLIENT_SECRET ?? "",
}),
],
});
This is method to get db instance
export const getDBInstance = () => {
console.log("getRequestContext", getRequestContext);
const DB = getRequestContext().env.AI_FORM_GENERATOR_DB;
return drizzle(DB, { schema });
};
How to get access to Binding variable AI_FORM_GENERATOR_DB during build process?
KYou can't, the build process is just a Ubuntu container separate to Workers/Pages. You'd need to hit the D1 REST API or make your own Worker that serves as an API.
HClarifying from the thread in No Access, they appear to be calling this within the scope of a Next route, but for some reason it still tries to call it at build time
KIts works in dev environment, but when I try build and deploy it fails on this point
Ksrc/types/cloudflare-env.ts
src/db/db-connection.ts
src/auth.js
src/db/db-connection.ts
src/auth.js
KK
Janyone got reacthottoast source
Nprocess.env.HYPERDRIVE.connectionString can't get value in next-on-page ,any recommendations ？ 
RAnyone ever have this problem with next on pages?
RCopy and pasted config and site from another deployment that works fine, and I'm getting this
Vhow would i add things like durable objects to my next-on-pages project? would i need to setup have a separate folder for workers that is deployed separately? could i get some guidance on what that would look like?
Jnot sure, I haven't tried it
KHi, guys!
How can I deploy nextjs app to cloudflare ipfs?
How can I deploy nextjs app to cloudflare ipfs?
K
L-> Just throwing it out there, my honest feedback on my cloudlare experience.
I tried to go full cloudflare for my project https://fullwindcss.com/
I learnt it's called cutting edge because it will cut you
I went with
Maybe a mitigation is to use classic workers (not edge runtime nextjs api routes) to handle the backend? Hope Stripe works there.
I would have loved to have a great experience on cloudflare but we're not there yet.
I tried to go full cloudflare for my project https://fullwindcss.com/
I learnt it's called cutting edge because it will cut you
I went with
- nextjs (next-on-pages) app router, server components, server actions, edge runtime
- drizzle + D1 for database
- all the static parts work fine.
if you have a blog it will be great and free up to 1mb for your site's bundle which is turned into a worker function. I was just over 1mb and had to switch to workers paid for 5$ a month (which is very fair) - you get the benefits of serverless, the site can handle usage spikes without you having to worry about anything (non issue during the product hunt launch).
- Next Auth on Drizzle + D1 + edge runtime has been a challenge (but manageable). Examples in the repo are much nicer than the documentation
- Stripe payments that work in dev fail most of the time in prod. I tried to move from server actions to webhooks, still doesn't work and basically impossible to debug.
- Error logs can be super cryptic, like "Error: The script will never generate a response."
- you can't use cloudflare pages' sentry plug-in in a next-on-pages app, so no error reporting.
- Log retention is not possible at the moment. You can either stream from your terminal or from the web dashboard. Good luck debugging prod in these conditions.
- The team at cloudflare isn't super dedicated to next-on-pages. It's not a core product the way it is at Vercel. Github issues can stay unanswered for 2 weeks, and sometimes for ever. The Discord server is more active.
Maybe a mitigation is to use classic workers (not edge runtime nextjs api routes) to handle the backend? Hope Stripe works there.
I would have loved to have a great experience on cloudflare but we're not there yet.
LMy repo is private but happy to jump on a call and show you
JError logs can be super cryptic, like "Error: The script will never generate a response."This would be a bug that generally you should open an issue on our repo for. Another user raised an issue a couple days ago about this that we have fixed related to the fetch patch which may also solve the problem for you - I'll shoot dario a message about making a release.
Github issues can stay unanswered for 2 weeksPlease feel free to bump an issue or add additional context if it's also affecting you.
Ljust re-read, I meant the next auth repo, examples folder https://github.com/nextauthjs/next-auth/tree/main/apps/examples/nextjs
I think I also took inspiration from another repo, this one I think https://github.com/yongyi520/cloudflare-nextjs-d1-error
still happy to show you how I did it
I think I also took inspiration from another repo, this one I think https://github.com/yongyi520/cloudflare-nextjs-d1-error
still happy to show you how I did it
Jit's due to some logic in the react server code which is what i'm trying to hack around in that pr, although we're seeing weird behaviour with the e2es which i need to spend some time looking into
Ji believe it's a relatively recent thing (past few months)
Jif you wanted, you could even try using the prerelease in the PR to build with
JHey there, looking for some help regarding some nasty and close to impossible to debug Error 1101 "Error: The script will never generate a response." errors.
We are developing quite a simple NextJS app that's bringing some APIs together. In particular we use Auth0 as an Auth Provider and then SWR to fetch data from multiple REST routes. Classic Customer Portal solution. It's still in the PoC level so we didn't even leverage KV or D1 yet. What drives us crazy is the fact that the same code runs perfectly fine on Vercel but constantly hits the 1101 on CF Pages.
We tried to run
If anyone have some ways on how to demistify this generic error ... I am highly greatful.
For context: We had some issues in one of the dependencies of the project before. That was when we first deployed it to Vercel. Vercel gave us a perfect clear logging output regarding the issue. We fixed that library to make it Edge compatible. Not the app runs fine on Vercel but still not on CF Pages.
We have auto Github deployments configured on both platforms and use the same config (ENV vars) on both. So code and config are identical. It's just the platform that difers ...
We are developing quite a simple NextJS app that's bringing some APIs together. In particular we use Auth0 as an Auth Provider and then SWR to fetch data from multiple REST routes. Classic Customer Portal solution. It's still in the PoC level so we didn't even leverage KV or D1 yet. What drives us crazy is the fact that the same code runs perfectly fine on Vercel but constantly hits the 1101 on CF Pages.
We tried to run
wrangler pages dev locally in hope that it might give us some more information but it simply won't work on our Windows machines.If anyone have some ways on how to demistify this generic error ... I am highly greatful.
For context: We had some issues in one of the dependencies of the project before. That was when we first deployed it to Vercel. Vercel gave us a perfect clear logging output regarding the issue. We fixed that library to make it Edge compatible. Not the app runs fine on Vercel but still not on CF Pages.
We have auto Github deployments configured on both platforms and use the same config (ENV vars) on both. So code and config are identical. It's just the platform that difers ...
Jthe prerelease link in the pr -
we don't have a canary. the beta release has a recursive fetch patch bugfix but nothing for the cache property
https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/8953244999/npm-package-next-on-pages-771.we don't have a canary. the beta release has a recursive fetch patch bugfix but nothing for the cache property
