The rule rxjs-x/no-sharereplay-before-takeuntil is very good, and highlights an issue that's very easy to cause.

The weakness is that there might be other methods which wraps takeUntil() and is prone for the same issue. In Angular you have the operator takeUntilDestroyed(), for example.

I imagine it could be an option "alias" which allows specifying methodnames that are also treated as takeUntil() for this rule.

{
  "rxjs-x/no-sharereplay-before-takeuntil": [
    "error",
    {
      "alias": ["takeUntilDestroyed"]
    }
  ],
}