feat: use paymaster for all zk testnet chains #15090
CI.yml
on: pull_request
optimize_ci
9s
Build Packages
1m 41s
Lint Packages
1m 48s
Unit Tests
5m 40s
Size
3m 3s
Matrix: E2E Tests
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
|