No error is generated for an incorrectly spelled config filename.

[JessyCatterwaul]

Is your feature request related to a problem? Please describe.

I'm a beginner to most of the technologies involved with Eleventy, and was following this tutorial: https://learn-eleventy.pages.dev/lesson/3/
I received errors when running npx eleventy --serve, that I did not understand.

I was helped by what seems to be an amazing Discord community. 😺
It turns out that I had just misspelled eleventy.js as elventy.js.

With eleventy not being a word that I'm all that familiar with looking at, that didn't register to my brain.

Describe the solution you'd like

I'm sorry, I don't know what is practical here. I just would have liked to have seen something automated that told me what the problem was, rather than

[11ty] 1. Problem creating an Eleventy Layout for the "./src/index.md" template file. (via EleventyBaseError)
[11ty] 2. You’re trying to use a layout that does not exist: _includes/layouts/home.html (via `layout: layouts/home.html`)

or

[11ty] 1. Having trouble rendering liquid template ./src/_includes/layouts/home.html (via TemplateContentRenderError)
[11ty] 2. tag "extends" not found, file:./src/_includes/layouts/home.html, line:1, col:1 (via ParseError)
[11ty] 3. tag "extends" not found (via AssertionError)

Describe alternatives you've considered

No response

Additional context

No response

[vrugtehagel]

I agree that this is an issue, and I've seen some people running into issues creating a config file with a name that seems like it would work but doesn't (like .eleventy.mjs or .eleventy.cjs).

My suggestion is to generate a warning message if no configuration file was found at all - I suspect most Eleventy projects have one anyway. It's not ideal for projects that (intentionally) don't have one, but I'm guessing that such a message would save more headaches than it creates regardless.