Instead of calling fetch(), I mocked out an API's data store using a const, kind of like this:

import 'server-only';
import {cache} from "react";
import {revalidatePath} from "next/cache";

// mimics the data that will be stored by an external API
console.log("Setting initial state.")
export const state = {
    foo: 1,
    bar: 'baz'
};

// mimics the cached GET fetch() to the external API 
export const getState = cache(async () => {
    return state;
})

// mimics a POST fetch() to the external API
export async function updateStateAction(newFoo: number) {
    state.foo = newFoo;
    revalidatePath('/')
}

But my server components always render with {foo: 1}, even after calling into that action to update foo to a new value. And the "Setting initial state" log gets emitted on each page load. It's like this file is getting re-imported from scratch on each render, erasing that global state I had set up. I've already set my pages to force-dynamic so it's not a static render issue.

Any ideas what's going on here, or how I can effectively use global server-side state in my Next.JS app router codebase?

Thanks!