Process completed with exit code 1.

Error: [vitest] No "SpotifyRateLimitError" export is defined on the "@/lib/spotify" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/spotify"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ POST src/app/api/playlists/[playlistId]/tracks/route.ts:390:24 ❯ src/app/api/playlists/[playlistId]/tracks/route.test.ts:426:22

Error: [vitest] No "SpotifyRateLimitError" export is defined on the "@/lib/spotify" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/spotify"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ POST src/app/api/playlists/[playlistId]/tracks/route.ts:390:24 ❯ src/app/api/playlists/[playlistId]/tracks/route.test.ts:402:22

TypeError: Cannot read properties of undefined (reading 'toISOString') ❯ src/app/api/playlists/route.ts:54:67 ❯ Module.GET src/app/api/playlists/route.ts:44:30 ❯ src/app/api/playlists/__tests__/route.test.ts:261:22

AssertionError: expected [ 'newTrack', 'newSwaplist', …(5) ] to have a length of 6 but got 7 - Expected + Received - 6 + 7 ❯ src/lib/notification-prefs.test.ts:145:32

Error: [vitest] No "notifyCircleMembers" export is defined on the "@/lib/notifications" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/notifications"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ src/app/api/playlists/route.ts:295:43 This error originated in "src/app/api/playlists/__tests__/route.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.

File has too many lines (1083). Maximum allowed is 300

File has too many lines (315). Maximum allowed is 300

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

File has too many lines (546). Maximum allowed is 300

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

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

File has too many lines (410). Maximum allowed is 300

File has too many lines (363). Maximum allowed is 300

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