Bump next from 15.3.2 to 15.5.2 in /dashboard/final-example #638
Annotations
10 warnings
|
Run tests:
seo/pages/index.js#L25
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
|
|
Run tests:
seo/pages/index.js#L25
A font-display parameter is missing (adding `&display=optional` is recommended). See: https://nextjs.org/docs/messages/google-font-display
|
|
Run tests:
seo/demo/pages/index.js#L23
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
|
|
Run tests:
seo/demo/pages/index.js#L23
A font-display parameter is missing (adding `&display=optional` is recommended). See: https://nextjs.org/docs/messages/google-font-display
|
|
Run tests:
basics/typescript-final/pages/api/hello.ts#L3
Assign arrow function to a variable before exporting as module default
|
|
Run tests:
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
|
|
Run tests:
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
|
|
Run tests:
basics/demo/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
|
|
Run tests:
basics/basics-final/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
|
|
Run tests:
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
|
Loading