feat(test): ⭐️ remove Bun specific imports, so that the tests can be using both Jest and Bun as they are automatically imported in the global scope. However, a Jest polyfill is required in the jest.setup.js because the global Request API (part of the Fetch API) is not available (or not properly configured?)

Author: Ansonhkg

jest.setup.js

@@ -3,3 +3,11 @@ const crypto = require('crypto');
 global.TextEncoder = require('util').TextEncoder;
 global.TextDecoder = require('util').TextDecoder;
 global.crypto = crypto;
+
+// If this is not included, you will get the following error when running it in Jest:
+// (Error) Details: Request is not defined
+// The problem is that Jest is running in a Node.js environment where the global Request API (part of the Fetch API) might not be available or properly configured. Bun, on the other hand, has this API built into its runtime by default, which is why it works.
+const { default: fetch, Request, Response } = require('node-fetch');
+global.fetch = fetch;
+global.Request = Request;
+global.Response = Response;

packages/networks/src/lib/networks/vNaga/common/LitChainClient/apis/rawContractApis/staking/getActiveUnkickedValidatorStructsAndCounts.spec.ts

@@ -1,4 +1,3 @@
-import { beforeAll, describe, expect, test } from 'bun:test';
 import { networkContext, NetworkContext } from '../../../_config';
 import { getActiveUnkickedValidatorStructsAndCounts } from './getActiveUnkickedValidatorStructsAndCounts';