TokenProviderMiddleware does not use custom fetch()

[denisw]

Checklist

• [X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• [X] I have looked into the API documentation and have not found a suitable solution or answer.
• [X] I have searched the issues and have not found a suitable solution or answer.
• [X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• [X] I agree to the terms within the Auth0 Code of Conduct.

Description

When I pass a custom fetch implementation to the ManagementClient constructor, then it is not forwarded to and used by the TokenProviderMiddleware created in the ManagementClient constructor.

Reproduction

import * as auth0 from 'auth0';

function customFetch(url, init) {
  console.log(url);
  return fetch(url, init);
}

const client = new auth0.ManagementClient({
  domain: 'https://example.us.auth0.com',
  clientId: 'dummy',
  clientSecret: 'dummy',
  fetch: customFetch,
});

await client.users.getAll({});

When running the script above, we should see the URL of the token endpoint to be printed, but because the TokenProviderMiddleware uses the global fetch and not the custom one, it doesn't.

Additional context

No response

node-auth0 version

4.0.0

Node.js version

18.17.0

[frederikprijck]

Thanks, I can see what's causing that. I will look into providing a fix.

[frederikprijck]

Fixed and released as 4.0.1.

Thanks for reporting, feel free to let us know if there would be any other issues.

[denisw]

Wow, that was quick! Thank you. 🙂