Process completed with exit code 2.

Parameter 'item' implicitly has an 'any' type.

Property 'label' does not exist on type 'Readonly<ChartTooltipContentProps>'.

Property 'payload' does not exist on type 'Readonly<ChartTooltipContentProps>'.

Interface 'ChartTooltipContentProps' cannot simultaneously extend types 'HTMLAttributes<HTMLDivElement>' and 'TooltipProps<ValueType, NameType>'.

Module '"recharts"' has no exported member 'ValueType'.

Module '"recharts"' has no exported member 'NameType'.

Type '(value: number) => [string, string]' is not assignable to type 'Formatter<ValueType, NameType> & ((value: ValueType, name: NameType, item: TooltipPayloadEntry, index: number, payload: TooltipPayload) => ReactNode | [...])'.

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

'_' is defined but never used

Unexpected any. Specify a different type

'_error' is defined but never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, peter-evans/create-or-update-comment@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The 'userRoles' logical expression could make the dependencies of useMemo Hook (at line 161) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'userRoles' in its own useMemo() Hook

The 'kits' logical expression could make the dependencies of useMemo Hook (at line 43) change on every render. To fix this, wrap the initialization of 'kits' in its own useMemo() Hook

React Hook useEffect has a missing dependency: 'keycloak'. Either include it or remove the dependency array

React Hook useCallback has a missing dependency: 'onSectionComplete'. Either include it or remove the dependency array. If 'onSectionComplete' changes too often, find the parent component that defines it and wrap that definition in useCallback

The 'sections' logical expression could make the dependencies of useMemo Hook (at line 416) change on every render. To fix this, wrap the initialization of 'sections' in its own useMemo() Hook

React Hook useEffect has a missing dependency: 'onResultCountChange'. Either include it or remove the dependency array. If 'onResultCountChange' changes too often, find the parent component that defines it and wrap that definition in useCallback

React Hook useEffect has a missing dependency: 'selectedFolderId'. Either include it or remove the dependency array

React Hook useEffect has missing dependencies: 'isAdminContext', 'isContentManager', 'isOrgManager', and 'keycloak.token'. Either include them or remove the dependency array

React Hook useCallback has an unnecessary dependency: 'keycloak.token'. Either exclude it or remove the dependency array