This is a bug with Node.js, described in https://github.com/nodejs/node/issues/57669. Let's see how the discussion on the Node.js repository goes before deciding on any workaround.