v5 - Differences between signIn function return types between v4 and v5

[AustinKostreba]

I've noticed that the returned types for the signIn function are different between v4 and v5. In v4, we would import sign in like this: import { signIn} from next-auth/react. However, in v5, we import it from the exported signIn function in the auth.ts file.
Here is the v4 function type definition to show the types:

signIn: <
  P extends RedirectableProviderType | undefined = undefined,
>(
  provider?: LiteralUnion<
    P extends RedirectableProviderType
      ? P | BuiltInProviderType
      : BuiltInProviderType
  >,
  options?: SignInOptions,
  authorizationParams?: SignInAuthorizationParams
) => Promise<
  P extends RedirectableProviderType ? SignInResponse | undefined : undefined
> 

And here is the v5 function type definition:

signIn: <
    P extends BuiltInProviderType | (string & {}),
    R extends boolean = true,
  >(
    /** Provider to sign in to */
    provider?: P, // See: https://github.com/microsoft/TypeScript/issues/29729
    options?:
      | FormData
      | ({
          /** The relative path to redirect to after signing in. By default, the user is redirected to the current page. */
          redirectTo?: string
          /** If set to `false`, the `signIn` method will return the URL to redirect to instead of redirecting automatically. */
          redirect?: R
        } & Record<string, any>),
    authorizationParams?:
      | string[][]
      | Record<string, string>
      | string
      | URLSearchParams
  ) => Promise<R extends false ? any : never>

My app supports multiple credentials providers to handle various login methods, like credentials logins and LDAP logins. In v4, deriving these types was easy. I'm not directly redirecting on a successful sign in, so it was useful to get a detailed response from the sign in, and the types would be correctly inferred by setting the first parameter to the id set for that credentials provider. For example,

const signInResponse = await signIn('ldap', {
    username: data.username,
    password: data.password,
    redirect: false,
})

However, in v5, the response resolves to either any or never, and the SignIn function only recognizes the default credentials provider, and can't correctly infer any of the types for the provider I've exampled (or any other ones, for that matter).

Am I missing something, or does this not seem like a direct regression for this function? It used to be so good at automatically handling any provider I threw at it, but now I feel like all the benefits of typescript are totally absent here.