Fix resolving js imports that have same-named ".d.ts" from ts with 'noTypeDefinitions' set to true

[williamvinogradov]

Reason:
If .d.ts exists, ts resolve import as the path to the type-definition file by default (instead of the js file).
But if we set the noTypeDefinitions flag to true,
we pass the unresolved import path to the ts.resolveJSModule.

And if we have a type alias:

// tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "@test/*": ["*"]
    }
  }
}

our unresolved import looks like

@test/foo

instead of

<path_to_directory>/foo

Therefore ts cannot resolve this import and fails with an error.

Solution:
Pass to the ts.resolveJSModule resolved path of the import without extension.

Relates to: #112

[mrjoelkemp]

Thanks @williamvinogradov! Released a new patch version with the fix.