Is `caches` field (Cache API) accessible?
Is
caches field (Cache API) accessible?
caches is or not on the global scope?)getPlatformProxy utility (used by next-on-pages under the hood) don't have a local dev support for caches: https://github.com/cloudflare/workers-sdk/issues/4879getRequestContext made things easier 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)cf-cache-status response headers? This is a Next 13 app using SSRreturn NextResponse.redirect(new URL("/auth", request.url));router.push instead of router.refresh on auth success e.g
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 it// file: env.d.ts
interface CloudflareEnv {
KV: KVNamespace;
}import { KVNamespace } from "@cloudflare/workers-types";
declare global {
interface CloudflareEnv {
KV: KVNamespace;
}
}19: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'