From 2ffb72d369ef62ed94086095d103307dc0093154 Mon Sep 17 00:00:00 2001
From: Jack Williams <1736957+jpwilliams@users.noreply.github.com>
Date: Tue, 12 Nov 2024 12:53:08 +0000
Subject: [PATCH] Fix `next` JSR export

We don't require this because we expect packages to also have ESM exports
declared in their `package.json`, but `next` does not do this, so we must
explicitly use the extension still.

Annoyingly, a dry run publish with `jsr` doesn't reveal this.
---
 packages/inngest/src/next.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/inngest/src/next.ts b/packages/inngest/src/next.ts
index 1e80e8df..e1b41738 100644
--- a/packages/inngest/src/next.ts
+++ b/packages/inngest/src/next.ts
@@ -21,7 +21,7 @@
  */
 
 import { type NextApiRequest, type NextApiResponse } from "next";
-import { type NextRequest } from "next/server";
+import { type NextRequest } from "next/server.js";
 import {
   InngestCommHandler,
   type ServeHandlerOptions,