feat: exclude iconlogo directory from TypeScript compilation #52
codeaashuAnnotations
10 errors and 11 warnings
|
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:
iconlogo/src/features/editor/TestimonialTicker.tsx#L48
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
iconlogo/src/features/editor/TestimonialTicker.tsx#L48
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
lint-and-build:
iconlogo/src/features/editor/FeedbackButton.tsx#L119
`'` 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:
iconlogo/src/routes/__root.tsx#L55
Do not use `<head>` element. Use `<Head />` from `next/head` instead. See: https://nextjs.org/docs/messages/no-head-element
|
|
lint-and-build:
iconlogo/src/routes/__root.tsx#L12
'SITE_URL' is defined but never used
|
|
lint-and-build:
iconlogo/src/integrations/tanstack-query/devtools.tsx#L3
Assign object to a variable before exporting as module default
|
|
lint-and-build:
iconlogo/src/features/landing/HeroSection.tsx#L99
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:
iconlogo/src/features/landing/HeroSection.tsx#L27
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:
iconlogo/src/features/editor/MobileTopBar.tsx#L36
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:
iconlogo/src/features/editor/InfoModal.tsx#L30
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:
iconlogo/src/features/editor/InfoModal.tsx#L1
'Label' is defined but never used
|
|
lint-and-build:
iconlogo/src/features/editor/AppShell.tsx#L113
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:
iconlogo/src/features/editor/AppShell.tsx#L81
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
|