wrangler pages deploy and I don't see an assets binding anywhere and it's still using @remix-run/cloudflare-pages...
npm create cloudflare@latest my-remix-app -- --framework=remix --experimental generates that but it shouldn't.headers for various asset routes._headers file in the public folder - https://developers.cloudflare.com/pages/configuration/headers/
wrangler pages functions build.ctx seems to be empty for us sometimes, since a couple of hours2024-09-23 with the nodejs_compat flag? We saw about a 2x increase in bundle size on our workers.nodejs_compat implies nodejs_compat_v2 after that compatibility_date & Wrangler adds polyfills with unenv"wrangler": "3.78.10", but works fine with wrangler on 3.78.9:ctxworkers.api.error.unknown [code: 10013]
function isNotEmptyObject<T extends Record<string, any>>(val: T | unknown): val is T {
if (Object.prototype.toString.call(val) !== '[object Object]') return false;
for (const _ in val as Record<string, any>) {
return true;
}
return false;
}
export default {
async fetch(request, env, ctx): Promise<Response> {
if (!isNotEmptyObject(ctx)) throw new Error('ctx');
return new Response('Hello World!');
},
} satisfies ExportedHandler<Env>;wrangler pages deploynpm create cloudflare@latest my-remix-app -- --framework=remix --experimentalheaders_headers "build": "remix vite:build && wrangler pages functions build --outdir build/worker",
"deploy": "npm run build && wrangler deploy",
"preview": "npm run build && wrangler dev",wrangler pages functions build for (const _ in val) {
return true;
}2024-09-23nodejs_compatnodejs_compatnodejs_compat_v2compatibility_date