What’s a good next step? Kick off another build?
What’s a good next step? Kick off another build?

wrangler pages dev. If you are using next dev, then Bindings like KV will not be populated.wrangler.toml
react-error-boundary to wrap my app like this, and now it catches everything and allowed us to customize the error page:<Image /> component it doesn't work, and no images serve even the static in the public directorywrangler pages devnext dev ⚡️ The project is set up for pnpm but it is currently being run via npm this might lead to build errors, please be sure to use the same package manager your project uses when running @cloudflare/next-on-pages22:43:28.203 ▲ Build Completed in .vercel/output [1m]
22:43:28.315 ⚡️ Completed `npx vercel build`.
22:43:30.081 ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/og.func/wasm/wasm_a7e702bc5ba9227243abda7977c8096f59478d3f.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_a7e702bc5ba9227243abda7977c8096f59478d3f.wasm'
22:43:30.137 Finished
22:43:30.138 Found _worker.js in output directory. Uploading.react-error-boundary<Image /><ErrorBoundary
onError={(error, errorInfo) => {
if (window.Sentry) {
window.Sentry.captureException(error);
}
}}
fallbackRender={({ error, resetErrorBoundary }) => (
// add your own UI
)}
>
<Component {...pageProps} />
</ErrorBoundary>