fix(Stencil): ensure strictConfig properties has default values if loadedConfig is undefined

[dgonzalezr]

The change ensures that the strictConfig object properties have default values if not provided in the loadedConfig or if loadedConfig is undefined.

When looking at the code, const loadedConfig = loadConfigResults.config where loadConfigResults results from an attempt to load a config:

const loadConfigResults = await loadConfig({
  config,
  configPath,
  logger,
  sys,
});
const loadedConfig = loadConfigResults.config;

meaning, perhaps, it could not be loaded at a certain point (according to the LoadConfigResults interface declaration on @stencil/core)

/**
 * Results from an attempt to load a config. The values on this interface
 * have not yet been validated and are not ready to be used for arbitrary
 * operations around the codebase.
 */
export interface LoadConfigResults {
    config: ValidatedConfig;
    diagnostics: Diagnostic[];
    tsconfig: {
        path: string;
        compilerOptions: any;
        files: string[];
        include: string[];
        exclude: string[];
        extends: string;
    };
}

Fixes: #1167

[nx-cloud]

View your CI Pipeline Execution ↗ for commit c759786.

Command	Status	Duration	Result
nx affected --target lint build test e2e	✅ Succeeded	38s	View ↗
nx-cloud record -- pnpm exec nx format:check	✅ Succeeded	2s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-14 17:40:39 UTC