[fengmk2]

Fixes #1261.

When Vite's root is not the working directory (for example vite app), the first config hook call reloads from that root, but it does not set configHookCalled. On the first dev restart, the root now equals loadedConfigDir, so the hook takes the first-call branch: it sets the flag and skips the reload. The server keeps stale env values until the second restart. This started in 1.5.0 with #985, which changed the check from process.cwd() to loadedConfigDir. The same stale restart happens with rootDir when _VARLOCK_ENV_KEY is already set, because then the dev-key lifecycle hook does not load rootDir before the main hook.

The fix replaces configHookCalled with a flag that every load sets and the main config hook clears once it has used that load. The hook reloads when the root differs, or on a dev resolve when the current load was already used (a restart). Any loader (the module-level load, the dev-key hook, an integration's refresh) now counts without needing its own flag. This also removes the second load on Nuxt dev restarts, where refreshVarlockEnv already reloaded before the config hook.

Tests cover restarts with the root equal to and different from the cwd, rootDir with and without a preset key, Nuxt-style refreshes, and builds, and assert load counts so redundant or skipped reloads show up.

One behavior change: in a dev or Vitest run whose first config has a different root, a later config call with the same root now reloads. That already happens when the root is the working directory.

[pullfrog]

✅ No new issues found.

Reviewed changes Reviewed the restart-state fix, both regression tests, and the patch release entry.

• Restart tracking: Marks the first root-correcting config reload as a completed hook call so the next dev restart reloads env values.
• Regression coverage: Tests repeated config resolution for a Vite root outside cwd and for rootDir with an existing encryption key. All 26 Vite integration tests passed via bunx turbo run test:ci --filter=@varlock/vite-integration; filesystem-watched restarts were not independently exercised.
• Release scope: Includes a patch release entry for @varlock/vite-integration.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}

[theoephraim]

thanks for this!

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@varlock/astro-integration@1262

npm i https://pkg.pr.new/@varlock/cloudflare-integration@1262

npm i https://pkg.pr.new/@varlock/nuxt-integration@1262

npm i https://pkg.pr.new/@varlock/vite-integration@1262

commit: 289620d

[pullfrog]

✅ No new issues found.

Reviewed changes Reviewed the load-consumption refactor and added regression coverage since the previous review.

• Replaced restart tracking: Tracked whether the current load has been consumed by the config hook, preserving first-restart reloads while reusing a preceding framework refresh.
• Expanded regression coverage: Added load-count checks for repeated resolves, dev-key root correction, Nuxt-style refreshes, and same-root builds. All 31 Vite integration tests passed via bunx turbo run test:ci --filter=@varlock/vite-integration; filesystem-watched restarts were not independently exercised.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}