ut.code(); LearnのremarkTermを実装し、キーワードのポップアップ・リンク #573
na-trium-144node.js.yml
on: pull_request
Matrix: check-docs
Matrix: lint
Matrix: types
Annotations
4 errors and 8 warnings
|
lint (22.x)
Process completed with exit code 1.
|
|
lint (22.x):
app/sidebar.tsx#L7
'LanguageEntry' is defined but never used
|
|
lint (22.x):
app/(docs)/@chat/chat/[chatId]/chatArea.tsx#L11
'PageEntry' is defined but never used
|
|
lint (22.x):
app/(docs)/@chat/chat/[chatId]/chatArea.tsx#L9
'LanguageEntry' is defined but never used
|
|
check-docs (22.x)
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/
|
|
types (22.x)
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/
|
|
lint (22.x)
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/
|
|
lint (22.x):
packages/runtime/src/worker/runtime.tsx#L151
The ref value 'pendingPromises.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'pendingPromises.current' to a variable inside the effect, and use that variable in the cleanup function
|
|
lint (22.x):
app/sidebar.tsx#L121
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
|
|
lint (22.x):
app/navbar.tsx#L61
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
|
|
lint (22.x):
app/footer.tsx#L8
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
|
|
lint (22.x):
app/accountMenu.tsx#L80
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
|