After upgrading from node-fetch 2.6.7 to "node-fetch": "^4.0.0-beta.1." I am seeing errors with the execution of fetch.
After running node bin/www, I am able to spin up my node backend server but then when making a request I see the following error now:

// Full paths ellided
{"message":"Error fetching tokens: TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received an instance of Object\n at checkListener (node:events:259:3)\n at ClientRequest.once (node:events:661:3)\n at new ClientRequest (node:_http_client:215:10)\n at Object.request (node:https:353:10)\n at /node_modules/agent-base/patch-core.js:25:22\n at file:///node_modules/node-fetch/src/index.js:94:20\n at new Promise ()\n at fetch (file://node_modules/node-fetch/src/index.js:49:9)

Reproduction
const fetch = (...args) =>
import('node-fetch').then(({ default: fetch }) => fetch(...args));

// Variables values ellided
const getTokens = async (code, redirectUrl) => {
const authString = Basic ${Buffer.from(${config.Id}:${config.secret}).toString('base64')};
const fetchTokenURL = tokenUrl + ?code=${code}&grant_type=auth_code&redirect=${redirect};

try {
let response = await fetch(fetchTokenURL, {
agent: new HttpsProxyAgent(httpProxy),
method: 'POST',
headers: {
Authorization: authString,
Accept: 'application/json',
}
})
let data = await response.json();
return data;
} catch (error) {
logger.info("Error fetching tokens: " + error.stack);
}
}

Steps to reproduce the behavior:

1. Change from const fetch = require("node-fetch"); to const fetch = (...args) =>
   import('node-fetch').then(({ default: fetch }) => fetch(...args));
2. Run node bin/www

Expected behavior

I should be able to hit my target endpoint without issues after import problem was resolved.

Screenshots

Your Environment
alpine linux

Additional context