[BUG]: 🚨 initVarlockEnv failed 🚨 on vite cloudflare based app

[yudyananda]

varlock version

0.7.4

Steps to reproduce

Follow the cluodflare+vite integration guide on stanstack-start project

What is expected?

Expect app to run as it should be without an error

What is actually happening?

run dev and return error

@tatalepa/web:dev: 🚨 initVarlockEnv failed  🚨
@tatalepa/web:dev: try rerunning your command via `varlock run`
@tatalepa/web:dev:  (x2)
@tatalepa/web:dev: [vite] An error happened during full reload
@tatalepa/web:dev: initVarlockEnv failed
@tatalepa/web:dev: Error: initVarlockEnv failed
@tatalepa/web:dev:     at initVarlockEnv (/home/yua/projects/tatalepa-project/apps/web/node_modules/.vite/deps_ssr/chunk-GUXIERT2.js?v=bf1ae134:196:11)
@tatalepa/web:dev:     at virtual:cloudflare/worker-entry:46:41
@tatalepa/web:dev:     at Object.runInlinedModule (workers/runner-worker/index.js:214:4)
@tatalepa/web:dev:     at ModuleRunner.directRequest (workers/runner-worker/vite/module-runner:1204:59)
@tatalepa/web:dev:     at ModuleRunner.cachedRequest (workers/runner-worker/vite/module-runner:1111:73)
@tatalepa/web:dev:     at ModuleRunner.import (workers/runner-worker/vite/module-runner:1061:10)
@tatalepa/web:dev:     at workers/runner-worker/vite/module-runner:726:6
@tatalepa/web:dev: error when starting dev server:
@tatalepa/web:dev: Error: initVarlockEnv failed
@tatalepa/web:dev:     at runInRunnerObject (workers/runner-worker/index.js:106:3)
@tatalepa/web:dev:     at getWorkerEntryExportTypes (workers/runner-worker/index.js:245:24)
@tatalepa/web:dev:     at null.<anonymous> (workers/runner-worker/index.js:349:37)
@tatalepa/web:dev:     at maybeCaptureError (workers/runner-worker/index.js:50:10)
@tatalepa/web:dev: error: script "dev" exited with code 1

System Info

System:
    OS: Linux 6.6 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 3.89 GB / 6.67 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh

Any additional comments?

I found a similar issue, and this could probably happen in other vite based apps.