`extends ArrayBufferLike` works for own package; but causes errors for downstream users

<!-- 🚨 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.5.1 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** + `extends ArrayBufferLike` + TS2312 + An interface can only extend an object type or intersection of object types with statically known members. **Code** Repro, https://github.com/AnyhowStep/ts-issue-35172 The line of code that introduced the problem, https://github.com/AnyhowStep/type-mapping/commit/cb420b8e14dda4de5bf017bcc4a3ab3f35e71de5#diff-f84343d86daf9a112cfa32bdb89c7cdaR2 The following is safe to use on own package and downstream packages, ```ts interface Buffer { ___doesNotExist? : any; } ``` The following causes downstream packages to break, ```ts interface Buffer extends ArrayBufferLike { ___doesNotExist? : any; } ``` **Expected behavior:** Option A: + Should crash for own package + Should crash for downstream packages Option B: + Should not crash for own package + Should not crash for downstream packages **Actual behavior:** + Does not crash for own package + Crashes for downstream packages **Playground Link:** None. But I have repro steps, https://github.com/AnyhowStep/ts-issue-35172 **Related Issues:** None that I could find.