Maybe there is some lint rule to make it a normal string, but in this PR I think it's ok.🤫

There's @typescript-eslint/quotes, which can be configured with allowTemplateLiterals: false to avoid unnecessary template literals (despite the name, it does not forbid all usage of template literals). To be compatible with Prettier, avoidEscape: true must also be set (even if you extend eslint-config-prettier, individual rule configurations take precedence).

The type casting can be avoided if we parameterize the function's input and output.

export function beginHiddenCallStack<T, A extends any[], R>(
  fn: (this: T, ...args: A) => R,
) {
  if (!SUPPORTED) return fn;

  return Object.defineProperty(
    function (this: T, ...args: A) {
      setupPrepareStackTrace();
      return fn.apply(this, args);
    },
    "name",
    { value: STOP_HIDNG },
  );
}

We still need to type cast somewhere, because the functions that we receive in the config have type Function which is not compatible with the "explicit" function types. However, I moved them to the config validation logic so that the "internals" are properly typed.

Nit: Can you restrict the typing here? It seems to me status can only be "hiding" | "showing" | "unknown".

May extend the example a bit, for example, what will be the shown call stack if we called injcectVirtualStackFrame(error, "h") and injcectVirtualStackFrame(error, "i")?