Cannot find module '@auth/drizzle-adapter' #983
-
|
Thanks for building this library! I'm wondering if there's any setup for Jest & Next.js required that's not documented because the readme jumps straight into installing I've followed the guide at https://nextjs.org/docs/app/building-your-application/testing/jest but using import type { Config } from "jest";
import nextJest from "next/jest.js";
const createJestConfig = nextJest({
// Provide the path to your Next.js app to load next.config.js and .env files in your test environment
dir: "./",
});
// Add any custom config to be passed to Jest
const config: Config = {
coverageProvider: "v8",
testEnvironment: "node",
// Add more setup options before each test is run
// setupFilesAfterEnv: ['<rootDir>/jest.setup.ts'],
};
// createJestConfig is exported this way to ensure that next/jest can load the Next.js config which is async
export default createJestConfig(config);I have a simple test for a import { testApiHandler } from "next-test-api-route-handler";
import * as appHandler from "./route";
it("returns 403 unauthorized when not authenticated", async () => {
expect.hasAssertions();
await testApiHandler({
appHandler,
test: async ({ fetch }) => {
await expect((await fetch()).json()).resolves.toStrictEqual({
error: "Unauthorized",
});
},
});
});But when I run
Have I missed something? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
|
I was able to solve this by mocking the // route.test.ts
import { testApiHandler } from "next-test-api-route-handler";
import * as appHandler from "./route";
import type { Session } from "next-auth";
let mockedSession: Session | null = null;
// Mock authOptions
jest.mock("@/lib/auth", () => ({
authOptions: {
adapter: {},
providers: [],
callbacks: {},
},
}));
jest.mock("next-auth/next", () => ({
getServerSession: jest.fn(() => Promise.resolve(mockedSession)),
}));
afterEach(() => {
mockedSession = null;
});
it("returns 403 unauthorized when not authenticated", async () => {
mockedSession = null;
await testApiHandler({
appHandler,
test: async ({ fetch }) => {
const response = await fetch({ method: "GET" });
console.log(await response.json());
expect(response.status).toBe(401);
},
});
});And this test now passes: However, if I attempt to check the returned JSON: it("returns 403 unauthorized when not authenticated", async () => {
mockedSession = null;
await testApiHandler({
appHandler,
test: async ({ fetch }) => {
const response = await fetch({ method: "GET" });
console.log(await response.json());
expect(response.status).toBe(401);
await expect(response.json()).resolves.toStrictEqual({
error: "Unauthorized",
});
},
});
});I get an error: I have |
Beta Was this translation helpful? Give feedback.
-
|
This was caused by adding |
Beta Was this translation helpful? Give feedback.
-
|
Mocking the use of it("returns 403 unauthorized when not authenticated", async () => {
mockedSession = null;
await testApiHandler({
appHandler,
test: async ({ fetch }) => {
const response = await fetch({ method: "GET" });
console.log(await response.json());
expect(response.status).toBe(401);
/*await expect(response.json()).resolves.toStrictEqual({
error: "Unauthorized",
});*/
},
});
});This works correctly. However, if I uncomment |
Beta Was this translation helpful? Give feedback.
-
|
Hi there! NTARH is conceptually quite simple: it's a thin wrapper around That last error is interesting though, |
Beta Was this translation helpful? Give feedback.
-
|
That's one of those interesting results of an impedance mismatch between the fetch spec, implementers of the fetch spec, and other implementers of the fetch spec. (what comes next is only AFAIK, please feel free to correct me; I'll leave this explanation here to link back to later on if the README needs updating) Currently, when calling fetch with Node.js (and Deno, Ruby, Python, and others) technically supports "full duplex" streams for the fetch body, where the server and client both send data to each other in parallel (scratching out #1 above), which would allow Hence the Try: it("returns 403 unauthorized when not authenticated", async () => {
mockedSession = null;
await testApiHandler({
appHandler,
test: async ({ fetch }) => {
const response = await fetch({
method: "DELETE",
body: "test", // <== this is a bit weird though since this isn't a stream
duplex: "half"
});
//console.log(await response.json());
//expect(response.status).toBe(401);
await expect(response.text()).resolves.toStrictEqual({
error: "Unauthorized",
});
},
});
});Unfortunately, the Node.js docs are lacking here since they just redirect to the MDN docs. Though, you shouldn't be getting this error when the request body isn't a stream, so you may need to add |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed explanation. Unfortunately that didn't help. Adding This is NodeJS v18.19.0. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, the TypeScript types for Node.js have not caught up yet last I checked. Still, you shouldn't have to use that option if you're not passing a stream for body. Can you link a minimal repo that demonstrates your error? I'll take a look later today. |
Beta Was this translation helpful? Give feedback.
-
|
I've created a simple repo at https://github.com/davidmytton/ntarh-test which has a failing test. This isn't the same as I reported above, but is failing when I think it should be passing... |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: When I replace SWC with babel and remove the Thank you for reporting this issue! |
Beta Was this translation helpful? Give feedback.
-
|
This has been addressed in v4.0.5. I'll be using your demo repo as an integration test for |
Beta Was this translation helpful? Give feedback.
-
|
Great, thanks. Confirmed v4.0.5 fixes this! |
Beta Was this translation helpful? Give feedback.
This has been addressed in v4.0.5.
I'll be using your demo repo as an integration test for
next/jest.jsand SWC going forward :) If the latest version of NTARH still isn't working for you, please open a new issue and I'll investigate.