feat(nextjs): caching functions so that it's fast #72
Annotations
9 errors and 11 warnings
Lint
@amaxa/nextjs#lint: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run lint --cache --cache-location node_modules/.cache/.eslintcache exited (1)
|
Lint:
apps/nextjs/src/app/(home)/admin/_components/form.tsx#L40
Use an `interface` instead of a `type`
|
Lint:
apps/nextjs/src/app/(home)/admin/_components/form.tsx#L49
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
|
Lint:
apps/nextjs/src/app/(home)/admin/_components/form.tsx#L54
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
|
Lint:
apps/nextjs/src/app/(home)/admin/_components/table.tsx#L31
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
|
Lint:
apps/nextjs/src/components/calendar-full.tsx#L82
Use an `interface` instead of a `type`
|
Lint:
apps/nextjs/src/components/calendar-full.tsx#L100
Use an `interface` instead of a `type`
|
Lint:
apps/nextjs/src/components/calendar-full.tsx#L108
Use an `interface` instead of a `type`
|
Lint
Process completed with exit code 1.
|
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/(auth)/unverified/page.tsx#L5
'Button' is defined but never used. Allowed unused vars must match /^_/u
|
Lint:
apps/nextjs/src/app/(auth)/unverified/page.tsx#L12
Unnecessary optional chain on a non-nullish value
|
Lint:
apps/nextjs/src/app/(auth)/unverified/page.tsx#L12
Unnecessary optional chain on a non-nullish value
|
Lint:
apps/nextjs/src/app/(auth)/unverified/page.tsx#L16
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/(auth)/unverified/page.tsx#L41
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