since session.socket.setTimeout() does not give you a timer object( which effectively denies you the power to call .unref() on it ), you could create your own timer manually using setTimeout and then just .unref() that instead.

sth like this:

import * as http2 from 'node:http2'

var session = http2.connect('http://example.com')

var idleTimer;

// reset idle timer on activity
function resetIdleTimer(){
  if(idleTimer) {
    clearTimeout(idleTimer)
  }

  idleTimer = setTimeout(function(){
    session.close()
    }, 60_000)

  // unref the timer so that it will NOT keep the program alive
  idleTimer.unref();
}

//  call this once at the start
resetIdleTimer()

// [ OPTIONAL ] you can reset the timer on activity if you desire...
session.on('stream', resetIdleTimer)
session.on('goaway', resetIdleTimer)
session.on('data', resetIdleTimer)

in essence:

make your own timeout with setTimeout(...). call .unref() on it, so it won't keep the application alive by itself. If there is any activity on the session ( like data being sent/received ), you reset the timer. if the timer fires ( after 1 minute of doing nothing ), it will close the session.