eslint-errors.log

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\app\layout.tsx
  4:10  warning  'PwaProvider' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\__tests__\errorDecoder.test.ts
  2:34  warning  'extractErrorMessage' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\__tests__\governance.test.ts
  183:13  warning  'initialBalance' is assigned a value but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\canvas\DelegationFlowGraph.tsx
    8:10  warning  'DelegationNode' is defined but never used                                                                       @typescript-eslint/no-unused-vars
    8:26  warning  'DelegationEdge' is defined but never used                                                                       @typescript-eslint/no-unused-vars
    8:42  warning  'ValidatorStatus' is defined but never used                                                                      @typescript-eslint/no-unused-vars
   25:5   warning  'loading' is assigned a value but never used                                                                     @typescript-eslint/no-unused-vars
   26:5   warning  'error' is assigned a value but never used                                                                       @typescript-eslint/no-unused-vars
  329:6   warning  React Hook useEffect has a missing dependency: 'getNodeStake'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
  527:26  warning  'e' is defined but never used                                                                                    @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\DelegateManager.tsx
  19:33  warning  'isLoading' is assigned a value but never used         @typescript-eslint/no-unused-vars
  25:10  warning  'selectedDelegate' is assigned a value but never used  @typescript-eslint/no-unused-vars
  26:10  warning  'customAddress' is assigned a value but never used     @typescript-eslint/no-unused-vars
  26:25  warning  'setCustomAddress' is assigned a value but never used  @typescript-eslint/no-unused-vars
  27:10  warning  'showCustomModal' is assigned a value but never used   @typescript-eslint/no-unused-vars
  28:10  warning  'showRevokeModal' is assigned a value but never used   @typescript-eslint/no-unused-vars
  57:9   warning  'handleRevoke' is assigned a value but never used      @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\ProposalCard.tsx
  30: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).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\ProposalCard.tsx:30:7
  28 |
  29 |     if (diff <= 0) {
> 30 |       setTimeRemainingText(proposal.status === 'executed' ? 'Executed' : 'Voting Ended');
     |       ^^^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  31 |       return;
  32 |     }
  33 |  react-hooks/set-state-in-effect

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\ProposalDetail.tsx
  38:5  warning  'userAddress' is assigned a value but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\ProposalList.tsx
  8:15  warning  'Proposal' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\governance\VoteHistoryTable.tsx
  6:3  warning  'formatVoteHistoryCsv' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\NetworkEventLog.tsx
  86:36  error  Compilation Skipped: Existing memoization could not be preserved

React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This value was memoized in source but not in compilation output.

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\NetworkEventLog.tsx:86:36
  84 |
  85 |   // Infinite scroll handler
> 86 |   const handleScroll = useCallback(() => {
     |                                    ^^^^^^^
> 87 |     const el = listRef.current
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 88 |     if (!el) return
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 89 |     // Pause auto-scroll when user scrolls away from top
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 90 |     setAutoScroll(el.scrollTop < 80)
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 91 |     // Load more when approaching bottom
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 92 |     if (el.scrollHeight - el.scrollTop - el.clientHeight < 80) {
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 93 |       setVisibleCount((prev) => Math.min(prev + PAGE_SIZE, filtered.length))
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 94 |     }
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 95 |   }, [filtered.length])
     | ^^^^ Could not preserve existing memoization
  96 |
  97 |   // Reset visible count on filter change
  98 |   useEffect(() => {  react-hooks/preserve-manual-memoization
  95:7   error  Compilation Skipped: Existing memoization could not be preserved

React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This dependency may be mutated later, which could cause the value to change unexpectedly.

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\NetworkEventLog.tsx:95:7
  93 |       setVisibleCount((prev) => Math.min(prev + PAGE_SIZE, filtered.length))
  94 |     }
> 95 |   }, [filtered.length])
     |       ^^^^^^^^ This dependency may be modified later
  96 |
  97 |   // Reset visible count on filter change
  98 |   useEffect(() => {                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      react-hooks/preserve-manual-memoization
  99:5   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).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\NetworkEventLog.tsx:99:5
   97 |   // Reset visible count on filter change
   98 |   useEffect(() => {
>  99 |     setVisibleCount(PAGE_SIZE)
      |     ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  100 |   }, [activeFilter])
  101 |
  102 |   return (                                                                                                                                                                                                                                                                                                                        react-hooks/set-state-in-effect

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\NetworkHealthDashboard.tsx
  120:17  error  `'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`  react/no-unescaped-entities

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\network\PeerGraph.tsx
  287:5  warning  Unused eslint-disable directive (no problems were reported from 'react-hooks/exhaustive-deps')

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\slashing\SlashingEventFeed.tsx
  105:10  error  Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\slashing\SlashingEventFeed.tsx:105:10
  103 |     if (!searchQuery.trim()) return displayedEvents
  104 |     const index = searchIndexRef.current
> 105 |     if (!index) return displayedEvents
      |          ^^^^^ Cannot access ref value during render
  106 |     return index.search(searchQuery).map(({ event }) => event)
  107 |   }, [displayedEvents, indexVersion, searchQuery])
  108 |

To initialize a ref only once, check that the ref is null with the pattern `if (ref.current == null) { ref.current = ... }`  react-hooks/refs
  106:12  error  Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\slashing\SlashingEventFeed.tsx:106:12
  104 |     const index = searchIndexRef.current
  105 |     if (!index) return displayedEvents
> 106 |     return index.search(searchQuery).map(({ event }) => event)
      |            ^^^^^ Passing a ref to a function may read its value during render
  107 |   }, [displayedEvents, indexVersion, searchQuery])
  108 |
  109 |   return (                                                                                                                                               react-hooks/refs
  106:12  error  Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\slashing\SlashingEventFeed.tsx:106:12
  104 |     const index = searchIndexRef.current
  105 |     if (!index) return displayedEvents
> 106 |     return index.search(searchQuery).map(({ event }) => event)
      |            ^^^^^^^^^^^^ Passing a ref to a function may read its value during render
  107 |   }, [displayedEvents, indexVersion, searchQuery])
  108 |
  109 |   return (                                                                                                                                        react-hooks/refs

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\supplychain\TierRow.tsx
  92:7  warning  Elements with the ARIA role "treeitem" must have the following attributes defined: aria-selected  jsx-a11y/role-has-required-aria-props

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\validators\DelegationDetailPanel.tsx
  108:11  warning  'minY' is assigned a value but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\components\validators\ExitWorkflowWizard.tsx
  148:19  warning  The ref value 'videoRef.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'videoRef.current' to a variable inside the effect, and use that variable in the cleanup function                          react-hooks/exhaustive-deps
  363:23  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

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\tests\useNetworkHealthDashboard.test.ts
  22:28  warning  '_config' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\tests\useSlashingStream.test.ts
  304:8  warning  'data' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useDoppelgangerDetection.ts
  27:39  warning  'ExpectedNodeConfig' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useSlashingStream.ts
  89:22  warning  The ref value 'receivedIdsRef.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'receivedIdsRef.current' to a variable inside the effect, and use that variable in the cleanup function  react-hooks/exhaustive-deps

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useSorobanStaking.ts
  165:10  warning  'labelFor' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useVirtualizer.ts
   85:5  warning  Unused eslint-disable directive (no problems were reported from 'react-hooks/set-state-in-effect')
  205:5  error    Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useVirtualizer.ts:205:5
  203 |
  204 |   const measureElementWrapper = Object.assign(
> 205 |     (el: Element | null) => {
      |     ^^^^^^^^^^^^^^^^^^^^^^^^^
> 206 |       measureElement(el)
      | ^^^^^^^^^^^^^^^^^^^^^^^^
> 207 |     },
      | ^^^^^^ Passing a ref to a function may read its value during render
  208 |     { attachIndex },
  209 |   )
  210 |  react-hooks/refs
  208:5  error    Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\hooks\useVirtualizer.ts:208:5
  206 |       measureElement(el)
  207 |     },
> 208 |     { attachIndex },
      |     ^^^^^^^^^^^^^^^ Passing a ref to a function may read its value during render
  209 |   )
  210 |
  211 |   return { getVirtualItems, getTotalSize, measureElement: measureElementWrapper }                                                                       react-hooks/refs

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\lib\api\staking.ts
  54:10  warning  'decodeError' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\services\beaconChainService.ts
  364:33  warning  '_baseUrl' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\services\tests\webhookService.test.ts
  14:8  warning  'DeliveryRecord' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\DELL\Desktop\b-191\VeriNode-Frontend\src\services\webSocketManager.ts
  487:29  warning  '_connectionId' is assigned a value but never used  @typescript-eslint/no-unused-vars
  487:49  warning  '_url' is assigned a value but never used           @typescript-eslint/no-unused-vars
  519:27  warning  '_connectionId' is assigned a value but never used  @typescript-eslint/no-unused-vars
  519:47  warning  '_url' is assigned a value but never used           @typescript-eslint/no-unused-vars

✖ 48 problems (10 errors, 38 warnings)
  0 errors and 2 warnings potentially fixable with the `--fix` option.