Optional chain expressions can return undefined by design - using a non-null assertion is unsafe and wrong

Optional chain expressions can return undefined by design - using a non-null assertion is unsafe and wrong

'isExcludedNode' is defined but never used

Unexpected console statement

Unexpected use of 'isNaN'. Use Number.isNaN instead https://github.com/airbnb/javascript#standard-library--isnan

Unexpected use of 'isNaN'. Use Number.isNaN instead https://github.com/airbnb/javascript#standard-library--isnan

Unary operator '++' used

Expected '===' and instead saw '=='

Expected '===' and instead saw '=='

'ReactZoomPanPinchContext' is defined but never used

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache/restore@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

React Hook useEffect has missing dependencies: 'cleanupWindowEvents' and 'init'. Either include them or remove the dependency array

Unexpected unnamed function

Unexpected unnamed function

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

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