Skip to content

teamid 콘텐츠 스타일 조정 #101

teamid 콘텐츠 스타일 조정

teamid 콘텐츠 스타일 조정 #101

Triggered via pull request February 25, 2026 03:56
Status Failure
Total duration 35s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
build
Process completed with exit code 2.
build: src/app/(root)/[teamid]/layout.tsx#L1
Cannot find module './_domain/components/Team/SidebarWrapper' or its corresponding type declarations.
build: src/components/Button/domain/FloatingButton/FloatingButton.tsx#L40
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
build: src/components/Button/domain/FilledRoundButton/FilledRoundButton.tsx#L59
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
build: src/components/Button/domain/EnterButton/EnterButton.tsx#L37
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
build: src/components/Button/domain/EditButton/EditButton.tsx#L38
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
build: src/components/Button/domain/EditButton/EditButton.stories.tsx#L268
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
build: src/components/Button/domain/EditButton/EditButton.stories.tsx#L201
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
build: src/components/Button/domain/EditButton/EditButton.stories.tsx#L138
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
build: src/components/Button/domain/ArrowButton/ArrowButton.tsx#L46
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
build: src/app/(root)/layout.tsx#L14
'isPending' is assigned a value but never used
build: src/app/(root)/boards/[articleId]/ArticleDetailPage.tsx#L229
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