<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with the latest published version. It may have already been fixed. For npm: `typescript@next` This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly --> **TypeScript Version:** 3.8.3 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** `getTypeAtLocation` **Code** ```ts declare class SomeClass implements NodeJS.CallSite { // } ``` **Expected behavior:** `getTypeAtLocation` on the `PropertyAccessExpression` node for `NodeJS.CallSite` should return `CallSite`. **Actual behavior:** Instead, it returns `any` with intrinsic name `error`. **Notes** Note that `getTypeAtLocation` on the parent `ExpressionWithTypeArguments` does actually succeed. **Playground Link:** N/A **Related Issues:** #35233 Thanks to @bradzacher for finding this!