🔧 Add .js extensions to Next.js module imports for ESM compliance

Extend the ESM compliance fix to include imports from next/script,
next/headers, and next/server modules in provider and script components.

This ensures proper module resolution when the package is consumed as a
native ESM module, where Node.js requires explicit file extensions for
all import specifiers including framework modules.

Author: hyperb1iss

src/provider/public-env-provider.tsx

@@ -1,4 +1,4 @@
-import { connection } from 'next/server'
+import { connection } from 'next/server.js'
 import { type FC, type PropsWithChildren } from 'react'
 
 import { getPublicEnv } from '../helpers/get-public-env.js'

src/script/env-script.tsx

@@ -1,4 +1,4 @@
-import Script, { type ScriptProps } from 'next/script'
+import Script, { type ScriptProps } from 'next/script.js'
 import { type FC } from 'react'
 
 import { escapeJsonForHtml } from '../helpers/escape-json-for-html.js'
@@ -146,7 +146,7 @@ export const EnvScript: FC<EnvScriptProps> = async ({
     if (typeof nonce === 'object' && nonce !== null) {
         try {
             // Dynamic import to avoid bundling server-only code in client contexts
-            const { headers } = await import('next/headers')
+            const { headers } = await import('next/headers.js')
             // Next.js 16+ requires async headers() call
             const headerStore = await headers()
 

src/script/public-env-script.tsx

@@ -1,5 +1,5 @@
-import { type ScriptProps } from 'next/script'
-import { connection } from 'next/server'
+import { type ScriptProps } from 'next/script.js'
+import { connection } from 'next/server.js'
 import { type FC } from 'react'
 
 import { getPublicEnv } from '../helpers/get-public-env.js'