Support custom electron-builder config locations

[seanssel]

In the process of upgrading this package now that I'm revisiting wdio in my project. This used to work with my setup in the past, but now I'm getting ERROR electron-service: Error: Electron-builder was detected but no configuration was found, make sure your config file is named correctly, e.g. electron-builder.config.json` when I try to run wdio.

I make use of the electron-builder's extend ability with multiple config files (yet another poorly documented electron-builder option). My project structure looks roughly like this:

.
├── build
├── config
│   ├── electron-builder-common.config.js
│   ├── electron-builder-production.config.js
│   ├── electron-builder-staging.config.js
├── e2e
│   ├── specs
│   ├── tsconfig.e2e.json
│   ├── tsconfig.json
│   ├── wdio.conf.ts
│   └── wdio.d.ts
| ... 

Each of my configs for specific environments extend the common config.

Looks like I have ways to get around this, but I swear this was working with my setup in the past so I'm just curious. Thanks!

[seanssel]

Crap, I just realized you have discussions enabled. I think this is more fitting for a discussion, will close.

[goosewobbler]

It's probably fine as an issue under investigation if this was working before. PRs are welcome if you want to help!

[seanssel]

Thanks, yeah I'll try to take a deeper look when I get some time.

I'm also running into some pain due to the fact that my wdio.conf.ts isn't in project root. Was attempting to use the appEntryPoint option today, but it assumes that the electron binary is in node_modules in the same directory as my wdio.conf.ts...it's actually in project root at the level above.

Might not be anything related to this library, but figured I'd mention it. I can easily move the wdio config file up, but I wanted to keep my project root cleaner.