Yes, as it should be. There are no enums. Instead, you can pass in any of the documented strings (or whatever the base type is). Even inside TypeScript, an enum is really just a union type on steroids.
When you expose TypeScript code to JavaScript consumers you absolutely must validate all incoming data anyway, whatever type you declare.
This is not about trusting the information your users provide. It is about making your APIs accessible to users. If you hide some information, your API is less accessible.
But it's just as hidden either way. The API consumer does not know there's an enum that's supposed to go in there. The only way to get that information is to read the documentation.
I have no idea where you are coming from unfortunately.
Generally speaking, a Javascript user has access to the same type script language features (including hints, auto-completion,...) as a typescript user.
Even the most primitive text editor supports language server protocol nowadays.
The library your interoperating with does not even have to be written in typescript if the author provided @typedef JSDocs.
const enums break this because no value of this type exists
