Yes, all of these are supported in JSDoc because they are supported in TypeScript. Because JSDoc is TypeScript. You can either define your types in JSDoc comments or in .ts files.
I really mean it. You can even use the @satisfies operator like so
/** @satisfies {Type} */
Discriminated unions, conditional types, mapped types, template literal types, etc work exactly the same way if you define them in a JSDoc comment as if you define them in a .ts file
Salesforce v2 is a pretty bull case for Palantir! This bias people have against against application platforms requiring a consultant ecosystem and per-customer installations is just not accurate - in software, as in the rest of the world, there are some areas where it's the right model to get things done efficiently. Walmart can't use an off-the-shelf CRM platform any more than US Steel could use an off-the-shelf furnace.
Never really occurred to me why Mr. Beast content doesn’t appeal to me (nor have I thought about it much)… their sole purpose is CTR. Makes sense. Lame.
Discriminated unions, conditional types, mapped types, template literal types, recursive type aliases, higher-kinded type patterns, generic constraints with conditional inference, the infer keyword, never type exhaustiveness checking, const assertions, readonly tuple and array inference, exact object types, key remapping in mapped types, indexed access types, variance annotations, assertion signatures, strict null checking with flow-sensitive narrowing, definite assignment assertions, the satisfies operator, declaration merging, module augmentation, symbol-typed properties, type-safe enums
…and not written via comments