.github/workflows/tests.yml (1)

22-23: Consider upgrading actions/setup-node to v4.

actions/checkout@v4 is used on line 19, but actions/setup-node@v2 is outdated. For consistency and to benefit from bug fixes and performance improvements, consider upgrading to v4.

Suggested fix

      - name: Setup Node.js
-        uses: actions/setup-node@v2
+        uses: actions/setup-node@v4
        with:
          node-version: '22'

package.json (1)

60-62: Consider renaming build script to clarify its purpose.

The build script name typically implies compilation/transpilation, but here it runs tests and benchmarks. This could be confusing for contributors. Consider a more descriptive name like ci or check.

That said, this is a minor naming concern and the current approach is functional.

benchmarks/config/default.mjs (1)

1-9: Minor: Inconsistent property quoting style.

EnvOverride uses unquoted keys while AnotherModule uses quoted keys. Consider using a consistent style throughout for readability.

Suggested fix

 export default {
     EnvOverride: {
         parm_number_1: "from_default_mjs",
         parm2: 22
     },
-    "AnotherModule": {
-        "parm10": "value10"
+    AnotherModule: {
+        parm10: "value10"
     }
 };

benchmarks/index.js (1)

29-38: Unused variables val may cause linter warnings.

The val variables are assigned but never read, which could trigger ESLint no-unused-vars warnings. While this is intentional for benchmarking purposes, consider using a void expression or disabling the lint rule locally.

Suggested fix to suppress warnings

   suite.add('get', (config, keys) => {
     for (const key of keys) {
-      let val = config[key];
+      void config[key];
     }
   });
 
   suite.add('get()', (config, keys) => {
     for (const key of keys) {
-      let val = config.get(key);
+      void config.get(key);
     }
   });