Process completed with exit code 1.

Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The ref value 'refreshWaiters.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'refreshWaiters.current' to a variable inside the effect, and use that variable in the cleanup function

'secondToast' is assigned a value but never used

'firstToast' is assigned a value but never used

'toast' is assigned a value but never used

'cancelSettlement' is defined but never used

'within' is defined but never used

The 'pools' conditional could make the dependencies of useMemo Hook (at line 85) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook

The 'pools' conditional could make the dependencies of useMemo Hook (at line 81) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook

The 'pools' conditional could make the dependencies of useMemo Hook (at line 77) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook