Version Packages #15075
jnsdlsCI.yml
on: pull_request
optimize_ci
2s
Build Packages
1m 27s
Lint Packages
2m 1s
Unit Tests
4m 52s
Size
4m 27s
Matrix: E2E Tests
Annotations
2 errors and 4 warnings
|
Unit Tests
***#test: command (/home/runner/work/js/js/packages/***) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
|
|
Unit Tests
Process completed with exit code 1.
|
|
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
|