How to handle HTTP/2 GOAWAY events / errors

We have code that connects to gmail using http/2 using node16.
From time to time we will receive an HTTP/2 GOAWAY message which results in an error occurring.
I cannot see from the documentation or the exported types any obvious way to hook into handling this event but what I would like to be able to do is monitor this event and handle it appropriately. The other option would be for the library to intercept and handle this event in the internal library way, I suppose.

Error [ERR_HTTP2_GOAWAY_SESSION]: New streams cannot be created after receiving a GOAWAY
at new NodeError (node:internal/errors:371:5)
at ClientHttp2Stream.requestOnConnect (node:internal/http2/core:696:17)
at node:internal/http2/core:1812:68
at Array.forEach (<anonymous>)
at ClientHttp2Session.<anonymous> (node:internal/http2/core:1812:11)
at Object.onceWrapper (node:events:646:26)
at ClientHttp2Session.emit (node:events:538:35)
at ClientHttp2Session.emit (node:domain:475:12)
at emit (node:internal/http2/core:328:3)
at processTicksAndRejections (node:internal/process/task_queues:85:21)

Inizia tracciando il comportamento di ClientHttp2Session e ClientHttp2Stream di Node in relazione allo stack ERR_HTTP2_GOAWAY_SESSION segnalato. Determina se la libreria può esporre un punto di ingresso per la gestione di GOAWAY o recuperare internamente, quindi verifica che il comportamento scelto impedisca la creazione di nuovi stream inutilizzabili e supporti una gestione appropriata da parte del chiamante.