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

TypeScript Version: 3.5.1

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,

interface Buffer {
    ___doesNotExist? : any;
}

The following causes downstream packages to break,

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.

Start with the linked AnyhowStep/ts-issue-35172 reproduction and compare the two Buffer declarations in the issue, including the referenced type-mapping commit. Confirm the downstream-package failure and determine whether the compiler should reject the declaration consistently or accept it consistently; done means the chosen behavior is reproduced and covered by an appropriate regression test.