[karthickeyan-dev]

Closes #800.

void.config.ts is loaded with jiti, which only aliases void/config, so an import through tsconfig paths failed with an error that reads like a missing package. env.ts already detects this case and adds a hint; the config loader now does the same.

Changes

• Moved extractFailedSpecifier() and looksLikeAlias() from host/load-user-env.ts into a new host/alias-hint.ts, with an aliasHint(err, file) helper that both loaders use.
• extractFailedSpecifier() now also accepts MODULE_NOT_FOUND, the code jiti's require-based loading reports.
• loadVoidConfig() appends the hint when the failed specifier looks like an alias:

  config: Could not load void.config.ts: Cannot find module '@/lib/theme'
  Require stack:
  - /path/to/app/void.config.ts
  
  Hint: '@/lib/theme' looks like a tsconfig path alias. void.config.ts does not resolve tsconfig "paths" — use a relative import (e.g. "./shared/...") instead.
  

• docs/reference/config.md now says to use relative imports or package names in void.config.ts, matching the env.ts note in the env vars guide.

The env.ts hint wording changes slightly ("env.ts does not resolve tsconfig "paths"" instead of "env.ts is loaded directly by Node and does not resolve…") so both files share one message.

Tests

• New packages/void/test/unit/config-loader.test.ts: a relative import loads, an @/… import gets the hint, and a missing scoped package (@scope/pkg) doesn't.
• vp test run (full suite: 793 files, 16674 tests passed) and vp run check pass.

🤖 Generated with Claude Code

[cpojer]

👍