fix: update project spotlight links and images across multiple pages … #79
codeaashuAnnotations
10 errors and 11 warnings
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L146
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L83
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L83
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L76
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L76
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L44
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L41
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build:
src/app/blog/imagen-watermark-removal/page.tsx#L36
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build:
src/app/about/page.tsx#L99
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build:
src/app/about/page.tsx#L55
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
lint-and-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint-and-build:
src/app/page.tsx#L211
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-and-build:
src/app/page.tsx#L91
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-and-build:
src/app/image-remover/page.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-and-build:
src/app/image-remover/page.tsx#L64
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-and-build:
src/app/background-remover/page.tsx#L62
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-and-build:
src/app/background-remover/page.tsx#L49
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-and-build:
src/app/api/detect-ai-image/route.ts#L259
'imageBuffer' is defined but never used
|
|
lint-and-build:
src/app/api/detect-ai-image/route.ts#L198
'fileType' is assigned a value but never used
|
|
lint-and-build:
src/app/ai-image-detector/page.tsx#L61
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-and-build:
src/app/ai-image-detector/page.tsx#L48
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
|