@amaxa/nextjs#format: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run format --cache --cache-location node_modules/.cache/.prettiercache exited (1)

Process completed with exit code 1.

Type '{ onChange: (...event: any[]) => void; onBlur: Noop; value: string | null | undefined; disabled?: boolean | undefined; name: "image"; ref: RefCallBack; placeholder: string; }' is not assignable to type 'InputProps'.

Type '{ status: "Verified" | "Unverified" | "Pending"; id: string; name: string | null; email: string; isPublic: boolean; role: "Admin" | "User"; emailVerified: Date | null; image: string | null; }' is not assignable to type '{ status: "Verified" | "Unverified" | "Pending"; id: string; email: string; isPublic: boolean; role: "Admin" | "User"; name?: string | undefined; image?: string | undefined; }'.

Property 'isLoading' does not exist on type 'UseTRPCMutationResult<void, TRPCClientErrorLike<{ input: { description: string; title: string; embedId: string; }; output: void; transformer: true; errorShape: { data: { zodError: typeToFlattenedError<any, string> | null; code: "PARSE_ERROR" | ... 17 more ... | "CLIENT_CLOSED_REQUEST"; httpStatus: number; path?: str...'.

Property 'isLoading' does not exist on type 'UseTRPCMutationResult<void, TRPCClientErrorLike<{ input: { description: string; title: string; embedId: string; }; output: void; transformer: true; errorShape: { data: { zodError: typeToFlattenedError<any, string> | null; code: "PARSE_ERROR" | ... 17 more ... | "CLIENT_CLOSED_REQUEST"; httpStatus: number; path?: str...'.

Object is possibly 'undefined'.

Object is possibly 'undefined'.

Object is possibly 'undefined'.

Argument of type 'TZDate | undefined' is not assignable to parameter of type 'TZDate'.

@amaxa/nextjs#typecheck: command (/home/runner/work/amaxa/amaxa/apps/nextjs) /home/runner/setup-pnpm/node_modules/.bin/pnpm run typecheck exited (2)

Process completed with exit code 2.

@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)

Use an `interface` instead of a `type`

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

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

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

Use an `interface` instead of a `type`

Use an `interface` instead of a `type`

Use an `interface` instead of a `type`

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/

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/

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/

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

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

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

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

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

'Button' is defined but never used. Allowed unused vars must match /^_/u

Unnecessary optional chain on a non-nullish value

Unnecessary optional chain on a non-nullish value

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