I would say we could probably go one step further and just offer all of this off of the parser serivces!

For example:

typeParserServices={getTypeAtLocation(node:TSESTree.Node):ReturnType<ts.TypeChecker['getTypeAtLocation']>;};constparserServices=util.getParserServices(context);parserServices.getTypeAtLocation(node);

That would make it even more straight-forward for people to use the tooling!

Oh interesting. I like putting this as a member ofParserServices, though I'm hesitant to put potentially dozens of them as siblings of our own properties. MaybeparserServices.checker.getTypeAtLocation?

the reason I like it as a direct sibling is it's one less step.
Right now people do things like

const{program}=util.getParserServices(context);constchecker=program.getTypeChecker();

Adding it as a separate property would make it more likely there's a clash if the consumer needs a more advanced API than what we offer.
For example:

const{checker, program}=util.getParserServices(context);constchecker2=program.getTypeChecker();

If we build it right then most usecases shouldn't really need to ever manually touchprogram/esTreeNodeToTSNodeMap/tsNodeToESTreeNodeMap!