Netlify ignores framework configuration and throws "Error: Detected commands for: Eleventy, Vite."

Support
1

Hi, I have an Eleventy project and recently added Vitest to it for local testing. This seems to confuse Netlify’s deployment which complains that it doesn’t know which one to use:

Error: Detected commands for: Eleventy, Vite. Update your settings to specify which to use. Refer to https://ntl.fyi/dev-monorepo for more information.

Ok, well that link says I can explicitly specify the framework. So I tried:

[dev]
framework = "11ty"

And:

[dev]
framework = "Eleventy"

But neither of these work and the same error surfaces. I wasn’t able to confirm that this should work as the documentation doesn’t state it. But ok, I guess I’ll just use #custom then. So I updated to:

[dev]
command = "npm start"
targetPort = 8080
framework = "#custom"

This is enough for netlify dev to accept the configuration, however I am continuing to get the same error. See this deployment where I printed the Netlify config with this setup, clearly defining a framework, and yet received the same error on deployment: WIP: Debugging · dgp1130/blog@0c3a677 · GitHub

This deployment is attempting to go to: https://post-isolating-css-inheritance--dwac-blog.netlify.app/

Sidebar: I feel like this error is a bit aggressive. I don’t build my site with Netlify (I have build = ““), I don’t use netlify dev, and to my knowledge I don’t rely on these framework integrations, nor do I particularly want to. Netlify genuinely has no need to know or care about what framework I’m using and it’s kind of frustrating that I can’t deploy for a completely unrelated problem which should in no way block deployments. I should be able to deploy a pre-built application without necessarily having a sound dev config. So I suspect there’s actually two bugs here:

  1. Netlify isn’t parsing my config correctly.
  2. Even if it does parse this bit incorrectly, I should still be able to publish, given that this doesn’t affect the publishing workflow.

Just my two cents

Probably unrelated but I’ll mention just in case / for an additional bug: While the above configuration is enough for netlify dev to accept it and build the site, it does fail when setting up edge functions (of which I have none):

$ npm run -s netlify dev

⬥ Injecting environment variable values for all scopes
⬥ Ignored general context env var: LANG (defined in process)
⬥ Setting up local dev server

❯ Installing extensions
   - neon

⬥ Starting #custom dev server
✔ #custom dev server ready on port 8080
⠋ Setting up the Edge Functions environment. This may take a couple of minutes.
   ╭─────────────────────── ⬥  ────────────────────────╮
   │                                                   │
   │   Local dev server ready: http://localhost:8888   │
   │                                                   │
   ╰───────────────────────────────────────────────────╯


> dgp1130-blog@0.0.0 start
> npm run -s clean && npm run -s build:11ty && npm run -s build:browser && npm run -s 11ty -- --serve

⠇ Setting up the Edge Functions environment. This may take a couple of minutes.
src/www/scripts/base.ts → src/www/scripts/base.js...
⠙ Setting up the Edge Functions environment. This may take a couple of minutes.created src/www/scripts/base.js in 1s

src/www/scripts/post.ts → src/www/scripts/post.js...
⠹ Setting up the Edge Functions environment. This may take a couple of minutes.created src/www/scripts/post.js in 129ms
✖ Setting up the Edge Functions environment. This may take a couple of minutes.
 ›   Error: Netlify CLI has terminated unexpectedly
This is a problem with the Netlify CLI, not with your application.
If you recently updated the CLI, consider reverting to an older version by running:

npm install -g netlify-cli@VERSION

You can use any version from https://ntl.fyi/cli-versions.

Please report this problem at https://ntl.fyi/cli-error including the error details below.

[11ty] Writing _site/404/index.html from ./src/www/404.njk
[11ty] Writing _site/deployment/index.html from ./src/www/deployment.njk
[11ty] Writing _site/index.html from ./src/www/index.njk
[11ty] Writing _site/feed.xml from ./src/www/feed.njk
[11ty] Writing _site/attributions/index.html from ./src/www/attributions.njk
[11ty] Writing _site/privacy/index.html from ./src/www/privacy.njk
[11ty] Writing _site/social/index.html from ./src/www/social.njk
Error: There was a problem setting up the Edge Functions environment. To try a manual installation, visit https://ntl.fyi/install-deno.
    at toError (file:///home/doug/Source/blog/node_modules/netlify-cli/dist/utils/command-helpers.js:146:16)
    at logAndThrowError (file:///home/doug/Source/blog/node_modules/netlify-cli/dist/utils/command-helpers.js:152:17)
    at prepareServer (file:///home/doug/Source/blog/node_modules/netlify-cli/dist/lib/edge-functions/proxy.js:148:16)
    at async Promise.all (index 1)
    at async file:///home/doug/Source/blog/node_modules/netlify-cli/dist/lib/edge-functions/proxy.js:73:41
    at async onRequest (file:///home/doug/Source/blog/node_modules/netlify-cli/dist/utils/proxy.js:610:35)

  System:
    OS: Linux 6.6 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11600K @ 3.90GHz
  Binaries:
    Node: 24.7.0 - ~/.nvm/versions/node/v24.7.0/bin/node
    npm: 11.5.1 - ~/.nvm/versions/node/v24.7.0/bin/npm
  Browsers:
    Chrome: 120.0.6099.71
2

Netlify CLI deploy command | Netlify CLI command reference

You can use the --no-build flag

3

Thanks @hrishikesh, deploying with –-no-build does work around the issue.

Ideally the deployment shouldn’t crash from this situation, but –-no-build is probably what I want regardless, so I don’t mind using it as a workaround here.

Thanks for the suggestion!

Relevant commit with the workaround for those interested: Skip builds in Netlify. · dgp1130/blog@f485abd · GitHub