tryGetModuleNameAsNodeModule: Ignore file extension

microsoft · Jun 7, 2018 · 67e3473 · 67e3473
1 parent e947154
commit 67e3473
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 9 deletions.
diff --git a/src/compiler/moduleSpecifiers.ts b/src/compiler/moduleSpecifiers.ts
@@ -248,7 +248,7 @@ namespace ts.moduleSpecifiers {
                     const mainFileRelative = packageJsonContent.typings || packageJsonContent.types || packageJsonContent.main;
                     if (mainFileRelative) {
                         const mainExportFile = toPath(mainFileRelative, packageRootPath, getCanonicalFileName);
-                        if (mainExportFile === getCanonicalFileName(path)) {
+                        if (removeFileExtension(mainExportFile) === removeFileExtension(getCanonicalFileName(path))) {
                             return packageRootPath;
                         }
                     }

diff --git a/tests/cases/fourslash/importNameCodeFixNewImportNodeModules7.ts b/tests/cases/fourslash/importNameCodeFixNewImportNodeModules7.ts
@@ -15,15 +15,8 @@
 // @Filename: node_modules/package-name/package.json
 //// { "main": "bin/lib/libfile.js" }
 
-
-// In this case, importing the module by its package name:
-// import { f1 } from 'package-name'
-// could in theory work, however the resulting code compiles with a module resolution error
-// since bin/lib/libfile.d.ts isn't declared under "typings" in package.json
-// Therefore just import the module by its qualified path
-
 verify.importFixAtPosition([
-`import { f1 } from "package-name/bin/lib/libfile";
+`import { f1 } from "package-name";
 
 f1('');`
 ]);