Repository navigation
Cloudflare integration + vinext 1.2: built worker crashes at boot (initVarlockEnv failed) #1234
Description
varlock version
@varlock/cloudflare-integration 1.6.2
Steps to reproduce
Setup
Tiny vinext 1.2 App Router app (one page reading ENV.* from varlock/env),
varlockCloudflareVitePlugin() in place of cloudflare(), local .env file
with dummy values. No Infisical, no credentials, no deploy involved.
vinext 1.2.0 · vite 8.0.14 · react 19.2.6 · varlock 1.23.0 ·
@varlock/cloudflare-integration 1.6.2 · wrangler 4.151.0 · macOS arm64
Repro
pnpm install
./node_modules/.bin/vite build # green
./node_modules/.bin/wrangler dev --config dist/server/wrangler.jsonActual
Worker crashes before serving anything:
Uncaught Error: initVarlockEnv failed
at null.<anonymous> (_next/static/env-Dh14o1ps.js:3:5)
plus the "no resolved env found" remediation text. Same under
varlock run -- wrangler dev. Verified from a clean checkout
(rm -rf node_modules dist, fresh install, rebuild).
What works (control cases in the README)
vite dev→ 200,🔒 [varlock] injecting resolved envlogged,.env
value rendered. Dev-mode injection is fine.- Same app with plain
cloudflare()and novarlock/envimport → builds,
boots, serves 200. Harness is fine; the integration is the variable.
Questions
- Is
varlock/envexpected to boot in a vinext-bundled worker under stock
wrangler dev? If yes, what supplies__VARLOCK_ENVthere? - Our deploy path is
vinext-cloudflare deploy, notwrangler deploy. Docs
say onlyvarlock-wranglerproduces the blob — any supported way to get it
with a non-wrangler deploy tool, or isvarlock-wranglera hard requirement?
What is expected?
No worker crash
What is actually happening?
Actual
Worker crashes before serving anything:
Uncaught Error: initVarlockEnv failed
at null.<anonymous> (_next/static/env-Dh14o1ps.js:3:5)
plus the "no resolved env found" remediation text. Same under
varlock run -- wrangler dev. Verified from a clean checkout
(rm -rf node_modules dist, fresh install, rebuild).
System Info
Any additional comments?
No response
Activity
pullfrog commentedon Oct 16, 2026
theoephraim commentedon Oct 16, 2026
Thanks for the clean repro, that made this quick.
What's happening: the built Worker only gets its env from a
__VARLOCK_ENVbinding.vite devandvite previewinject it for you, andvarlock-wrangler dev/varlock-wrangler deploysupply it when running wrangler against the build output. Plainwrangler devdoes neither, soinitVarlockEnvhas nothing to load.varlock run -- wrangler devcan't help either: workerd never sees the host process env.On your repro this works as-is:
So to answer your questions:
wrangler devisn't expected to boot it. Usevarlock-wrangler dev --config dist/server/wrangler.json(orvite preview) as thestartscript.vinext-cloudflare deploycalls wrangler'sversions upload/deploythrough wrangler's API rather than spawning thewranglerbinary, so there's no seam forvarlock-wranglerto sit in front of it. Usevite build && varlock-wrangler deploy --config dist/server/wrangler.jsoninstead. It deploys the same build output; what you lose is vinext's cache-warming flags. Supporting the newcfCLI /cloudflare.config.tsflow is on our list.Changes coming out of this:
varlock-wrangler dev/deployinstead of the genericinitVarlockEnvadviceSeparately, while building the example we found that
console.log(ENV.SECRET)inside a Server Component leaked the raw value into the dev-mode RSC payload through React's console replay (varlock's leak detection then truncated the page). That's fixed in the same release.github-actions commentedon Oct 19, 2026
✅ A fix has been merged to
mainin #1236 and will ship in the next release. GitHub auto-closed this issue on merge, but the change isn't published yet.Cloudflare: clear error for a missing __VARLOCK_ENV binding, redact R…