Cloudflare Developers•2y ago

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

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

conqr ᯅ•2/21/24, 11:40 PM

an env variable

DarioOP•2/21/24, 11:40 PM

could it be that in

process.env

process.env

you had used the same variable name for something else?

conqr ᯅ•2/21/24, 11:41 PM

I think what happened is the nextjs dev server loaded

.env

.env

into

process.env

process.env

DarioOP•2/21/24, 11:41 PM

yeah, it does that

conqr ᯅ•2/21/24, 11:41 PM

I had it in

.env

.env

too

DarioOP•2/21/24, 11:42 PM

ok yeah that makes sense then

X•2/21/24, 11:43 PM

DarioOP•2/21/24, 11:49 PM

@conqr ᯅ I'll improve our error message to remind developers to use the edge runtime

, hopefully this can help avoid developers confusion/frustration: https://github.com/cloudflare/next-on-pages/issues/674

GitHub

[⚡ Feature]: Make local `getRequestContext` remind developers to us...

We've recently made the getRequestContext local error more helpful, reminding people to set up the dev platform: next-on-pages/packages/next-on-pages/src/api/getRequestContext.ts Lines 52 to 61...

conqr ᯅ•2/21/24, 11:50 PM

Still learning next, so I forget this quite often

DarioOP•2/21/24, 11:50 PM

yeah.... but it's not your fault, it's the problem of Next.js always defaulting to node.js

DarioOP•2/21/24, 11:51 PM

some versions back they did allow you to globally specify the edge runtime and have it applied to all your routes!

DarioOP•2/21/24, 11:51 PM

I so wish they didn't remove that

JJames Not sure what you mean by caching correctly? You typically don't cache pages whe...

chubbspeterson•2/22/24, 12:38 AM

You don't cache pages when you do SSR? That doesn't make sense to me.

Take for example a site with 10s of thousands of pages...it wouldn't be efficient to statically generate them all, so they would be generated server side and the response would be cached at the edge. This way the next request comes from cache vs generating it again

conqr ᯅ•2/22/24, 6:33 AM

What would this be caused by?

Screenshot_2024-02-21_at_10.32.47_PM.png

conqr ᯅ•2/22/24, 6:51 AM

Seems like NPM package htmlrewriter caused the issue :(

bigansh•2/22/24, 9:29 AM

the site is deployed, but i am getting 404 error. this is the url: https://testing.client-6ek.pages.dev/

bigansh•2/22/24, 9:30 AM

bigansh•2/22/24, 10:29 AM

ok, so i deleted the project and did it again, i got the worker limit error

bigansh•2/22/24, 10:30 AM

but when i ran this command ❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test

it showed me this size. not sure what the issue here is

Bbigansh but when i ran this command `❯ yarn wrangler deploy .vercel/output/static/_worke...

Befus•2/22/24, 10:36 AM

Did you set the nodjs_compat flag?

BBefus Did you set the nodjs_compat flag?

bigansh•2/22/24, 10:36 AM

yes

Bbigansh but when i ran this command `❯ yarn wrangler deploy .vercel/output/static/_worke...

DarioOP•2/22/24, 10:59 AM

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_hooksnode: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)

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 };

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

Similar Threads