팀 생성하기 페이지 퍼블리싱 및 관련 로직 추가 #62
JieunsseAnnotations
8 errors and 10 warnings
|
build
Process completed with exit code 2.
|
|
build:
src/app/providers.tsx#L4
Cannot find module '@tanstack/react-query' or its corresponding type declarations.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L17
Parameter 'name' implicitly has an 'any' type.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L16
Binding element 'group' implicitly has an 'any' type.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L4
Cannot find module '@tanstack/react-query' or its corresponding type declarations.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L3
Cannot find module '@/shared/queries/groups/queryKeys' or its corresponding type declarations.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L2
Cannot find module '@/shared/queries/groups/useCreateGroupMutation' or its corresponding type declarations.
|
|
build:
src/app/addteam/_hooks/useCreateTeam.ts#L1
Cannot find module '@/shared/apis/groups/types' or its corresponding type declarations.
|
|
build:
src/components/Button/domain/GnbAddButton/GnbAddButton.tsx#L36
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/FloatingButton/FloatingLikeButton.tsx#L54
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/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
|