Implement block action registry and analysis panel with in-place comp… #357
deploy-frontend-aws.yml
on: push
Lint & Code Quality
49s
Security Audit
27s
Secret Scan (Gitleaks)
46s
Build Verification
47s
Deploy to AWS
1m 34s
Annotations
11 warnings
|
Lint & Code Quality
Found console.log statements - consider removing for production
|
|
Lint & Code Quality:
frontend/src/components/app/RouteLoadingSkeleton.tsx#L43
'_files' is defined but never used
|
|
Lint & Code Quality:
frontend/src/components/app/RouteLoadingSkeleton.tsx#L43
'_text' is defined but never used
|
|
Lint & Code Quality:
frontend/src/components/app/OnboardingModal.tsx#L386
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 & Code Quality:
frontend/src/components/app/MessageList.tsx#L72
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 & Code Quality:
frontend/src/components/app/ChatInput.tsx#L493
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 & Code Quality:
frontend/src/components/app/ChatInput.tsx#L84
'isPreparing' is assigned a value but never used
|
|
Lint & Code Quality:
frontend/src/components/app/AppContentRouter.tsx#L128
React Hook useEffect has missing dependencies: 'conversation' and 'upsertConversation'. Either include them or remove the dependency array
|
|
Lint & Code Quality:
frontend/src/app/demo/page.tsx#L376
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 & Code Quality:
frontend/src/app/demo/page.tsx#L305
Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
Lint & Code Quality:
frontend/src/app/demo/page.tsx#L4
'Play' is defined but never used
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
frontend-audit-report
Expired
|
321 Bytes |
sha256:6983f447ce78fef9b13b565371cdb35fc1c03173f58feb9e39aa7ac2e813940d
|
|
|
frontend-build
Expired
|
41.4 MB |
sha256:7f261c94d95a804946576a099faf733c208e215ef43df3e02cf949dffcad0fc9
|
|
|
frontend-gitleaks-report
Expired
|
6.53 KB |
sha256:57872f89c58401eae4d439e99b671d0931ebc14f9691634c95df6c32060ec4f8
|
|