Discrepancies Between Dev Mode and Build Behavior in Next.js

When testing the following Next.js code, there is a noticeable difference between development (npm run dev --turbo) and production (npm run build && npm run start) modes:

import Link from "next/link";

async function getRandomNumber() {
  const res = await fetch('http://localhost:3020/random-number');
  const data = await res.json();
  return data.numero;
}

export default function Home() {
  return (
    <div>
      <p>{getRandomNumber()}</p>
    </div>
  );
}

In development mode, the fetch request is triggered every time the page is loaded, navigated to, or revisited, and the updated data is rendered. In production mode, the data appears to be cached, and the page does not fetch fresh data as expected, rendering a fixed value. Adding export const dynamic = 'force-dynamic' resolves the issue, ensuring that the data is fetched dynamically in both modes.

Step-by-Step Guide to Reproduce

Set up the test environment:

Ensure you have a Next.js application initialized (npx create-next-app).
Add the provided code to a pages/index.js or app/page.js file.
Start a simple server at http://localhost:3020/numero-aleatorio that returns a random number (like the Express example provided earlier).

Run in Development Mode:

Start the development server with the Turbo engine enabled:

bash

Copy code

npm run dev --turbo

Open http://localhost:3000 in your browser.
Refresh the page or navigate away and return to it. 3.Expected behavior:* The fetch request is triggered every time, and the random number updates.

Run in Production Mode:

Build the application:

bash

Copy code

npm run build

Start the production server:

bash

Copy code

npm run start

Open http://localhost:3000 in your browser.
Refresh the page or navigate away and return to it. 5.Expected behavior:* Without dynamic: 'force-dynamic', the fetched data does not update.

Is it normal for Next.js to behave differently in development and production modes regarding fetch requests and caching, requiring explicit configurations like dynamic: 'force-dynamic' to align the behaviors?