V3 - Using NextResponse causes a module-not-found error about payload HOT 2 CLOSED

A follow-up on this issue.

Using Response instead of NextResponse in the handler function does not cause this error. Also, using NextResponse within a custom route file, like the one in the alpha demo, does not cause this error either.

As a side note, destructuring the http-status was causing a syntax error when generating types only, but I checked the source and the aliases are exported. Not sure if it could be related.

// SyntaxError: The requested module 'http-status' does not provide an export named 'OK'
import { OK } from 'http-status';

// But this is fine
import HttpStatus from 'http-status';
Response.json(someResponse, { status: HttpStatus.OK });

from payload.

Fixed in beta.6

from payload.