Update tests to work with newest node LTS

[CluEleSsUK]

All the jest-http-mock tests fail on the latest LTS version of node, as they appear to use actual fetch rather than the mock (presumably because fetch is now available on LTS)

[paschal533]

Hi @CluEleSsUK, I'm interested in working on this issue. I'm from PLDG, and I have experience with Node.js and Jest. Could you please assign this issue to me?

[CluEleSsUK]

done @paschal533 - thanks for your help!!

[paschal533]

Hi @CluEleSsUK

I cloned the project and ran the tests on Node.js version 22.13.0. The only tests that initially failed were:

test('Beacon fetching works with testnet', async () => {
  await endToEndTest('https://pl-us.testnet.drand.sh');
});

test('Beacon fetching works with mainnet', async () => {
  await endToEndTest('https://api.drand.sh');
});

However, after adding testTimeout: 30000 to the jest.config.ts file, all tests passed successfully. Here's the updated configuration:

module.exports = {
  preset: "ts-jest",
  testEnvironment: "node",
  testTimeout: 30000,
  transform: {
    "^.+\\.ts?$": "ts-jest",
  },
  transformIgnorePatterns: ["<rootDir>/node_modules/"],
};

Could you confirm if the issue lies elsewhere or if there’s additional context I might be missing? I'd be happy to investigate further if needed.

[CluEleSsUK]

interesting! Could you try updating the GitHub action to run on a newer version and see if it builds successfully?
I don’t have any extra context other than it failed when I tried it heh

[paschal533]

Hi @CluEleSsUK

I’ve updated the GitHub Action to use Node.js version 22.x and created a pull request to test the pipeline. The tests ran successfully with this change, including the previously failing ones.

Would you like me to proceed with any further updates or optimizations?