From 97925710bea00497804e91951b2d046c6e474b0e Mon Sep 17 00:00:00 2001
From: Maddy Guthridge <hello@maddyguthridge.com>
Date: Sat, 3 Aug 2024 00:24:03 +1000
Subject: [PATCH] Fix linter errors with TypeScript declarations

ESLint gives a `no-undef` error without the `<T = any>` constraint in the type definition. This PR adds the constraint to help prevent people from getting linting errors from the configuration.
---
 website/docs/getting-started/setup.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/getting-started/setup.md b/website/docs/getting-started/setup.md
index e09e7a03..3a520d78 100644
--- a/website/docs/getting-started/setup.md
+++ b/website/docs/getting-started/setup.md
@@ -69,7 +69,7 @@ import 'vitest';
 declare module 'vitest' {
   interface Assertion<T = any> extends CustomMatchers<T> {}
   interface AsymmetricMatchersContaining<T = any> extends CustomMatchers<T> {}
-  interface ExpectStatic extends CustomMatchers<T> {}
+  interface ExpectStatic<T = any> extends CustomMatchers<T> {}
 }
 ```
 
@@ -99,7 +99,7 @@ import 'vi';
 declare module 'vi' {
   interface Assertion<T = any> extends CustomMatchers<T> {}
   interface AsymmetricMatchersContaining<T = any> extends CustomMatchers<T> {}
-  interface ExpectStatic extends CustomMatchers<T> {}
+  interface ExpectStatic<T = any> extends CustomMatchers<T> {}
 }
 ```