Modified Routing Options in Index Page#177
Open
Jaswanth-Kumar-2007 wants to merge 2 commits into
Open
Annotations
11 warnings
|
Complete job
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/
|
|
Run npm run lint:
src/pages/questions/[id].tsx#L81
React Hook useEffect has an unnecessary dependency: 'auth.currentUser'. Either exclude it or remove the dependency array. Outer scope values like 'auth.currentUser' aren't valid dependencies because mutating them doesn't re-render the component
|
|
Run npm run lint:
src/pages/notifications.tsx#L35
React Hook useEffect has a missing dependency: 'fetchNotifications'. Either include it or remove the dependency array
|
|
Run npm run lint:
src/pages/leaderboard.tsx#L314
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run npm run lint:
src/pages/leaderboard.tsx#L197
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run npm run lint:
src/pages/_app.tsx#L63
React Hook useEffect has a missing dependency: 'publicRoutes'. Either include it or remove the dependency array
|
|
Run npm run lint:
src/constants/boilerplate.tsx#L98
Assign object to a variable before exporting as module default
|
|
Run npm run lint:
src/components/quiz/StartScreen.tsx#L176
React Hook useEffect has missing dependencies: 'activeUser?.username', 'authUser', 'isMatchmaking', 'selectedDifficulty', 'selectedTopic', and 'socket'. Either include them or remove the dependency array
|
|
Run npm run lint:
src/common/components/Ques/QuesList.tsx#L357
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run npm run lint:
src/common/components/Profile/Profile.tsx#L307
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run npm run lint:
src/common/components/Profile/Profile.tsx#L246
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
|
background
wait
wait-all
cancel
parallel
Loading