Cloudflare Developers•17mo ago

Thanks, looks great, will definitely give it a go

Ffletcher3 Thanks, looks great, will definitely give it a go

Firu•8/20/24, 12:03 PM

sure thing! lemme know if you find any pitfalls or pain points i might've missed

ItsWendell•8/20/24, 12:38 PM

Axiom actually also supports a lot of the OpenTelemetry standard, I also haven't got vercel/otel to work yet, if someone did, that would be awesome so I can send those into axiom too.

IItsWendell Hard to see what is happening here when we don't see how the pages are generated...

sean.h•8/20/24, 1:07 PM

Sure, been on other things the last few days.

job-logs.txt284.59KB

neoney•8/22/24, 5:09 PM

getRequestContext doesn't seem to have hyperdrive?

neoney•8/22/24, 5:09 PM

it smissing

neoney•8/22/24, 5:10 PM

and when it starts

neoney•8/22/24, 5:10 PM

Found a non-empty WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING variable for binding. Hyperdrive will connect to this database during local development.

hunter.jia•8/23/24, 4:03 AM

i deploy monorepo to pages and successful,but the access path is not available
Do you guys know the reason why

hunter.jia•8/23/24, 4:04 AM

the monorepo is about next

Max•8/23/24, 9:03 PM

I‘m using Next Requests and next-on-pages.
Which IP is used when calling an external (free+publicly available) API?
I assume it’s Cloudflare‘s IP, isn’t it?
I‘m asking because I‘m afraid of hitting the rate limit of that external API.

D Trombett•8/23/24, 9:48 PM

well, yeah, the request is sent from Cloudflare servers

D Trombett•8/23/24, 9:49 PM

it shouldn't be always the same tho, as it depends on the region and the server

Sheng•8/23/24, 10:40 PM

Is there any way that we can use single .env file for environment variables instead of duplicated variables in .env, .dev.vars, and the wrangler.toml file?

James•8/24/24, 11:54 AM

unfortunately wrangler refuses to respect the industry standard of using .env

Bonadio•8/24/24, 5:34 PM

Hi, trying to create a Nextjs project with "npm install --save-dev @Cloudflare/next-on-pages" results in 5 vulnerabilities (1 low, 2 moderate, 2 high), running npm audit fix does not solve the problem. Any ideas?

whizzy•8/25/24, 12:44 PM

my d1 is not working on local machine, gives me error of table not found, using with pages, and d1 binding
I also gave it this value in wrangler.toml but doesnt seem to be working

preview_database_id = "DATABASE"

preview_database_id = "DATABASE"

whizzy•8/25/24, 12:45 PM

can anyone help me setup locally, just give me couple of steps

D Trombett•8/25/24, 2:31 PM

might be obvious but... did you create the table locally?

D Trombett•8/25/24, 2:32 PM

afaik local database doesn't inherit anything from the real one

whizzy•8/26/24, 2:50 PM

why to create local one? what I want to test the remote d1 on local ?

Wwhizzy why to create local one? what I want to test the remote d1 on local ?

Hard@Work•8/26/24, 2:58 PM

You can't. next-on-pages only interacts with local DBs

whizzy•8/26/24, 3:00 PM

daaamn, was this supposed to be a feature ? why ?

sean.h•8/27/24, 1:53 PM

I think I've figured out what's helping our next on pages worker bundle go over 25MiB.
We have 1256 static pages and 24 edge function routes.
The static routes are all output to a prerender-manifest.json (this is normal NextJS behaviour).

The next-on-pages deploy process copies the contents of this file into each edge function js file as a __PRERENDER_MANIFEST variable.
Our prerender-manifest.json comes in at 781KiB, so for me we've got it duplicated 24 times and in theory only need 1 copy of this in the final worker that's generated.

Has anyone else come across this before I raise it as a bug/improvement on GitHub?

AA•8/27/24, 2:25 PM

any differences between 1.9.0 and 1.13.2 that would give me an "ReferenceError: XMLHttpRequest is not defined"

kstulgys•8/27/24, 2:25 PM

"Your Worker exceeded the size limit of 1 MiB"

How? I tried already quite a few thing in my my nextjs 14 app. This is the app:

export default function Home() {
  return null;
  // return <Client />;
}
// import Client from "./client";
// import dynamic from "next/dynamic";

// const Client = dynamic(() => import("./client").then((mod) => mod.Client), {
//   loading: () => <p>Loading...</p>,
// });

export default function Home() {
  return null;
  // return <Client />;
}
// import Client from "./client";
// import dynamic from "next/dynamic";

// const Client = dynamic(() => import("./client").then((mod) => mod.Client), {
//   loading: () => <p>Loading...</p>,
// });

AAA any differences between 1.9.0 and 1.13.2 that would give me an "ReferenceError: ...

AA•8/27/24, 2:38 PM

Going to try 1.12.1.. i wonder what version killed this

AA•8/27/24, 2:44 PM

yea 1.9.0 is the last version of next-on-pages i can use.. Tips for troubleshooting would be appreciated

AA•8/27/24, 2:51 PM

https://github.com/cloudflare/next-on-pages/releases/tag/%40cloudflare%2Fnext-on-pages%401.10.0 no obvious changes

GitHub

Release @cloudflare/next-on-pages@1.10.0 · cloudflare/next-on-pages

Minor Changes

739e2a7: make (no-op) caches available in dev mode
update setupDevPlatform to also add a caches object to the global scope
so that it can be used during development in a production-...

AAA any differences between 1.9.0 and 1.13.2 that would give me an "ReferenceError: ...

yuripave•8/27/24, 3:36 PM

Apparently the issue starts from 1.31.2 with the route scoping change, 1.31.1 should work without issue

Yyuripave Apparently the issue starts from 1.31.2 with the route scoping change, 1.31.1 s...

AA•8/27/24, 3:47 PM

I tried on 1.10.0 and had the same issue

AA•8/27/24, 8:04 PM

its not apparently obvious what the change was. i wonder if its a dep change..

AA•8/27/24, 8:05 PM

I think its probably an unintended interaction with graphql-request

Ssean.h I think I've figured out what's helping our next on pages worker bundle go over ...

James•8/28/24, 9:48 AM

hmm we dedupe some of these manifests but this might be a new one that we aren't accounting for, could you make an issue please

James•8/28/24, 9:48 AM

yeah your XMLHttpRequest problems sounds like an issue with one of your dependencies to me

JJames hmm we dedupe some of these manifests but this might be a new one that we aren't...

sean.h•8/28/24, 10:09 AM

Sure,

sean.h•8/29/24, 10:48 AM

For those that might want to track it, https://github.com/cloudflare/next-on-pages/issues/869

GitHub

[🐛 Bug]: __PRERENDER_MANIFEST duplication · Issue #869 · cloudflare...

next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030 CP...

jdruwe•8/29/24, 12:10 PM

"UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins" anyone else experienced that error locally when building? I have following import: 'import { randomUUID } from 'node:crypto';' as mentioned on: https://developers.cloudflare.com/workers/runtime-apis/nodejs. Am I doing something wrong?

James•8/30/24, 7:49 AM

Is that error coming when Next.js builds?

jdruwe•8/30/24, 10:58 AM

@James yes it is, it seems like it is a next spefific thing

jdruwe•8/30/24, 10:58 AM

@Anay-208 you can, you just need to import it from node:crypto -> https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/

Cloudflare Docs

Crypto | Cloudflare Workers docs

The node:crypto module provides cryptographic functionality that includes a set of wrappers for OpenSSL’s hash, HMAC, cipher, decipher, sign, and verify functions.

jdruwe•8/30/24, 11:45 AM

That's causing the build issue, they also discussed it internally at: https://github.com/replicate/replicate-javascript/issues/225 I am now using the web crypro api which should also work inside a worked as you said (still need to verify

)

GitHub

Reading from "node:crypto" is not handled by plugins · Issue #225 ·...

Environment: Node Version: 20.11.1 macOS: 14.2.1 next: 14.1.3 replicate: 0.28.1 I am getting Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugin...

James•8/30/24, 12:06 PM

yeah webcrypto should be fine

diffthanevery01•8/30/24, 1:32 PM

Hi, I have another question about Cloudflare Pages. Whenever I uploaded changes on Github to the appropriate branch it would automatically build the app and upload it to Pages, but for some time now (2 weeks) the app doesn't build, it stutters and hangs like that until timeout. When I do it manually using a command from the console, everything uploads nicely in 2-3 minutes (the app is on NextJS)

diffthanevery01•8/30/24, 1:32 PM

There is nothing in the logs, it just stutters at random times

export default function Home() { return null; // return <Client />; } // import Client from "./client"; // import dynamic from "next/dynamic"; // const Client = dynamic(() => import("./client").then((mod) => mod.Client), { // loading: () => <p>Loading...</p>, // });

Thanks, looks great, will definitely give it a go

Similar Threads