Should Start docs document that import.meta.dirname changes during prerender?

[allohamora]

I ran into a confusing path-resolution issue with TanStack Start + Nitro prerendering.
In server code, I used import.meta.dirname to resolve a project-relative directory:

// src/server/db.ts
import path from 'node:path';
import { migrate } from 'orm';

// import.meta.dirname in the development equals '/project/src/server';
// import.meta.dirname in the prerender equals '/project/.output/server/_ssr'
const MIGRATIONS_DIR = path.join(import.meta.dirname, '..', '..', 'migrations');

migrate(MIGRATIONS_DIR);

This works in the dev environment, but during prerendering, the module is executed from the built server output (.output/server/_ssr), so import.meta.dirname no longer points to the expected path.

This could be fixed by resolving with process.cwd():

// src/server/db.ts
import path from 'node:path';
import { migrate } from 'orm';

// process.cwd() always equals '/project'
const MIGRATIONS_DIR = path.join(process.cwd(), 'migrations');

migrate(MIGRATIONS_DIR);

Should the Static Prerendering docs mention that server code executed during prerendering runs from generated output, so import.meta.dirname should not be assumed to refer to the original file path?