zero config detection issue with turborepo

[MickL]

Environment

• bun 1.2.1
• nitropack 2.10.4 / nitro-nightly@3.0.0-beta-28969273.f7aa9de6

Describe the bug

When deploying to Cloudflare Pages, the preset 'node-server' is selected instead of 'cloudflare-pages'. This leads to all deployments failing. I tried with both v2 and nightly v3.

Maybe some changes have been made at Cloudflare so the detection mechanism doesnt work anymore? My last successful deployment was on 14th of December. My next deployment on 16th of December failed because of selecting preset 'node-server'.

Additional informations

My Nuxt projects are still using the 'cloudflare-pages' preset.

Workaround

Set preset manually in package.json: "build": "NITRO_PRESET='cloudflare-pages' nitro build",

[pi0]

Just created a new project, cloudflare_pages is detected just as well. Have you set any custom command or something perhaps?

[MickL]

You are right, works in a minimal reproduction repo that I created. I figured this is an issue of Turborepo that I am using: Turborepo is actually removing all environment variables that are not on the allowlist (globalEnv array): https://turbo.build/repo/docs/crafting-your-repository/using-environment-variables#strict-mode

Could you tell me what environemnt variable is used to determine that the preset cloudflare-pages should be used? I dont find the select logic in the repo. I can then open an issue at Turborepo to not remove this variable.

Workaround: turbo run build --env-mode=loose

[pi0]

CF_PAGES

you can find the logic here: https://github.com/unjs/std-env/blob/main/src/providers.ts#L72

If had time do you mind to open a PR to mention about turbo repo workaround in cloudflare pages section? 🙏

[MickL]

Probably ALL providers would need an info that they dont get auto detected when using Turborepo without explicitly allowing the variables or setting --env-mode=loose? The same applies to Nuxt docs.

I opened an issue: vercel/turborepo#9860

I know they already have NUXT_* and NITRO_* variables on a allowlist so they dont get cut off by default. I am sure they will also add all variables that Nitro uses for detecting the deployment environment.

[pi0]

We can add banner here instead in meanwhile: https://nitro.build/deploy#zero-config-providers