npm install --force when deploying next to cloudflare pages?





crypto in next.js on workers? I found if I use edge runtime, cryptoX509Certificate would be availablenext-on-pages and a wrangler.toml so that when I publish a new post, it makes a build with the new post. I know how ot make the hook with WP and such, but don't see a way to add it to my account. I also don't see a way to connect my github to account since I'm deploying with the deploy command. @cloudflare/next-on-pages to deploy my site and didn't connect it to github. I wanted to create a hook, like this https://developers.cloudflare.com/pages/configuration/deploy-hooks/#wordpress@cloudflare/next-on-pages but see it them if I set up pages connecting to github account.unstable_after support with next-on-pages, it just required waitUntil which I managed to inject into it:# unknown). Can you link the PR on GitHub for context?npm install --force23:16:38.104 Cloning repository...
23:16:39.261 From https://github.com/kaankutan/kutan.dev
23:16:39.261 * branch 93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261
23:16:39.305 HEAD is now at 93d203e Image optimization added
23:16:39.306
23:16:39.390
23:16:39.391 Using v2 root directory strategy
23:16:39.417 Success: Finished cloning repository files
23:17:32.083 Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083 Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a285797701:52:20.142 ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142 ⚡️
01:52:20.142 ⚡️ The following routes were not configured to run with the Edge Runtime:
01:52:20.143 ⚡️ - /_not-found
01:52:20.143 ⚡️ - /index
01:52:20.143 ⚡️ - /login
01:52:20.143 ⚡️ - /settings
01:52:20.143 ⚡️ - /users
01:52:20.143 ⚡️ - /websites/[id]
01:52:20.143 ⚡️ - /websites
01:52:20.144 ⚡️
01:52:20.144 ⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144 ⚡️ export const runtime = 'edge';cryptocryptoedgeunstable_after# unknownname = "some-name"
compatibility_date = "2024-10-18"
assets = { directory = "./public" }
routes = [
{ pattern = "test.example.com", custom_domain = true }
]