Feature: Routes page #19240
gregfromstlCI.yml
on: pull_request
optimize_ci
3s
Build Packages
44s
Lint Packages
1m 56s
Unit Tests
49s
Size
3m 23s
Matrix: E2E Tests
Annotations
4 warnings
|
Lint Packages:
apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L77
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 Packages:
apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L86
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 Packages:
apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L79
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 Packages:
apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L111
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
|