
> temp_project@0.1.0 lint
> eslint


/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/actions/auth-actions.ts
  42:19  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  85:19  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/(auth)/login/page.tsx
  15:3   warning  'InputGroup' is defined but never used                           @typescript-eslint/no-unused-vars
  16:3   warning  'Stack' is defined but never used                                @typescript-eslint/no-unused-vars
  33:19  error    Unexpected any. Specify a different type                         @typescript-eslint/no-explicit-any
  83:20  error    `'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`  react/no-unescaped-entities

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/(auth)/register/page.tsx
  37:19  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/admin/users/page.tsx
  14:3   warning  'IconButton' is defined but never used    @typescript-eslint/no-unused-vars
  24:10  warning  'FaTrash' is defined but never used       @typescript-eslint/no-unused-vars
  32:38  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  36:52  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  77:21  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  84:30  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/page.tsx
  124:53  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  135:39  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  139:50  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/predictions/page.tsx
   13:40  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  139:62  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  158:39  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  168:45  error  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/app/profile/page.tsx
  24:50  error    Unexpected any. Specify a different type                                                                         @typescript-eslint/no-explicit-any
  38:6   warning  React Hook useEffect has a missing dependency: 'fetchProfile'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
  47:17  error    Unexpected any. Specify a different type                                                                         @typescript-eslint/no-explicit-any
  65:17  error    Unexpected any. Specify a different type                                                                         @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/auth/login-form.tsx
   6:3   warning  'Box' is defined but never used                                  @typescript-eslint/no-unused-vars
  10:3   warning  'Stack' is defined but never used                                @typescript-eslint/no-unused-vars
  54:16  error    `'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`  react/no-unescaped-entities

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/auth/register-form.tsx
   6:3  warning  'Box' is defined but never used    @typescript-eslint/no-unused-vars
  10:3  warning  'Stack' is defined but never used  @typescript-eslint/no-unused-vars

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/matches/league-match-list.tsx
   4:10  warning  'Box' is defined but never used           @typescript-eslint/no-unused-vars
  15:42  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  45:49  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/matches/match-card.tsx
   5:19  warning  'FaTrophy' is defined but never used                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         @typescript-eslint/no-unused-vars
   9:47  error    Unexpected any. Specify a different type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     @typescript-eslint/no-explicit-any
  19:17  error    Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/matches/match-card.tsx:19:17
  17 |             try {
  18 |                 const date = new Date(Number(match.mst_utc));
> 19 |                 setFormattedDate(date.toLocaleTimeString("tr-TR", { hour: '2-digit', minute: '2-digit' }));
     |                 ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  20 |             } catch (e) {
  21 |                 setFormattedDate("-");
  22 |             }  react-hooks/set-state-in-effect
  20:22  warning  'e' is defined but never used                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                @typescript-eslint/no-unused-vars
  33:21  warning  Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      @next/next/no-img-element
  51:21  warning  Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      @next/next/no-img-element
  71:21  warning  Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      @next/next/no-img-element

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/predictions/prediction-modal.tsx
   8:3  warning  'Select' is defined but never used  @typescript-eslint/no-unused-vars
  10:3  warning  'Badge' is defined but never used   @typescript-eslint/no-unused-vars

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/components/predictions/prediction-view.tsx
   3:85  warning  'Separator' is defined but never used     @typescript-eslint/no-unused-vars
  12:36  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  45:21  error    Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/contexts/AuthContext.tsx
  39:7  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/Users/piton/Documents/GitHub/Suggest-Bet-FE/src/contexts/AuthContext.tsx:39:7
  37 |
  38 |     if (storedToken && storedUser) {
> 39 |       setToken(storedToken);
     |       ^^^^^^^^ Avoid calling setState() directly within an effect
  40 |       setUser(JSON.parse(storedUser));
  41 |       // Optional: Verify token validity with a /me endpoint if available
  42 |     }  react-hooks/set-state-in-effect

✖ 45 problems (27 errors, 18 warnings)

