D
getRequestContext made things easier 
D
next-dev hacks we can actually easily make it available during dev too... I can easily open a PR for that, but again the no-op implementation provided by getPlatformProxy is currently the best I can offer 
caches is or not on the global scope)D
D
D
S
B
JBD
M
C
cf-cache-status response headers? This is a Next 13 app using SSR
M
P
O
return NextResponse.redirect(new URL("/auth", request.url));router.push instead of router.refresh on auth success e.g
GG
IG
DD
https://github.com/cloudflare/next-on-pages/blob/3846730c4a0d12cda128d691160968d0a131a6f1/packages/next-on-pages/tests/templates/utils/http.test.ts#L46-L54JJ
B
DD
Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' is the culprit but I don't know anything about what could cause itD
MDMMDJDJDMMDDDDDD
getRequestContextnext-devgetPlatformProxycachescf-cache-statusreturn NextResponse.redirect(new URL("/auth", request.url));router.pushrouter.refresh19:01:36.442 ▲ Build Completed in .vercel/output [57s]
19:01:36.553 ⚡️ Completed `npx vercel build`.
19:01:39.216 ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
19:01:39.272 Finished
19:01:39.273 Found _worker.js in output directory. Uploading.
19:01:40.514 Attaching additional modules:
19:01:40.515 - __next-on-pages-dist__/manifest/27d10e462fba646daaa29468a0656e12.js (esm)
19:01:40.515 - __next-on-pages-dist__/manifest/__RSC_SERVER_MANIFEST.js (esm)
19:01:40.515 - __next-on-pages-dist__/webpack/137.js (esm)
19:01:40.515 - __next-on-pages-dist__/webpack/1796.js (esm)
19:01:40.516 - __next-on-pages-dist__/webpack/44bff480f105853cb03b9b061f5738d6.js (esm)
19:01:40.516 - __next-on-pages-dist__/webpack/5303.js (esm)
19:01:40.516 - __next-on-pages-dist__/webpack/6595.js (esm)
19:01:40.516 - __next-on-pages-dist__/webpack/8775.js (esm)
19:01:40.516 - __next-on-pages-dist__/webpack/8f135fd1cad616b24af4b973584a7795.js (esm)
19:01:40.677 ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.
19:01:40.678
19:01:40.678
19:01:40.682
19:01:40.683 ✘ [ERROR] Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.683
19:01:40.683
19:01:40.685 ✘ [ERROR] Build failed with 1 error:
19:01:40.685
19:01:40.685 error: Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.685
19:01:40.685
19:01:40.698 Failed building Pages Functions.
19:01:41.641 Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrHUnexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'// file: env.d.ts
interface CloudflareEnv {
KV: KVNamespace;
}import { KVNamespace } from "@cloudflare/workers-types";
declare global {
interface CloudflareEnv {
KV: KVNamespace;
}
}import { ImageResponse } from 'next/og'
import Image from 'next/image'
// Route segment config
export const runtime = 'edge'
// Image metadata
export const size = {
width: 32,
height: 32,
}
export const contentType = 'image/png'
// Image generation
export default function Icon() {
return new ImageResponse(
(
// ImageResponse JSX element
<Image height={size.height} width={size.width} src="/favicons/apple-icon-180x180.png" alt="PurpleHosting - Icon" />
),
// ImageResponse options
{
// For convenience, we can re-use the exported icons size metadata
// config to also set the ImageResponse's width and height.
...size,
}
)
}