add pagination and search bar to the invoice table #7
StephDietzAnnotations
1 error and 10 warnings
|
test
Process completed with exit code 1.
|
|
test:
basics/assets-metadata-css-starter/pages/index.js#L60
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
|
|
test:
basics/basics-final/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
|
|
test:
basics/demo/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
|
|
test:
basics/learn-starter/pages/index.js#L59
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
|
|
test:
basics/navigate-between-pages-starter/pages/index.js#L59
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
|
|
test:
basics/typescript-final/pages/api/hello.ts#L3
Assign arrow function to a variable before exporting as module default
|
|
test:
dashboard/15-final/app/ui/customers/table.tsx#L44
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
|
|
test:
dashboard/15-final/app/ui/dashboard/latest-invoices.tsx#L28
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
|
|
test:
dashboard/15-final/app/ui/hero.tsx#L23
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
|
|
test:
dashboard/15-final/app/ui/invoices/table.tsx#L121
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
|