console vite/vitest configs rely on features configLoader: 'native' drops — a future Vite major turns 5 warnings into a broken config load #3384

Found while working #3305 (wiring apps/console/tsconfig.node.json into a gate). Not fixed there — orthogonal to that change, filing per PD #10. Deliberately left unassigned.

What

Every vite build / vitest run touching the console prints this, once per config load (so it repeats several times in one test run):

(!) Your Vite config uses features that are unsupported by `configLoader: 'native'`,
    which is planned to become the default in a future major version of Vite:
  - `__dirname` (vitest.config.ts:13:33). Use `import.meta.dirname` instead
  - import "./vite.config" without a file extension (vitest.config.ts:4:24). Add the file extension
  - `__dirname` (vite.config.ts:56:35). Use `import.meta.dirname` instead
  - import "../../scripts/vite-crypto-stub" without a file extension (vite.config.ts:6:32). Add the file extension
  - import "../../scripts/vite-maplibre-worker" without a file extension (vite.config.ts:7:36). Add the file extension

Two distinct incompatibilities, both in apps/console:

1. __dirname in an ESM config — apps/console/vitest.config.ts and apps/console/vite.config.ts. Vite's current (bundling) loader injects a CJS-ish shim; the native loader will not. Replacement is import.meta.dirname.
2. Extensionless relative imports — vitest.config.ts imports ./vite.config, and vite.config.ts imports ../../scripts/vite-crypto-stub / ../../scripts/vite-maplibre-worker. Node's native ESM resolver does not do extension guessing.

(Line numbers above are from origin/main. On #3305's branch the two scripts/ imports shift to 10/11 because a comment was added above them — the imports themselves are untouched.)

Why it matters

This is dormant today — it is only a warning, and everything builds and tests green, which is why this is filed as a finding rather than a defect. What makes it worth recording is the failure mode when Vite flips the default: the console's config would fail to load, so vite build, vite dev, and the console's whole vitest project all die at once, on a dependency bump rather than on a code change. The fix is mechanical and can be done at any time; the cost of discovering it during an upgrade is a blocked upgrade.

There is also a mild interaction with #3305: apps/console/tsconfig.node.json now type-checks vite.config.ts and the scripts/vite-*.ts plugins, so whoever adds the file extensions has a gate that will confirm the specifiers still resolve. moduleResolution: "bundler" accepts both spellings, so adding .ts extensions there will not upset the type-check either way.

Suggested direction (not decided)

• __dirname -> import.meta.dirname in both console configs.
• Add explicit extensions to the three relative config imports.
• Optionally set configLoader: 'native' explicitly afterwards so the repo pins the behaviour instead of waiting to inherit it, and any regression shows up immediately rather than at the next Vite major.