you should use `wrangler pages deploy` not `wrangler deploy`, can you try that? 🙂

you should use

wrangler pages deploy

wrangler pages deploy

not

wrangler deploy

wrangler deploy

, can you try that?

DDario you should use `wrangler pages deploy` not `wrangler deploy`, can you try that? ...

bigansh•2/22/24, 11:00 AM

actually i was following your guide. but ok

bigansh•2/22/24, 11:00 AM

https://github.com/cloudflare/next-on-pages/issues/523 this link took me to this page. https://developers.cloudflare.com/workers/platform/limits/#worker-size hence the confusion

DDario you should use `wrangler pages deploy` not `wrangler deploy`, can you try that? ...

bigansh•2/22/24, 11:01 AM

got this error.

Bbigansh https://github.com/cloudflare/next-on-pages/issues/523 this link took me to this...

DarioOP•2/22/24, 11:02 AM

no sorry.... you are going to face the worker-size limit no matter what you use

I was just saying that regarding the last error (the

node:async_hooks

node:async_hooks

one), it's likely due to using the wrong command

Bbigansh actually i was following your guide. but ok

DarioOP•2/22/24, 11:03 AM

do we tell users to run

wrangler deploy

wrangler deploy

somewhere?

if so please let me know as that needs amending!

DDario do we tell users to run `wrangler deploy` somewhere? 😲 if so please let me know...

bigansh•2/22/24, 11:04 AM

check the second link. it tells user to run wrangler deploy with dryrun to check the size

bigansh•2/22/24, 11:04 AM

Bbigansh check the second link. it tells user to run wrangler deploy with dryrun to check...

DarioOP•2/22/24, 11:05 AM

yes... but that's

Workers

Workers

documentation, not

Pages

Pages

documentation....

but yeah I guess we should have the same information in the

Pages

Pages

documentation

DDario yes... but that's `Workers` documentation, not `Pages` documentation.... but ye...

bigansh•2/22/24, 11:06 AM

yes. worker limit for pages is an extremely common issue. i have pinged this chat 100s of times with same request coz it is very arbritary.

bigansh•2/22/24, 11:06 AM

but the issue at hand right now, how do i check my worker size for the nextjs site?

Bbigansh got this error.

DarioOP•2/22/24, 11:06 AM

can you remove the cli arguments? (since they are not supported in

wrangler pages deploy

wrangler pages deploy

)

DDario can you remove the cli arguments? (since they are not supported in `wrangler pag...

bigansh•2/22/24, 11:08 AM

that will deploy the website. i dont want to do that. just want to check the size

Bbigansh but the issue at hand right now, how do i check my worker size for the nextjs si...

DarioOP•2/22/24, 11:09 AM

basically the only thing (as far as I remember) is to build the worker

@cloudflare/next-on-pages

@cloudflare/next-on-pages

, then take the

.vercel/output/static/_worker.js

.vercel/output/static/_worker.js

manually gzip it and check the gzip's output size

DDario basically the only thing (as far as I remember) is to build the worker `@cloudfl...

bigansh•2/22/24, 11:13 AM

ok, so its 1.5 mb

bigansh•2/22/24, 11:13 AM

oof

DarioOP•2/22/24, 11:23 AM

with the paid tier the limit goes up to 10 MB by the way

DDario weird.... what were you trying to access?

Befus•2/22/24, 11:30 AM

How do you get the env in a non request?
Example in my case:

import { getRequestContext } from "@cloudflare/next-on-pages";
import { drizzle } from "drizzle-orm/d1";

export const runtime = 'edge';

const { env } = getRequestContext();

const db = drizzle(env.DB);



export { db };

import { getRequestContext } from "@cloudflare/next-on-pages";
import { drizzle } from "drizzle-orm/d1";

export const runtime = 'edge';

const { env } = getRequestContext();

const db = drizzle(env.DB);



export { db };

BBefus How do you get the env in a non request? Example in my case: ```tsx import { get...

DarioOP•2/22/24, 11:33 AM

How do you get the env in a non request?

all your source code is run inside a Cloudflare worker request handler, so you're basically always handling a request (i.e. you should always be able to run

getRequestContext

getRequestContext

)

DDario > How do you get the env in a non request? all your source code is run inside a ...

Befus•2/22/24, 11:34 AM

Yea thats what I thought aswell just getting this error when building:
Error: Error: failed to retrieve the Cloudflare request context
12:31:26.281 ▲ at u (/opt/buildhome/repo/.next/server/app/api/auth/[...nextauth]/route.js:352:2658)
12:31:26.281 ▲ at 73355 (/opt/buildhome/repo/.next/server/app/api/auth/[...nextauth]/route.js:347:27369)
12:31:26.281 ▲ at webpack_require (/opt/buildhome/repo/.next/server/edge-runtime-webpack.js:25:42)
12:31:26.281 ▲ at /opt/buildhome/repo/.next/server/app/api/auth/[...nextauth]/route.js:381:4970
12:31:26.281 ▲ at webpackJsonpCallback (/opt/buildhome/repo/.next/server/edge-runtime-webpack.js:208:39)
12:31:26.281 ▲ at /opt/buildhome/repo/.next/server/app/api/auth/[...nextauth]/route.js:1:51
12:31:26.281 ▲ at Script.runInContext (node:vm:135:12)
12:31:26.282 ▲ at runInContext (node:vm:283:6)
12:31:26.282 ▲ at evaluateInContext (/opt/buildhome/repo/node_modules/next/dist/server/web/sandbox/context.js:377:38)
12:31:26.282 ▲ at getRuntimeContext (/opt/buildhome/repo/node_modules/next/dist/server/web/sandbox/sandbox.js:70:9)
12:31:26.282 ▲ > Build error occurred
12:31:26.284 ▲ Error: Failed to collect page data for /api/auth/[...nextauth]
12:31:26.284 ▲ at /opt/buildhome/repo/node_modules/next/dist/build/utils.js:1258:15
12:31:26.284 ▲ at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
12:31:26.284 ▲ type: 'Error'

BBefus How do you get the env in a non request? Example in my case: ```tsx import { get...

DarioOP•2/22/24, 11:34 AM

The code you're sharing seems fine to me... I'd need to see how you're using it to see what might be going wrong

PS: also we do have a current bug that prevents

drizzle

drizzle

from working

DDario The code you're sharing seems fine to me... I'd need to see how you're using it ...

Befus•2/22/24, 11:35 AM

Fully prevents drizzle from working? Or certain functions?

BBefus Yea thats what I thought aswell just getting this error when building: Error: Er...

DarioOP•2/22/24, 11:38 AM

ah yeah I see... that means that that code is getting run by Next.js during the build process to pre-render something....

is that file always only imported in routes using the edge runtime? (because if it is I would assume that Next.js should not error here

)

this might be an actual Next.js + next-on-pages bug/limitation...

(I'd have to look into it further...) one thing you could do as a workaround would be to use

getOptionalRequestContext

getOptionalRequestContext

in that case and checking if you do or not get the request context

BBefus Fully prevents drizzle from working? Or certain functions?

DarioOP•2/22/24, 11:40 AM

fully... I think.... I am not too sure to be honest

anyways the bug that most likely causes it not to work has been fixed in our runtime (https://github.com/cloudflare/workerd/pull/1665/) so hopefully it should work fine after the next runtime release (in a week or two)

Befus•2/22/24, 11:41 AM

I managed to get next-on-pages -> drizzle -> d1 working with next auth for creating my users, so it was working fine for me? Weird

But when I was using process.env it worked on production but not locally and now that I am using env and getRequestContext it works locally but not in production lol

DarioOP•2/22/24, 11:43 AM

I managed to get next-on-pages -> drizzle -> d1 working with next auth for creating my users, so it was working fine for me? Weird

ok, maybe sometimes/in some cases it works.... I really don't know to be honest

(but if it works for you great!

)

DarioOP•2/22/24, 11:45 AM

But when I was using process.env it worked on production but not locally and now that I am using env and getRequestContext it works locally but not in production lol

I had this exact conversation yesterday

is that you're using variables in a

.env

.env

file? (those are only available/populated by

next dev

next dev

but not by

wrangler pages dev

wrangler pages dev

nor in the deployed application)

DDario fully... I _think_.... I am not too sure to be honest 😓 anyways the bug that ...

Befus•2/22/24, 11:45 AM

I see that this PR has been merged, maybe it is already fixed or is it not in prod yet?

BBefus I see that this PR has been merged, maybe it is already fixed or is it not in pr...

DarioOP•2/22/24, 11:46 AM

no, I'm sure it is not in prod as they haven't released it yet (https://github.com/cloudflare/workerd/releases)

DDario > But when I was using process.env it worked on production but not locally and n...

Befus•2/22/24, 11:48 AM

My .env file atm has nothing in it related to bindings, well when it worked using process.env I was using this:

env.d.ts
declare global {
  namespace NodeJS {
    interface ProcessEnv {
      DB: D1Database;
      DOCUMENTS_BUCKET: R2Bucket;
    }
  }
}

export {}

env.d.ts
declare global {
  namespace NodeJS {
    interface ProcessEnv {
      DB: D1Database;
      DOCUMENTS_BUCKET: R2Bucket;
    }
  }
}

export {}

Now: (working local but not in production)

env.d.ts
interface CloudflareEnv {
  DB: D1Database;
  DOCUMENTS_BUCKET: R2Bucket;
}

env.d.ts
interface CloudflareEnv {
  DB: D1Database;
  DOCUMENTS_BUCKET: R2Bucket;
}

DarioOP•2/22/24, 11:50 AM

My .env file atm has nothing in it related to bindings

weird

the

env.d.ts

env.d.ts

file is only for providing the correct types, it doesn't effect what it made availabe or not (also I thought the issue could have been string bindings, not actual bindings, the latter doesn't really have anything to do with

.env

.env

files)

BBefus My .env file atm has nothing in it related to bindings, well when it worked usin...

DarioOP•2/22/24, 11:51 AM

so right now you have an application and in it you can do

process.env.DB

process.env.DB

but if you do

getRequestContext().env.DB

getRequestContext().env.DB

you can't access your binding?

DarioOP•2/22/24, 11:52 AM

@Befus PS: I just noticed this issue on github: https://github.com/cloudflare/next-on-pages/issues/675 I'm not sure if that's you, anyways I just thought of pointing it out to you

, I'll look into that as soon as I can

GitHub

How to access your process.env.DB D1 dev binding outside of a Route...

If I understand correctly, version 1.9.0 removes the possibility to access your process.env.DB dev binding outside of a Route Handler. When using the v5/beta version of next-auth / auth.js, you nee...

DDario <@262845927616806923> PS: I just noticed this issue on github: https://github.co...

Befus•2/22/24, 11:53 AM

Lol thats not me but the exact same issue lol

DDario so right now you have an application and in it you can do `process.env.DB` but i...

Befus•2/22/24, 11:54 AM

process.env.DB doesn't work atm because i am only using env.d.ts which has the cloudflareEnv inside of it alongside with getRequestContext
This works locally perfectly fine but on production/preview it fails

BBefus process.env.DB doesn't work atm because i am only using env.d.ts which has the c...

DarioOP•2/22/24, 11:58 AM

as I said

env.d.ts

env.d.ts

doesn't matter too much, in your code you can do:

(process.env as any).DB

(process.env as any).DB

and see if it contains the binding

DDario as I said `env.d.ts` doesn't matter too much, in your code you can do: `(process...

Befus•2/22/24, 12:02 PM

Build seems successful when using this:

import { drizzle } from "drizzle-orm/d1";

export const runtime = "edge";

const db = drizzle((process.env as any).DB);

export { db };

import { drizzle } from "drizzle-orm/d1";

export const runtime = "edge";

const db = drizzle((process.env as any).DB);

export { db };

Befus•2/22/24, 12:02 PM

Gonna test if it actually works

DDario as I said `env.d.ts` doesn't matter too much, in your code you can do: `(process...

Befus•2/22/24, 12:10 PM

Seems to be working fine now

DarioOP•2/22/24, 12:16 PM

what if you try using

getOptionalRequestContext

getOptionalRequestContext

instead of

process.env

process.env

gui.ohm•2/22/24, 12:20 PM

Is it expected that static assets return an ETag but routes api url don't? I've migrated my app to next-on-pages from a pre-existing expressjs app and that's a key difference. I wonder if I should manually add the Etag computation on my routes or if that would be discouraged to do so? Is there a setting that would enable so in next-on-pages or cloudflare's config?

bigansh•2/22/24, 12:24 PM

ok so we upgraded and the site is now live. but it is slow like slow. like the page doesnt even open. and we have to refresh multiple times. when i run it locally using the wrangler command, it is crazy fast. not sure what is going on here

bigansh•2/22/24, 12:24 PM

i get this error a lot.

bigansh•2/22/24, 12:24 PM

ezzat•2/22/24, 5:55 PM

Hey everyone!

I recently added a _headers file to my Next.js application's public directory to set some headers, but it doesn't seem to be working as expected.

I'm curious to know how this affects the entire application. Does it impact all routes, pages, or any other aspects I should be aware of?

Thanks in advance for any insights you can provide!