Skip to content

Conversation

@vrugtehagel
Copy link
Contributor

Creates a warning for when a default config file (e.g. .eleventy.js or eleventy.config.js) was not found and none was explicitly specified using the --config option.

Fixes #3654.

For the wording of this error, I avoided saying "No default config file found" since following that up with "using the default configuration" would be confusing. It also doesn't seem necessary to say "default config file" anyway, since this warning cannot appear when a config file was manually specified, so there is no ambiguity.

@zachleat
Copy link
Member

Going to close this one per comment left on #3654 (comment) sorry! Happy to discuss other options!

@zachleat zachleat closed this Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

More friendly output for an incorrectly spelled default config filename (missing config file)

2 participants