Error Message and Logs
Explicit build configuration is ignored when repository contains Supabase Edge Functions
Projects that primarily use Node.js with pnpm workspaces are incorrectly treated as Deno applications if a supabase/functions directory exists. Even after specifying a custom nixpacks.toml, the build process continues selecting the Deno environment instead of honoring the configured Node.js setup.
Steps to Reproduce
- Create a pnpm workspace with a Node.js application.
- Add Supabase Edge Functions under
supabase/functions.
- Configure Nixpacks using a
nixpacks.toml file to target Node.js.
- Trigger a deployment.
- Observe that the build uses the Deno provider rather than the configured Node.js provider.
- Replace the build with a custom Dockerfile and deploy again.
- The application builds and deploys without issues.
Example Repository URL
No response
Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
Expected behavior: Explicit configuration in nixpacks.toml should override automatic language detection.
Actual behavior: The presence of Supabase Edge Functions causes Deno detection to take precedence, even when the main project is a Node.js monorepo.
Error Message and Logs
Explicit build configuration is ignored when repository contains Supabase Edge Functions
Projects that primarily use Node.js with pnpm workspaces are incorrectly treated as Deno applications if a
supabase/functionsdirectory exists. Even after specifying a customnixpacks.toml, the build process continues selecting the Deno environment instead of honoring the configured Node.js setup.Steps to Reproduce
supabase/functions.nixpacks.tomlfile to target Node.js.Example Repository URL
No response
Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
Expected behavior: Explicit configuration in
nixpacks.tomlshould override automatic language detection.Actual behavior: The presence of Supabase Edge Functions causes Deno detection to take precedence, even when the main project is a Node.js monorepo.