feat: implement user onboarding and profile API with Prisma and sessi… #242
Annotations
10 errors and 4 warnings
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/session/config.test.ts#L13
ReferenceError: jest is not defined
❯ tests/session/config.test.ts:13:5
|
|
Run unit tests:
tests/property/validation-properties.test.ts#L2
Error: Cannot find package 'fast-check' imported from '/home/runner/work/Remitwise-Frontend/Remitwise-Frontend/tests/property/validation-properties.test.ts'
❯ tests/property/validation-properties.test.ts:2:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
Run lint:
components/SettingsHeader.tsx#L44
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
|
|
Run lint:
components/FinancialInsightsHeader.tsx#L223
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
|
|
Run lint:
components/FinancialInsightsHeader.tsx#L130
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
|
|
Run lint:
app/transactions/page.tsx#L178
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