Optimize the plugin system #498
lint.yml
on: pull_request
Ruff Lint & Format
15s
Frontend Lint
28s
Annotations
12 warnings
|
Ruff Lint & Format
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-python@v5, astral-sh/setup-uv@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/
|
|
Frontend Lint
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, pnpm/action-setup@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/
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-session/BotSessionMonitor.tsx#L225
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-log/view/BotLogListComponent.tsx#L145
React Hook useCallback received a function whose dependencies are unknown. Pass an inline function instead
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-log/view/BotLogListComponent.tsx#L107
React Hook useEffect has a missing dependency: 'manager'. Either include it or remove the dependency array
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-log/view/BotLogListComponent.tsx#L59
React Hook useEffect has missing dependencies: 'initComponent' and 'onDestroy'. Either include them or remove the dependency array
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-log/view/BotLogCard.tsx#L171
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-form/BotForm.tsx#L510
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-form/BotForm.tsx#L482
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-form/BotForm.tsx#L135
React Hook useEffect has a missing dependency: 'setBotFormValues'. Either include it or remove the dependency array
|
|
Frontend Lint:
web/src/app/home/bots/components/bot-card/BotCard.tsx#L30
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Frontend Lint:
web/src/app/auth/space/callback/page.tsx#L156
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|