Non-NPM Package Name Conflict

[fowl2]

The readme says:

If the package you are adding typings for is not on npm, make sure the name you choose for it does not conflict with the name of a package on npm. (You can use npm info to check for the existence of the package.)

This isn't much guidance, and doesn't seem to consider that someone could create an npm package after this check.

This has happened @types/xrm provides types for the js APIs available within the Microsoft Dataverse platform (previously known as Dynamics CRM), which is not on NPM. Now someone has created an NPM package xrm and the Typescript bot is linking to it.

Renaming the existing types package for the non-npm code would be disruptive.
If this newly created npm package started needing types, they would be hard to find.

Not sure what to do? Some extra metadata somewhere?