next-on-pages is not perfect and does have it's drawbacks and issues, but performance wise in theory

D

DarioOP•3/20/24, 11:31 PM

(including the API routes of course)

P

Pat Branchaud•3/20/24, 11:42 PM

That’s music to my ears

T

thanhle•3/21/24, 4:24 AM

Hello there. Is the smart placement work on next-on-pages yet?

J

James•3/21/24, 9:25 AM

smart placement is pretty broken with Pages in general at the moment

DDario next-on-pages is not perfect and does have it's drawbacks and issues, but perfor...

P

Pepijn•3/21/24, 9:34 AM

Hi Dario, could you elaborate on the existing drawbacks and issues? Just starting with next on pages and seems to run fine for us, but before making a switch from Vercel with big projects, want to know the ins-and-outs

JJames smart placement is pretty broken with Pages in general at the moment

T

thanhle•3/21/24, 12:48 PM

But it still works well with Workers. Is it correct?. i am planning use next-on-pages for deploy my nextjs app and use CloudFlare Workers for API route with smart placement. what do you recommend about this setup?

JJames smart placement is pretty broken with Pages in general at the moment

T

thanhle•3/21/24, 1:04 PM

You mean this is the Pages Functions?

J

juanferreras•3/21/24, 9:18 PM

we've been adopting next-on-pages recently and it's been working really, really great (kudos to Dario/James/any other contributors I might be missing!)

(on a somewhat similar note to the messages above) I did want to know if either of you had any methods to reliably profile timings in Cloudflare workers – we were surprised to see that:

const t0 = Date.now();
const data = env.KV.get(key);
const t1 = Date.now();

const t0 = Date.now();
const data = env.KV.get(key);
const t1 = Date.now();

seemed to be reporting

XXX ms

XXX ms

in lab conditions even on cache hits (where in a plain worker we see

XX ms

XX ms

_. Then we realized it wasn't KV but rather the first IO we had (and with the CF Workers security measures, we understand we could be measuring things before that I/O that just wait for the I/O to tick?)

Tthanhle But it still works well with Workers. Is it correct?. i am planning use next-on-...

J

James•3/22/24, 6:30 PM

I'm not sure about workers because I don't use Workers, I just know that Smart Placement can cause internal errors with Pages. You can try your setup though, I'm not sure if it only happens with Pages functions or if it also happens with static assets

L

Logan•3/22/24, 11:36 PM

I have a question. If we were to deploy a server side NextJS app to pages, is there a list of originating IP addresses that app would communicate with or a way to get a list of IPs from our deployment that can be whitelisted on another system we have?

LLogan I have a question. If we were to deploy a server side NextJS app to pages, is th...

J

JohnDotAwesome•3/23/24, 12:15 AM

Someone correct me if I'm wrong, but the IP's of outgoing requests from Workers ought to match Cloudflare's ips's https://cloudflare.com/ips but just because a request is coming from that IP doesn't mean it's legitimate traffic. There's some good info here https://news.ycombinator.com/item?id=26690388

IP Ranges | Cloudflare

This page is intended to be the definitive source of Cloudflare’s current IP ranges.

kentonv

Hi, I'm the tech lead of Cloudflare Workers.This article contains several misunderstandings.If a Cloudflare customer has configured their origin server to respond only to Cloudflare IPs, then they MUST also verify that the "Host" header on any request actually matches their domain name. If they do not verify the Host header, then anyone can sign...

Hacker News

•

4/4/21, 3:47 PM

JJohnDotAwesome Someone correct me if I'm wrong, but the IP's of outgoing requests from Workers ...

L

Logan•3/23/24, 12:25 AM

If that is the case, that is awesome. Will wait on any anti-confirmation.

JJames I'm not sure about workers because I don't use Workers, I just know that Smart P...

T

thanhle•3/23/24, 1:41 AM

thank you so much for the infor James

Q

quisi.do•3/23/24, 9:00 AM

Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is this channel for SSR? I wasn't aware of Pages offering SSR. If so, is there any documentation about this?

Qquisi.do Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is ...

H

Hello, I’m Allie!•3/23/24, 9:20 AM

Yes, it is. next-on-pages adapts Next’s Serverless code to make it compatible with Pages

Qquisi.do Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is ...

D

DarioOP•3/23/24, 11:30 AM

Yes, it's documented here

https://developers.cloudflare.com/pages/framework-guides/nextjs/
(specifically for Next.js)

Cloudflare Docs

Deploy a Next.js site · Cloudflare Pages docs

React framework for building full-stack web applications.

P

Pat Branchaud•3/23/24, 2:47 PM

Hey, I’m trying to find a solution for hosting with next-on-pages a full slug translation i18n (ex: fr/blogue, en/blog). Looking for a solution without the use of a middleware like amannn/next-intl does, the only viable I found right now is svobik7/next-roots copying folders on build. Any other ideas or examples your guys are aware of? 3 days of searching now and It seems complicated..

J

James•3/23/24, 5:08 PM

You could maybe use next.config.js rewrites, but that could end up being pretty laborious

0

0xwei_hup•3/23/24, 6:13 PM

hey guyss, anyone here has a nextjs 14 using drizzle and cloudflare d1 github repo that i can look at? just trying to see and learn how other people doing it

J

Jeff•3/23/24, 6:22 PM

Hey guys, how might I troubleshoot an: "Error code: 1000" error for a next on pages project? It uses pages router, and the /api route throws status code 403, with a plaintext response of "error code: 1000". Works locally with wrangler pages dev. The logs do not make it to the log tail, so seems its before my app

J

Jeff•3/23/24, 6:25 PM

I see online that 1000 implies I'm pointing to a cloudflare ip in some way, but this is just a pages.dev/api/ route, so im not sure how

J

Jeff•3/23/24, 7:30 PM

It seems that passing of specific

x-vercel-*

x-vercel-*

or

cf-*

cf-*

headers was triggering this. The headers were coming from

next/headers

next/headers

and may have gotten mixed around by all the trpc context switching going on in the T3stack boilerplate. If anyone runs into this I just wrote code to strip any of those headers being sent on UI requests

E

Erisa•3/24/24, 1:49 PM

It was likely the cf-connecting-ip header

M

mr nooli•3/24/24, 4:26 PM

Hey, I've got a next-on-pages project, and I'm running into Error 1101 and the CF dashboard is showing:

"exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1711296914762
    }
  ],

"exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1711296914762
    }
  ],

"exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1711296914762
    }
  ],

"exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1711296914762
    }
  ],

How do I go about debugging this? As I can run this locally with

npm run dev

npm run dev

(idk if

npx wrangler dev

npx wrangler dev

is the right command, if so I'm running into a bunch of 500 errors that I really can't figure out)

J

James•3/24/24, 4:29 PM

are you using the latest version (1.11.0)?

M

mr nooli•3/24/24, 4:30 PM

yep

M

mr nooli•3/24/24, 4:31 PM

if

wrangler dev

wrangler dev

is the right command this is the error I'm getting:

[wrangler:inf] Ready on http://localhost:8787
[wrangler:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at Object.fetch (file:///Volumes/[...]/.vercel/output/static/_worker.js/index.js:40:40336)

[wrangler:inf] Ready on http://localhost:8787
[wrangler:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at Object.fetch (file:///Volumes/[...]/.vercel/output/static/_worker.js/index.js:40:40336)

[wrangler:inf] Ready on http://localhost:8787
[wrangler:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at Object.fetch (file:///Volumes/[...]/.vercel/output/static/_worker.js/index.js:40:40336)

[wrangler:inf] Ready on http://localhost:8787
[wrangler:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at Object.fetch (file:///Volumes/[...]/.vercel/output/static/_worker.js/index.js:40:40336)

Mmr nooli if `wrangler dev` is the right command this is the error I'm getting: ``` [wran...

H

Hello, I’m Allie!•3/24/24, 4:33 PM

It should be

wrangler pages dev

wrangler pages dev

instead

H

Hello, I’m Allie!•3/24/24, 4:33 PM

Since it is Pages

M

mr nooli•3/24/24, 4:35 PM

ah, doing that gives me:

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

M

mr nooli•3/24/24, 4:38 PM

oh wait that was cos the port was in use, forcing a port just gives me a 404 error

M

mr nooli•3/24/24, 4:38 PM

do I need to include a

node-compat

node-compat

somewhere?

J

James•3/24/24, 4:41 PM

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

J

James•3/24/24, 4:41 PM

muscle memory

M

mr nooli•3/24/24, 4:43 PM

legend, how do I load my environment variables from that

J

James•3/24/24, 4:45 PM

I think wrangler uses .dev.vars instead of .env, which drives me absolutely crazy

M

mr nooli•3/24/24, 4:45 PM

M

mr nooli•3/24/24, 4:46 PM

oh it's workign

M

mr nooli•3/24/24, 4:46 PM

no errors locally

M

mr nooli•3/24/24, 4:46 PM

J

James•3/24/24, 4:47 PM

lol perfect

M

mr nooli•3/24/24, 4:47 PM

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

(?) could this be the issue?

J

James•3/24/24, 4:48 PM

nah that's an annoying warning because of a response.clone in react i think it is

J

James•3/24/24, 4:48 PM

or it's a request.clone that they do somewhere, can't remember. i just recall dario found the line in react where it comes from

M

mr nooli•3/24/24, 4:49 PM

hmmmm any idea what the 1101 error could be from/how to debug it?

J

James•3/24/24, 4:49 PM

that would suggest an error is being thrown IIRC, you could tail a deployment and see if there's any useful logs?

M

mr nooli•3/24/24, 4:49 PM

what's the command for that?

J

James•3/24/24, 4:50 PM

npx wrangler pages deployment tail

npx wrangler pages deployment tail

M

mr nooli•3/24/24, 4:51 PM

I can't login (?)

M

mr nooli•3/24/24, 4:52 PM

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

next-on-pages is not perfect and does have it's drawbacks and issues, but performance wise in theory

Similar Threads

Similar Threads

Similar Threads