> uptime-sentinel@0.2.2 lint > eslint E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\app\api\dashboard\stats\route.ts 22:13 error 'userId' is never reassigned. Use 'const' instead prefer-const E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\app\settings\page.tsx 43:18 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). E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\app\settings\page.tsx:43:18 41 | useEffect(() => { 42 | const tab = searchParams.get('tab'); > 43 | if (tab) setActiveTab(tab); | ^^^^^^^^^^^^ Avoid calling setState() directly within an effect 44 | }, [searchParams]); 45 | 46 | if (status === 'loading' || !session) { react-hooks/set-state-in-effect E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCDisplay.tsx 3:31 error 'useCallback' is defined but never used unused-imports/no-unused-imports 5:39 error 'Clock' is defined but never used unused-imports/no-unused-imports 5:56 error 'X' is defined but never used unused-imports/no-unused-imports 5:70 error 'Minimize2' is defined but never used unused-imports/no-unused-imports 6:43 error 'RefreshCw' is defined but never used unused-imports/no-unused-imports 7:27 error 'ChevronDown' is defined but never used unused-imports/no-unused-imports 8:5 error 'BarChart3' is defined but never used unused-imports/no-unused-imports 8:16 error 'ShieldCheck' is defined but never used unused-imports/no-unused-imports 8:36 error 'Info' is defined but never used unused-imports/no-unused-imports 8:42 error 'Smartphone' is defined but never used unused-imports/no-unused-imports 9:45 error 'MousePointer2' is defined but never used unused-imports/no-unused-imports 46:12 warning 'initialTheme' is defined but never used. Allowed unused args must match /^_/u unused-imports/no-unused-vars 56:12 warning 'isFullscreen' is assigned a value but never used. Allowed unused vars must match /^_/u unused-imports/no-unused-vars 60:12 warning 'isRefreshing' is assigned a value but never used. Allowed unused vars must match /^_/u unused-imports/no-unused-vars 60:26 warning 'setIsRefreshing' is assigned a value but never used. Allowed unused vars must match /^_/u unused-imports/no-unused-vars 69:12 warning 'displayScale' is assigned a value but never used. Allowed unused vars must match /^_/u unused-imports/no-unused-vars 69:26 warning 'setDisplayScale' is assigned a value but never used. Allowed unused vars must match /^_/u unused-imports/no-unused-vars 74:24 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). E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCDisplay.tsx:74:24 72 | useEffect(() => { 73 | const savedView = localStorage.getItem('noc_view_mode') as 'grid' | 'map'; > 74 | if (savedView) setViewMode(savedView); | ^^^^^^^^^^^ Avoid calling setState() directly within an effect 75 | 76 | const savedTheme = localStorage.getItem('noc_theme_mode') as ThemeMode; 77 | if (savedTheme) setThemeMode(savedTheme); react-hooks/set-state-in-effect 100:13 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). E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCDisplay.tsx:100:13 98 | useEffect(() => { 99 | if (sseData) { > 100 | setMonitors(sseData.monitors.map((m) => ({ | ^^^^^^^^^^^ Avoid calling setState() directly within an effect 101 | id: m.id, 102 | name: m.name, 103 | type: m.type, react-hooks/set-state-in-effect 457:109 warning 'regIdx' is defined but never used. Allowed unused args must match /^_/u unused-imports/no-unused-vars 575:98 error Unexpected any. Specify a different type @typescript-eslint/no-explicit-any E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCMapView.tsx 5:17 error 'Wifi' is defined but never used unused-imports/no-unused-imports 5:23 error 'WifiOff' is defined but never used unused-imports/no-unused-imports 5:32 error 'AlertTriangle' is defined but never used unused-imports/no-unused-imports 5:47 error 'ChevronRight' is defined but never used unused-imports/no-unused-imports 5:94 error 'Info' is defined but never used unused-imports/no-unused-imports 6:29 error 'polyline' is defined but never used unused-imports/no-unused-imports 104:51 warning 'isDark' is defined but never used. Allowed unused args must match /^_/u unused-imports/no-unused-vars 104:103 warning 'onMonitorClick' is defined but never used. Allowed unused args must match /^_/u unused-imports/no-unused-vars 112:23 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). E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCMapView.tsx:112:23 110 | const [activeProbe, setActiveProbe] = useState(null); 111 | > 112 | useEffect(() => { setMounted(true); }, []); | ^^^^^^^^^^ Avoid calling setState() directly within an effect 113 | 114 | useEffect(() => { 115 | if (selectedFilterCountry && selectedFilterCountry !== 'all') { react-hooks/set-state-in-effect 118:17 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). E:\Running Apps\Network-Monitor-App\uptime-sentinel\src\components\noc\NOCMapView.tsx:118:17 116 | const coords = COUNTRY_COORDS[selectedFilterCountry]; 117 | if (coords) { > 118 | setZoomTarget(coords); | ^^^^^^^^^^^^^ Avoid calling setState() directly within an effect 119 | setZoomTrigger(prev => prev + 1); 120 | } 121 | } else if (selectedFilterCountry === 'all') { react-hooks/set-state-in-effect 339:113 error Unexpected any. Specify a different type @typescript-eslint/no-explicit-any Ô£û 34 problems (25 errors, 9 warnings) 18 errors and 0 warnings potentially fixable with the `--fix` option.