Using import { env } from "cloudflare:

Using import { env } from "cloudflare:workers" doesnt include this variable

TK•12/2/25, 11:28 AM

CF_PAGES_COMMIT_SHACF_PAGES_COMMIT_SHA doesn't exist in workers, and we don't inject anything at runtime, but during the build you have access to some CI vars https://developers.cloudflare.com/workers/ci-cd/builds/configuration/#default-variables

Cloudflare Docs

Configuration

Understand the different settings associated with your build.

TTK `CF_PAGES_COMMIT_SHA` doesn't exist in workers, and we don't inject anything at ...

gegiOP•12/2/25, 1:14 PM

Are these env variables also accessiable on the client for example vite?

TK•12/2/25, 1:16 PM

No they are only available as injects from the workers ci system

gegiOP•12/2/25, 1:17 PM

Injects means, I have to do something like {{WORKERS_CI_COMMIT_SHA}} in my wrangler.jsonc?

gegiOP•12/2/25, 1:17 PM

sorry for so many questions

gegiOP•12/2/25, 1:18 PM

@TK for example this?

TK•12/2/25, 1:18 PM

No worries!

TK•12/2/25, 1:19 PM

Let me get you an example

gegiOP•12/2/25, 1:19 PM

Yes, please. Appreicate it! Looking for a proper solution since 2 days ð¥¹

gegiOP•12/2/25, 1:22 PM

btw, I am using the vite cloudflare plugin together with tanstack start if this info is necessary

TK•12/2/25, 3:12 PM

hey! sorry I had a few calls and then have struggled through this like you but fortunately for a bit less time. Our docs could definitely do better here!

TTK hey! sorry I had a few calls and then have struggled through this like you but f...

gegiOP•12/2/25, 3:17 PM

Don't worry. Appreicate your help. Thank you!

TK•12/2/25, 3:26 PM

If you are using Vite there is a definedefine option that you can use to inject variables that are being replaced on build.

There's a demo of that and an associated git repo here:

https://github.com/MattieTK/2025-12-02-workers-ci-envs-vite/

https://2025-12-02-workers-ci-envs-vite.tk.workers.dev/

GitHub

GitHub - MattieTK/2025-12-02-workers-ci-envs-vite

Contribute to MattieTK/2025-12-02-workers-ci-envs-vite development by creating an account on GitHub.

TK•12/2/25, 3:28 PM

If you are not using Vite it's slightly more fiddly which is where I spent most of the time, but you are basically either writing in the vars at build time to a file that exports them that you then read from via a custom build command, or you are modifying your build command to include references inline

TTK If you are using Vite there is a `define` option that you can use to inject vari...

gegiOP•12/2/25, 3:42 PM

I see, this example is totally enough for me. Thank you. That's actually what I was looking for. I needed it so I can notify my users, that a new version exists of the frontend. You basically gave me almost the full implementation

gegiOP•12/2/25, 3:45 PM

But one question I do have. I have to access them through

process.env

process.env

and not through the cloudflare:workerscloudflare:workers

gegiOP•12/2/25, 3:46 PM

Also, I guess they aren't genereated in the worker-configuration.d.tsworker-configuration.d.ts unless I'm missing out something on my side

gegiOP•12/2/25, 3:48 PM

what I also found during my researches is this:

"version_metadata": {
    "binding": "CF_VERSION_METADATA"
},

"version_metadata": {
    "binding": "CF_VERSION_METADATA"
},

this one gets generated in the worker-configuration.d.tsworker-configuration.d.ts

TK•12/2/25, 3:54 PM

Yeah so they are generated on the build side only, so when your worker runs through the CI process, the build command's output includes transpiling your worker code such that these variables get directly replaced with the value at build time. I'm talking to our SAs and the team about the docs here because I think they could be clearer.

gegiOP•12/2/25, 3:54 PM

Thank you so much!

gegiOP•12/2/25, 3:55 PM

Really appreciate it

TK•12/2/25, 3:55 PM

Thanks for raising the challenge with us!

TTK Thanks for raising the challenge with us!

gegiOP•12/2/25, 4:22 PM

One thought of me: Since I am using the vite-cloudflare plugin, is it perhaps possible to inject this envs to vite with the plugin in the future?

gegiOP•12/2/25, 4:22 PM

so we don't have to set it up