Skip to content

Dashboard storybook minor cleanup + fix crashing stories #15087

Dashboard storybook minor cleanup + fix crashing stories

Dashboard storybook minor cleanup + fix crashing stories #15087

Triggered via pull request November 8, 2024 16:04
Status Success
Total duration 3m 22s
Artifacts

CI.yml

on: pull_request
optimize_ci
3s
optimize_ci
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Lint Packages: apps/dashboard/src/app/team/[team_slug]/(team)/page.tsx#L321
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/team/[team_slug]/(team)/page.tsx#L362
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/team/[team_slug]/[project_slug]/page.tsx#L304
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/team/[team_slug]/[project_slug]/page.tsx#L345
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element