Regression in v15.1.0: cookies() throws in server action

[debel27]

Link to the code that reproduces this issue

https://github.com/debel27/next-issue_server-action-context

To Reproduce

All the relevant code is in this file:

src/app/page.tsx

import { cookies } from "next/headers";

export default function HomePage() {
  return (
    <main>
     <form action={serverAction}>
       <button>Click</button>
     </form>
    </main>
  );
}

async function serverAction() {
  "use server";
  await cookies(); // <- this throws in Next.js 15.1.0 when JS is disabled on the client
  console.log("action called"); // <- this statement is reached in Next.js 15.0.0
}

1. Start the application in development (next dev)
2. Open the application in the web browser
3. Open the devTools and disable Javascript. Refresh the page.
4. Click the button

Current vs. Expected behavior

Expected behavior

The server action runs successfully.

Actual behavior

The server action throws, leading to a blank page. The thrown error is:

 ⨯ Error: `cookies` was called outside a request scope. Read more: https://nextjs.org/docs/messages/next-dynamic-api-wrong-context
    at cookies (src/app/page.tsx:15:15)
  13 | async function serverAction() {
  14 |   "use server";
> 15 |   await cookies(); // <- this throws in Next.js 15.1.0 when JS is disabled on the client
     |               ^
  16 |   console.log("action called"); // <- this statement is reached in Next.js 15.0.0
  17 | } {
  page: '/'
}
 ✓ Compiled /_error in 355ms (807 modules)
 POST / 500 in 861ms

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:09:44 UTC 2024
  Available memory (MB): 31798
  Available CPU cores: 24
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: 15.0.3
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Runtime

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

Additional context

I think my problem is a regression that was introduced in Next 15.1.0. When I downgrade to 15.0.0, I do not encounter the problem.

// No problem with these dependencies
"dependencies": {
  "react": "19.0.0-rc-65a56d0e-20241020",
  "react-dom": "19.0.0-rc-65a56d0e-20241020",
  "next": "15.0.0"
}

The problem only occurs when JavaScript is disabled on the client. Could it have something to do with hydration?

I only tested the code locally.

[joshuaballoch]

I've run into this as well, calling any of the Dynamic APIs from server actions. In my case:

1. I was on next 15.1.4, react 19.0.0
2. I ran into this when trying to submit a form with JS disabled, just to check out NextJS's progressive enhancement, and see the form submit without JS and work fine
3. I ran into the error message: Error: \headers` was called outside a request scope. Read more: https://nextjs.org/docs/messages/next-dynamic-api-wrong-context
   at headers (src/server/actions.ts:21:25)`

I downgraded to 15.0.4 and no longer see this issue.

I agree with @debel27 that maybe this is a but that was introduced in 15.1.0

[ztanner]

Hi - thank you for the report. This was fixed in #74196 which is currently on canary, and will be released in an upcoming stable version of Next.js