Seems to work if I add a ton of export const dynamic = "force-dynamic";, albeit annoying

Could I make the whole app dynamic by default instead somehow perhaps?

export const getSettings = unstable_cache(
async (): Promise<SettingsValues> => {
if (process.env.NODE_ENV === 'development' && !process.env.DB_URL) {
throw new Error("Database not available");
}

const settings = (await db.select().from(settingsTable).limit(1)).at(0);
if (!settings) {
throw new Error("Settings not found.");
}
return settings.value;
},
[settingsTag],
settingsNextConfig
);
This is my think

You can apply this to the top-most layout that you want to have this on and it propagate to nested routes. I personally use it in my root layout itself since my whole app is fully dynamic anyways.

The reason why you need an explicit flag to mark a route segment as dynamic is that Next deduces whether a segment is dynamic based on you using dynamic APIs such as headers, cookies, searchParams.

If it doesn't find any of those it will default to static by default and thus attempting to run your query during build time and failing if the DB isn't available during build time.

I see

I'll do like you and make all dynamic because there's no static content anyway, and I will cache stuff