Add configFile option

[loilo]

This deprecates the configFileName option and renames it to configFile.
It keeps its user-facing behaviour, improving some path resolutions under the hood.
Using the configFileName option will now raise a logWarning in the console.

[johnnyreilly]

Thanks! I'll try and take a look this weekend. Tests pass!

[johnnyreilly]

Brilliant - thanks!

[johnnyreilly]

shipped with v2.3.4 - thanks for your help!

[loilo]

My pleasure. 🙃

[develar]

So cool, electron-webpack uses ts-loader in the user projects and in any case have to find tsconfig (and set to fork-ts-checker-webpack-plugin if need, option tsconfig) So, a little bit more reliable (because don't rely on ts-loader logic anymore — no logic duplication) and faster. Thanks a lot.

[loilo]

@develar Glad that it helped.

I'm still wondering if this option could need an additional per-entry-point configurability, something like this:

configFile: {
  '*': 'tsconfig.json', // ← default value
  'named-entry-point-a': '/var/www/tsconfig.json',
  'named-entry-point-b': 'wildly-different-name.json'
}

Before possibly opening an issue about this, what do you @develar as an experienced ts-loader user think about this?

[develar]

@loilo I think it is not required. Currently, we use one tsconfig.json for both parts (Electron app consists of two parts — code for renderer process and code for main process). I cannot imagine when it can be required :)

[loilo]

Okay, thanks for your feedback – I guess then I could go deeper in thinking about this instead.