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 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/

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

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

React Hook useMemo has missing dependencies: 'anchors', 'handleViewPointClick', 'hasNavigator', 'sectionRef', 'sections', and 'setMapId'. Either include them or remove the dependency array

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

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

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

React Hook useEffect has missing dependencies: 'props' and 'reportVisibility'. Either include them or remove the dependency array. However, 'props' will change when *any* prop changes, so the preferred fix is to destructure the 'props' object outside of the useEffect call and refer to those specific props inside useEffect

Unexpected any. Specify a different type

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element