Well, I guess have fun untangling that knot whenever there's a problem with Webpack! We all know how easy and fun the last Webpack major version upgrade was to all the things out there designed to reduce the amount of interaction with it when bootstrapping a project.
Just freaking learn Webpack, dude. I agree that it sucks, but not everything about your job needs to be fun.
For example, if there isn't a config file, it's usually because there are more than one. Or, even worse, the config is dynamically generated. A build process like that is much harder for me to fully understand than one with a simple webpack.config.js.
However, this may be biased, as it's coming from the perspective of someone who already "knows Webpack".