You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
10:26:35 ../types/build/src/deps/xml2js/xml2js.d.ts(10,25): error TS7016: Could not find a declaration file for module './parser.js'. '/var/lib/TeamCity/work/30ffb35c1b6c4089/keyman/common/web/types/src/deps/xml2js/parser.js' implicitly has an 'any' type.
10:26:35 ../types/build/src/deps/xml2js/xml2js.d.ts(11,26): error TS7016: Could not find a declaration file for module './builder.js'. '/var/lib/TeamCity/work/30ffb35c1b6c4089/keyman/common/web/types/src/deps/xml2js/builder.js' implicitly has an 'any' type.
10:26:35 ../types/build/src/main.d.ts(34,25): error TS7016: Could not find a declaration file for module './deps/xml2js/xml2js.js'. '/var/lib/TeamCity/work/30ffb35c1b6c4089/keyman/common/web/types/src/deps/xml2js/xml2js.js' implicitly has an 'any' type.
10:26:35 ../types/build/src/main.d.ts(34,25): error TS7016: Could not find a declaration file for module './deps/xml2js/xml2js.js'. '/var/lib/TeamCity/work/30ffb35c1b6c4089/keyman/common/web/types/src/deps/xml2js/xml2js.js' implicitly has an 'any' type.
Regression arising from #11660. Causing builds to fail on master, which suggests a potential confict with #11424?
This is happening due to inconsistency in the tsconfig.json compilerOptions between web and common/web/types. Specifically, in this instance, allowJs diverges from the global default:
The problem seems to be that tsc --build in common/web/keyboard-processor will attempt to build common/web/types using the settings from common/web/keyboard-processor/tsconfig.json.
How best to resolve this? I can see various strategies we could use:
Eliminate all compilerOptions overrides across all tsconfig.json files. This is a good long-term solution, as it simplifies our build environment, but it may be difficult to pull off.
Patch this specific issue. I am not sure of the most reliable approach to doing this at present; I patched out the allowJs property from web/tsconfig.base.json and the build then succeeded, but it may cause other problems?
If memory serves, the allowJs was originally in place due to its interaction with emitting .d.ts files; there was a point where TS would refuse to emit declaration files if allowJS were true. We're past that point now, and it appears that no build errors resulted - that would be the only potential complication I'd worry about here.
Regression arising from #11660. Causing builds to fail on master, which suggests a potential confict with #11424?
The text was updated successfully, but these errors were encountered: