Use a more agnostic test approach to avoid breaking changes across Node versions

Author: dacharyc

package.json

@@ -16,7 +16,7 @@
     }
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=20.0.0"
   },
   "scripts": {
     "clean": "rimraf dist coverage .nyc_output",

tests/oasprey/matchers/toSatisfyApiSpec/__snapshots__/toSatisfyApiSpec.test.ts.snap

@@ -65,7 +65,9 @@ describe.each(
 
       it('fails', () => {
         const assertion = () => expect(res).toSatisfyApiSpec();
-        expect(assertion).toThrowErrorMatchingSnapshot();
+        expect(assertion).toThrow(/expected.*received.*to satisfy a '204' response defined for endpoint 'GET \/some\/path'/);
+        expect(assertion).toThrow(/received.*had request path.*\/some\/path.*but your API spec has no matching path/);
+        expect(assertion).toThrow(/Paths found in API spec:/);
       });
 
       it('fails when using .not', () => {

tests/oasprey/matchers/toSatisfyApiSpec/toSatisfyApiSpec.test.ts

@@ -75,7 +75,8 @@ describe('loadSpec(filepathOrObject)', () => {
         ),
       );
       const func = () => loadSpec(pathToApiSpec);
-      expect(func).toThrow(`${invalidArgErrorMessage}Invalid YAML or JSON:\n`);
+      // In Node.js v22+, the error message format changed from "Invalid YAML or JSON" to the actual filesystem error
+      expect(func).toThrow(invalidArgErrorMessage);
     });
   });