It's possible to use HF along with Next-Auth Providers?

[jonathanunes1991]

I would like to use Hyper-Fetch along with Next-Auth, using Next.JS page routes.
When using the custom provider of Next-Auth, I need to make a POST call to a specific gateway... when making a call using HF, an error is displayed:

⨯ uncaughtException: Error: Controller is not found
    at createAbortListener (E:\.......\node_modules\@hyper-fetch\core\dist\index.cjs.js:1494:13)
    at ClientRequest.<anonymous> (E:\.......\node_modules\@hyper-fetch\core\dist\index.cjs.js:325:25)
    at Object.onceWrapper (node:events:633:26)
    at ClientRequest.emit (node:events:518:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
    at Socket.socketOnData (node:_http_client:535:22)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

and after completing the request, the reported result is:

response: {
  data: null,
  status: 0,
  error: Error: Request timeout
      at getErrorMessage (E:\.......\node_modules\@hyper-fetch\core\dist\index.cjs.js:373:12)
      at onTimeoutError (E:\.......\node_modules\@hyper-fetch\core\dist\index.cjs.js:1481:19)
      at ClientRequest.<anonymous> (E:\.......\node_modules\@hyper-fetch\core\dist\index.cjs.js:353:37)
      at ClientRequest.emit (node:events:518:28)
      at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
      at Object.onceWrapper (node:events:632:28)
      at TLSSocket.emit (node:events:530:35)
      at Socket._onTimeout (node:net:589:8)
      at listOnTimeout (node:internal/timers:573:17)
      at process.processTimers (node:internal/timers:514:7),
  success: false,
  extra: { headers: {} }
}

the call is made within the following file: src\pages\api\auth\[...nextauth].ts

export const authOptions: AuthOptions = {
  providers: [
    CredentialsProvider({
      id: 'signInByEmailAndPassword',
      name: 'signInByEmailAndPassword',
      credentials: {
        email: { label: 'email', type: 'text', placeholder: 'e-mail' },
        password: { label: 'password', type: 'password', placeholder: 'password' }
      },
      authorize: async (credentials) => {
        try {
          if (!credentials) return null

          const { data, success } = await authService.postSignIn({ email: 'abc@test.com', password: '12345' }).send()

          ...
        } catch (error) {
          return null
        }
      }
    })
  ],
  ...
}

Could this issue be occurring because the call is being made on the server side? Or is there any configuration required to make this type of request?

I'm grateful for your support and guidance!

[jonathanunes1991]

To complement... I've created an interface to make it easier to consume the requests:

const client = new Client({ url: 'URL' }).setLoggerSeverity(2).setDebug(true)

export const clientPost = <ResponseMapper, ResponseServer>({
  url,
  data,
  options,
  format
}: ClientPost<ResponseMapper, ResponseServer>) =>
  client
    .createRequest<ResponseServer>()({
      method: 'POST',
      endpoint: url,
      options
    })
    .setData(data)
    .setResponseMapper<ResponseMapper>((response) => ({
      ...response,
      data: (format && response?.data ? format(response.data) : response?.data) as ResponseMapper
    }))

const postSignIn = (data: PostSignInRequest) =>
  clientPost<PostSignInResponse, PostSignInServerResponse>({
    url: '/security/account/login',
    data
  })

export const authService = {
  postSignIn
}