Issue errors on tslib version ranges in package.json #35927
Description
Similar in spirit to #33603
@bterlson and friends on the Azure SDK team mentioned that there was an issue with tslib where a local installation might grab tslib@1.10.x, but could have issues in other environments because their package.json specified a minimum version (1.9.x) which was too old.
I don't think that we generally dive into package.json to issue errors, but this seemed pretty unexpected, and it leads to more obvious behavior than with issuing errors about missing exports.
On the other hand, this might be a problem for slightly more esoteric but legitimate use-cases like alternate implementations/sources of tslib. For example, a user could point tslib at a local folder or a GitHub URL.