I would say no personally, simply because of the amount of unnecessary requests it causes
I would say no personally, simply because of the amount of unnecessary requests it causes
Ni created a custom link component that set prefetch=false automatically, idk why nextjs enabled it by default 
Nand I dont see a big difference in load time
Jthe cynical view would be more requests = more money
JI understand the benefits behind prefetching, but I don't understand the need to prefetch everything in the viewpoint. on hover, sure, but not the viewport.
Nyes but in nextjs you can either disable it completly (not even on hover) or enable for viewport
NI think they do that because they will get more money from vercel
JI never realised you couldn't have hover only. that sounds like a worthwhile feature to add
ZDoes that not go against the backwards compatibility philosophy of workers? Putting it somewhere other than the runtime because that allows for breaking changes seems to me like trying to exploit a "loophole" in the rules around backwards compatibility.
ZPlease correct me if I'm wrong
JI thought the plan was to get rid of the node_compat nonsense /shrug
ITechnical limitations are technical limitations but naming them similar sounding (and same meaning things) when they're different doesn't really sound like a technical limitation? 
Dagain, I totally totally agree 
historical reasons?!
historical reasons?!
Dmh.... well, the "somewhere other than the runtime" is wrangler, since that is a built time flag, and that is under semver... is that really a loophole? 
NHow do i test my api routes db calls from local development, like accessing kv from next dev
ZIt would require you to stick with old, unsupported, versions of wrangler if you want to make sure your worker keeps working as expected. The only reason I can see for not using compat dates is because you plan to break backwards compatibility at some point, and that feel very wrong to me in workers. While you are correct that this wouldn't technically violate the backwards compatibility guarantees (a change in this wouldn't be a change in the runtime, and deployed workers would keep working), it still doesn't sit right with me.
DDoes blob: fetch not work on next on pages?
Like:
The above works in development mode but doesn't work when using npx wrangler pages dev
Like:
The above works in development mode but doesn't work when using npx wrangler pages dev
DAlso, I think this is the reason why @vercel/og doesn't work with next-on-pages?
N@vercel/og works with next-on-pages
DI see... the way I see it is sort of like: we don't have a perfect solution, so, instead of adding to the runtime something half-baked/problematic right now (thus committing to it forever) let's find an intermediate solution that can help people out to some degree, best-effort like. That being the build time node_compat flag.
That does make sense to me.
Also people with much more knowledge in that area than me made the decision above (which I don't know how set in stone is to be honest), people who know the downsides and maintenance burden of adding such polyfills into the runtime, so I trust their judgment
, but if you want I am totally happy to pass your feedback along or see if I can connect you directly with them
That does make sense to me.
Also people with much more knowledge in that area than me made the decision above (which I don't know how set in stone is to be honest), people who know the downsides and maintenance burden of adding such polyfills into the runtime, so I trust their judgment
, but if you want I am totally happy to pass your feedback along or see if I can connect you directly with them 
Dyeah it should!
(
although there's a small bug that makes it potentially fail sometimes
as you can see near the bottom here: https://github.com/cloudflare/next-on-pages/issues/39
)
(
although there's a small bug that makes it potentially fail sometimes
as you can see near the bottom here: https://github.com/cloudflare/next-on-pages/issues/39
)
GitHub
I'm having issues getting my project to successfully deploy on Cloudflare because I am relying on a dependency (@vercel/og) which uses satori/wasm. The Vercel building process goes fine but whe...
Dit should work... (could you maybe share a repro? )
(could you maybe share a repro? )
KI installed @cloudflare/next-on-pages on my aplication and it alert a lot of vulnerability
debug 4.0.0 - 4.3.0
Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c
fix available via
node_modules/@vercel/fun/node_modules/debug
@vercel/fun <=1.1.0
Depends on vulnerable versions of debug
Depends on vulnerable versions of semver
node_modules/@vercel/fun
vercel 28.12.3 >=32.0.2
Depends on vulnerable versions of @vercel/fun
Depends on vulnerable versions of @vercel/node
node_modules/vercel
semver 7.0.0 - 7.5.1
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
fix available via
node_modules/@vercel/fun/node_modules/semver
undici <=5.28.2
Undici proxy-authorization header not cleared on cross-origin redirect in fetch - https://github.com/advisories/GHSA-3787-6prv-h9w3
fix available via
node_modules/@vercel/node/node_modules/undici
@vercel/node 2.14.0 || >=3.0.2
Depends on vulnerable versions of undici
node_modules/@vercel/node
6 vulnerabilities (3 low, 3 moderate)
npm audit report
debug 4.0.0 - 4.3.0
Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c
fix available via
npm audit fixnode_modules/@vercel/fun/node_modules/debug
@vercel/fun <=1.1.0
Depends on vulnerable versions of debug
Depends on vulnerable versions of semver
node_modules/@vercel/fun
vercel 28.12.3 >=32.0.2
Depends on vulnerable versions of @vercel/fun
Depends on vulnerable versions of @vercel/node
node_modules/vercel
semver 7.0.0 - 7.5.1
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
fix available via
npm audit fixnode_modules/@vercel/fun/node_modules/semver
undici <=5.28.2
Undici proxy-authorization header not cleared on cross-origin redirect in fetch - https://github.com/advisories/GHSA-3787-6prv-h9w3
fix available via
npm audit fixnode_modules/@vercel/node/node_modules/undici
@vercel/node 2.14.0 || >=3.0.2
Depends on vulnerable versions of undici
node_modules/@vercel/node
6 vulnerabilities (3 low, 3 moderate)
GitHub
semver vulnerable to Regular Expression Denial of Service
GitHub
Undici proxy-authorization header not cleared on cross-origin redirect in fetch
DThanks but today when I built the app without making any changes, it started working. I don't know how and why 
Dhttps://www.npmjs.com/package/@cf-wasm/og
https://www.npmjs.com/package/@cf-wasm/resvg
https://www.npmjs.com/package/@cf-wasm/satori
I published npm package by forking vercel/og and it supports svg output
https://www.npmjs.com/package/@cf-wasm/resvg
https://www.npmjs.com/package/@cf-wasm/satori
I published npm package by forking vercel/og and it supports svg output
npm
Generate Open Graph Images dynamically from HTML/CSS without a browser.. Latest version: 0.1.12, last published: 2 hours ago. Start using @cf-wasm/og in your project by running
npm i @cf-wasm/ognpm
A high-performance SVG renderer and toolkit, powered by Rust based resvg.. Latest version: 0.1.12, last published: 2 hours ago. Start using @cf-wasm/resvg in your project by running
npm i @cf-wasm/resvg. There is 1 other project in the npm registry using @cf-wasm/resvg.npm
Enlightened library to convert HTML and CSS to SVG.. Latest version: 0.1.12, last published: 2 hours ago. Start using @cf-wasm/satori in your project by running
npm i @cf-wasm/satoriit may be related to the runtime issue I mentioned
let's keep an eye on it
let's keep an eye on it
Nyes i know but only if you have paid plan
Nbecause with free plan vercel/og is too big
Bis it only me or does anyone have this issue where when you fix a syntax error the compiler error persists before you restart the whole dev server?
Btbh its not only for syntax error but for any error wow
Bthe error gets dismissed when you do some kind of change, but for any hard reloads the error comes back until you restart the dev server
Tdo you have any suggest for the package of fetching data in Workers. I use fetch but it is inconvenient. Axios is not compatible with edge run time.
HFetch is the way to fetch data on Workers. You could probably write something similar over a TCP socket, but that would be a lot more work, and a lot less ergonomic
Jwhy do you need a package to fetch data?
TI got it. fetch is fine for me. Ijust consider other package. Cause in nodejs I mainly use axios, so I thought edge runtime also support axios
TI try to use R2binding in next-on-pages. As fas as I understand, It only work locally when I run npm run dev. I mean it creates the r2 folder in the .wrangler. Is there anyway I can interact with the remore resource R2 in cloudflare when running "npm run dev" in nextjs app using next-on-pages.
Byou can check out my library https://github.com/sunneydev/requestly
TUpon inspecting the _worker.js folder in the .vercel/output directory after running "npx @cloudflare/next-on-pages" in my Next.js app, I noticed a JSON file named "nop-build-log.json." It's hefty, around 262 kB, free tier limit for Workers is 1 MB after gzip compression. My question is: Is the "nop-build-log.json" file essential for running the application? Also, does Cloudflare Pages upload this file during deployment via the dashboard with Git integration?
P.S.: Cloudflare is fantastic! I truly enjoy using their services, especially the supportive community. I plan to upgrade my account to a paid tier eventually, as my application will likely exceed the 1 MB limit in the future. My point here is to try to reduce the bundle size of the code and understand how the system works.
Thank you all.
P.S.: Cloudflare is fantastic! I truly enjoy using their services, especially the supportive community. I plan to upgrade my account to a paid tier eventually, as my application will likely exceed the 1 MB limit in the future. My point here is to try to reduce the bundle size of the code and understand how the system works.
Thank you all.
HIt's only counted if it is imported by the
_workers.js file, which I'm going to guess it isn't. Then it is instead subject to the 25 MiB per-file limitJthat file isn't included in the uploaded deployment
Tthank James
Tthank you.
RJnope, looks like it's supposed to be for nuxt instead of next
Thow easy is it to hit that 10MB worker size on the paid plan?
IWorkers are now limited to 25MB, not 10.
Toh so 1mb free 25mb on paid?
IYup.
Ttake my $5
Twhy I see on the website it said that the limit is 10MB. Can you share the link for 25 MB limit?
IThere was an open docs pull request but it was closed for some reason: https://github.com/cloudflare/cloudflare-docs/pull/13253/files
