fix: Remove moduleResolution CompilerHost setting

This setting leads to unexpected behavior due to [1] [1]: https://devblogs.microsoft.com/typescript/announcing-typescript-5-6/#support-for-arbitrary-module-identifiers4
SAP · Sep 11, 2024 · 1f1dbf8 · 1f1dbf8
1 parent 2dfb412
commit 1f1dbf8
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 3 deletions.
diff --git a/resources/overrides/index.d.ts b/resources/overrides/index.d.ts
@@ -1,3 +1,3 @@
 import "./jquery.sap.mobile";
 import "./jquery.sap";
-import "./library/index"
+import "./library/index";
diff --git a/src/linter/ui5Types/TypeLinter.ts b/src/linter/ui5Types/TypeLinter.ts
@@ -14,7 +14,6 @@ const log = getLogger("linter:ui5Types:TypeLinter");
 const DEFAULT_OPTIONS: ts.CompilerOptions = {
  target: ts.ScriptTarget.ES2022,
  module: ts.ModuleKind.ES2022,
- moduleResolution: ts.ModuleResolutionKind.NodeNext,
  // Skip lib check to speed up linting. Libs should generally be fine,
  // we might want to add a unit test doing the check during development
  skipLibCheck: true,

diff --git a/src/linter/ui5Types/amdTranspiler/transpiler.ts b/src/linter/ui5Types/amdTranspiler/transpiler.ts
@@ -31,7 +31,6 @@ function createCompilerHost(sourceFiles: SourceFiles, writtenFiles: WrittenFiles
 }
 
 const compilerOptions = {
- moduleResolution: ts.ModuleResolutionKind.NodeNext,
  checkJs: false,
  allowJs: true,
  skipLibCheck: true,