I periodically run into this, and it can be quite annoying, sometimes even destructive.
My 11ty build command usually looks like this:
npx @11ty/eleventy --config=somedir/eleventy.js
The current behavior is that if 11ty doesn't find the file specified, it still builds, but using the default config.
This can create a lot of trash in the directory structure that I then need to remove manually.
I’d be inclined to consider it a bug: if I’ve explicitly specified a config file, I literally never want to build with the default config. If the config file I specified is not found, that’s a genuine error condition, and 11ty should just let me know and exit early (possibly by helpfully outputting CWD too or the full path it was trying).
I periodically run into this, and it can be quite annoying, sometimes even destructive.
My 11ty build command usually looks like this:
The current behavior is that if 11ty doesn't find the file specified, it still builds, but using the default config.
This can create a lot of trash in the directory structure that I then need to remove manually.
I’d be inclined to consider it a bug: if I’ve explicitly specified a config file, I literally never want to build with the default config. If the config file I specified is not found, that’s a genuine error condition, and 11ty should just let me know and exit early (possibly by helpfully outputting CWD too or the full path it was trying).