fix: simplify isNodeExceptionLike check

in some environments, particularly jsdom with jest, Error objects
may not be `instanceof Error` despite being similar and used in the
same way.

To avoid these issues we only need to validate the shape and properties
that might be thrown. In some cases these could false positive, however
it's less likely that they'll false positive, than it is that jest/jsdom
will throw these objects _like_ the errors they represent (guaranteed)

src/node/SetupServerApi.ts

@@ -14,7 +14,7 @@ import { mergeRight } from '~/core/utils/internal/mergeRight'
 import { handleRequest } from '~/core/utils/handleRequest'
 import { devUtils } from '~/core/utils/internal/devUtils'
 import { SetupServer } from './glossary'
-import { isNodeException } from './utils/isNodeException'
+import { isNodeExceptionLike } from './utils/isNodeException'
 
 const DEFAULT_LISTEN_OPTIONS: RequiredDeep<SharedOptions> = {
   onUnhandledRequest: 'warn',
@@ -80,7 +80,10 @@ export class SetupServerApi
            * which won't be printed anyway if `setMaxListeners` fails.
            */
           if (
-            !(isNodeException(error) && error.code === 'ERR_INVALID_ARG_TYPE')
+            !(
+              isNodeExceptionLike(error) &&
+              error.code === 'ERR_INVALID_ARG_TYPE'
+            )
           ) {
             throw error
           }

src/node/utils/isNodeExceptionLike.ts

@@ -0,0 +1,14 @@
+/**
+ * Determines if the given value is shaped like a Node.js exception.
+ * Node.js exceptions have additional information, like
+ * the `code` and `errno` properties.
+ *
+ * In some environments, particularly jsdom/jest these may not
+ * instances of `Error` or its subclasses, despite being similar
+ * to them.
+ */
+export function isNodeExceptionLike(
+  error: unknown,
+): error is NodeJS.ErrnoException {
+  return !!error && typeof error === 'object' && 'code' in error
+}