feat: add delegation status filter validation (#113) - #226

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Node version =="
node -v || true

echo "== tests/unit/package.json script =="
cat tests/unit/package.json | sed -n '1,80p'

echo "== engine/toolchain hints =="
fd -i 'package.json|.nvmrc|.node-version|.tool-versions|Dockerfile|ci|workflow' . \
  | sed -n '1,120p'

Repository: DelegoLabs/Delego

Length of output: 1145

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== root package.json (engines/scripts) =="
cat package.json | sed -n '1,220p'

echo "== Node/toolchain files =="
fd -HI '(^\.nvmrc$|^\.node-version$|^\.tool-versions$|^Dockerfile$|^package-lock\.json$|^pnpm-lock\.yaml$|^yarn\.lock$)' . -t f

echo "== CI/workflow files =="
fd -HI '(\.github/workflows/.*\.ya?ml$|ci|workflow)' . -t f

echo "== search for node version references =="
rg -n --hidden --glob '!**/node_modules/**' --glob '!**/dist/**' --glob '!**/build/**' -e 'node\s*:?v?(\d+)' -e 'actions/setup-node' -e 'setup-node' -e 'engines' -e '18\.' -e '20\.' -e '22\.' .github . 2>/dev/null || true

Repository: DelegoLabs/Delego

Length of output: 20920

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .github/workflows/ci.yml =="
cat -n .github/workflows/ci.yml | sed -n '1,260p'

Repository: DelegoLabs/Delego

Length of output: 5452

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .github/workflows/ci.yml =="
cat -n .github/workflows/ci.yml | sed -n '1,260p'

Repository: DelegoLabs/Delego

Length of output: 5452

🌐 Web query:

Node.js --experimental-test-module-mocks introduced in which version supported Node 20

💡 Result:

The --experimental-test-module-mocks flag was introduced to the Node.js test runner in version 22.0.0 [1][2]. While it was developed and merged into the main branch in May 2024, it is not supported in Node.js 20 [1][2]. The feature, which enables mock.module functionality in the node:test runner, remains an experimental feature in newer releases [3][4][5]. Because module mocking relies on customization hooks that are also experimental, there have been no plans to backport this feature to Node.js 20 [2]. Users attempting to use mock.module in Node.js 20 will find the property undefined [6].

Citations:

• 1: nodejs/node@7a67ecf161
• 2: test_runner: support module mocking nodejs/node#52848
• 3: https://nodejs.org/api/test.html
• 4: https://nodejs.org/docs/v22.11.0/api/test.html
• 5: doc: cover --experimental-test-module-mocks flag nodejs/node#55021
• 6: https://stackoverflow.com/questions/79004444/mock-module-is-undefined-in-node-js-v22-9-0-nodetest-module

🌐 Web query:

Node.js --experimental-test-module-mocks introduced in which version supported Node 20

💡 Result:

The --experimental-test-module-mocks flag was introduced in Node.js v22.3.0 [1][2][3]. While there were discussions regarding backporting this feature to Node.js 20.x, it was explicitly marked as "backport-blocked" in the Node.js repository [4], and the feature is not natively supported in Node.js 20 versions. To use module mocking via the node:test module, you must use a Node.js version that includes the feature, starting from v22.3.0 [5][1].

Citations:

• 1: nodejs/node@5e25c2a79a
• 2: https://bhdouglass.com/blog/nodejs-test-runner/
• 3: doc: cover --experimental-test-module-mocks flag nodejs/node#55021
• 4: test_runner: support module mocking nodejs/node#52848
• 5: https://nodejs.org/docs/v22.11.0/api/test.html

🌐 Web query:

site:nodejs.org --experimental-test-module-mocks Node.js release notes

💡 Result:

The --experimental-test-module-mocks command-line flag is a feature in Node.js that enables module mocking within the built-in test runner [1][2]. Key details regarding this flag: Purpose: It allows developers to mock the exports of ECMAScript modules (ESM), CommonJS modules (CJS), and Node.js built-in modules during testing [2][3]. Stability: This feature is currently marked as having a stability index of 1.0 (Early development) [1]. Availability: The flag was introduced in Node.js v22.3.0 and v20.18.0 [1]. Usage: To utilize module mocking, you must start the Node.js process with this flag enabled [2][3]. If your environment uses the Node.js Permission Model, using this feature also requires the --allow-worker flag [1]. Implementation: Within tests, module mocking is accessed via the mock.module method provided by the test runner [2][4][5]. It is recommended to perform imports of the module to be tested dynamically after the mock has been configured to ensure the mock is correctly applied [4][5]. For detailed usage, you can refer to the official Node.js documentation for the test runner module [6][2].

Citations:

• 1: https://nodejs.org/api/cli.html
• 2: https://nodejs.org/download/release/v23.6.1/docs/api/test.html
• 3: https://nodejs.org/docs/v22.11.0/api/test.html
• 4: https://nodejs.org/learn/test-runner/using-test-runner
• 5: https://nodejs.org/learn/test-runner/mocking
• 6: https://nodejs.org/api/test.html

🌐 Web query:

site:nodejs.org v20.18.0 experimental-test-module-mocks node:test

💡 Result:

In Node.js v20.18.0, the --experimental-test-module-mocks command-line flag was introduced to enable experimental module mocking support in the built-in test runner [1][2][3]. Key details regarding this feature include: Experimental Status: As of its introduction, this feature is classified as Early Development (stability index 1.0) [2][4]. Usage: To use this feature, you must explicitly pass the --experimental-test-module-mocks flag when running your Node.js process [2][5]. If you are also using the Node.js Permission Model, this feature requires that you additionally pass the --allow-worker flag [2]. Functionality: This flag enables the mock.module(specifier[, options]) API within the node:test module [4][3]. This API allows for mocking the exports of ECMAScript modules (ESM), CommonJS modules (CJS), and Node.js built-in modules [4]. Important Implementation Note: When mocking modules, the mock must be configured before the module being mocked is imported or required by the code under test [6][5]. Because of this, it is common practice to use dynamic import statements after the mock has been set up to ensure the mocked version of the module is loaded instead of the original [6][5]. The mock.module API supports several configuration options, including: - cache: A boolean indicating whether to cache the mock module (default is false) [4]. - defaultExport: An optional value to serve as the module's default export [4]. - namedExports: An optional object to define the module's named exports [4]. This feature was part of the Node.js v20.18.0 release, which included several related commits to support module detection and refactor the mocking implementation [3][7].

Citations:

• 1: https://nodejs.org/download/release/v20.18.0/docs/api/all.html
• 2: https://nodejs.org/api/cli.html
• 3: https://nodejs.org/en/blog/release/v20.18.0
• 4: https://nodejs.org/docs/latest-v20.x/api/test.html
• 5: https://nodejs.org/learn/test-runner/using-test-runner
• 6: https://nodejs.org/learn/test-runner/mocking
• 7: https://nodejs.org/es/blog/release/v20.18.0

🌐 Web query:

site:nodejs.org "experimental-test-module-mocks" "v20.18.0" "v22.3.0"

💡 Result:

The flag --experimental-test-module-mocks is a Node.js command-line option used to enable module mocking functionality within the built-in test runner [1][2]. This feature was added in Node.js version 22.3.0 and backported to version 20.18.0 [1]. When enabled, it allows developers to mock the exports of ECMAScript modules (ESM), CommonJS modules (CJS), JSON modules, and Node.js built-in modules during testing [3][2]. This is typically achieved using the mock.module method provided by the node:test module [3][2]. If you are using the Permission Model in Node.js, using this feature also requires passing the --allow-worker flag [1].

Citations:

• 1: https://nodejs.org/api/cli.html
• 2: https://r2.nodejs.org/docs/v22.17.1/api/test.html
• 3: https://nodejs.org/download/release/latest-v20.x/docs/api/test.html