tsconfig.json custom configuration

[Oleh Berehovskyi]

Hi,

I’m trying to configure `compilerOptions` for LWC TypeScript during Push/Deploy, but I’ve encountered some issues.
Currently, both `**/lwc/tsconfig.json` and `**/lwc/tsconfig.compile.json` files are managed by IC, and any changes I make are reverted upon Push/Deploy. The same happens with the `.illuminatedCloud/lwc/tsconfig.json` file. Additionally, modifying the root `tsconfig.json` doesn’t seem to have any effect.
Am I missing a configuration step here? While I understand that I can use the CLI to achieve the desired outcome, is there a way to configure the Push/Deploy compilation process directly?

Thanks in advance for your help!

Best regards,
Oleh Berehovskyi

[Scott Wells]

Hi. Yes, with IC’s first-class support for LWC/TypeScript, IC expects to fully manage the tsconfig*.json files under the lwc and .illuminatedCloud/lwc directories. You can disable the feature altogether by unchecking Illuminated Cloud | Configure Application | Lightning Web Components | Lightning Web Components TypeScript support (beta). While that will keep IC from generating/updating its own tsconfig*.json files, it will still maintain the standard and project-specific type definitions under .illuminatedCloud/lwc/types. Note that unchecking that option will also disable automatic compilation of LWC TypeScript files on deployment, the option to create an LWC TypeScript component, and a few other aspects of the overall feature.

Regards,
Scott Wells

​

[Scott Wells]

Perhaps looking at this differently, if you're trying to use IC's first-class support for LWC/TypeScript and are finding that you're needing to change the compiler configuration, please let me know what changes you're needing to make and why. It's very possible (likely?) that others will need those same changes. Feel free to report any issues or shortcomings in the public issue tracker so that they're concretely on my -- and other IC users' -- radar.

Regards,

Scott Wells