fix: prettier errors #62
not-aniAnnotations
3 errors and 13 warnings
|
typecheck
Cannot find module '@amaxa/db/schema' or its corresponding type declarations.
|
|
typecheck
@amaxa/website#typecheck: command (/home/runner/work/amaxa/amaxa/apps/website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run typecheck exited (2)
|
|
typecheck
Process completed with exit code 2.
|
|
format
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
typecheck
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint:
apps/website/src/app/(marketing)/about-us/_components/our-partners.tsx#L47
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:
apps/website/src/app/(marketing)/about-us/_components/our-partners.tsx#L62
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:
apps/website/src/app/(marketing)/team/page.tsx#L89
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:
apps/website/src/components/platform-hero.tsx#L48
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:
apps/website/src/components/platform-hero.tsx#L53
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:
apps/nextjs/src/app/(dashboard)/project/[id]/(root)/calendar/_components/project-calendar.tsx#L30
Unexpected any. Specify a different type
|
|
lint:
apps/nextjs/src/app/(dashboard)/project/[id]/(root)/calendar/_components/project-calendar.tsx#L31
Unexpected any. Specify a different type
|
|
lint:
apps/nextjs/src/app/(dashboard)/project/[id]/(root)/calendar/_components/project-calendar.tsx#L111
Unsafe assignment of an `any` value
|
|
lint:
apps/nextjs/src/app/(dashboard)/project/[id]/(root)/calendar/_components/project-calendar.tsx#L112
Unsafe assignment of an `any` value
|
|
lint:
apps/nextjs/src/app/(dashboard)/project/[id]/(root)/calendar/_components/project-calendar.tsx#L121
Unsafe assignment of an `any` value
|