LoaderOptions: configFileContent

[hdennen]

We're specifying different tsconfig settings for different builds and I'd like to be able to just generate one and pass it in without writing anything to disk. Is anyone working on anything like this? I'm happy to take a shot at it when I get the time.

[johnnyreilly]

Not at present but we welcome contributions - go for it!

[hdennen]

Will do 👌

[loilo]

We could extend the scope of the possible new configFile option to achieve this (see #607). Naming-wise, it could definitely go in there.

Currently, the option takes file names and path, so strings only. We could passing a JavaScript object interpret as "passing the config directly". What do you think, @hdennen?

I'm not sure if overloading an option like that could confuse users, however it would definitely prevent other kinds of confusion with mutually exclusive options (configFileName ↔ configFileContent).

[hdennen]

@loilo Honestly I don't think it matters. My knee jerk response is to put options 1 to 1 with what they do but adding more functionality to the configFile option seems fine.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing as stale. Please reopen if you'd like to work on this further.