PR #750 introduced the ability to opt out of Fathom analytics via the DISABLE_ANALYTICS flag. Unfortunately, while this PR provides a mechanism to disable analytics, it does not fully work in practice because the logic is applied only in a browser context that can't access it.

I run the project using:

npm install
npm run dev

Then I set the following in .env (or by passing it explicitly as an env variable):

VITE_DISABLE_ANALYTICS=true

However, analytics is still loaded.

The logic for disabling analytics is currently inside the index.html:

Problem:

• process.env does not exist in the browser.
• import.meta.env cannot be used inside plain HTML, only in JS/TS modules processed by Vite.
• As a result, setting VITE_DISABLE_ANALYTICS in .env has no effect.
• This is not a .env issue since it’s caused by the logic running in the browser context.

Expected behavior:
Setting VITE_DISABLE_ANALYTICS=true in .env should disable analytics when running npm run dev (and in production builds).

Workaround:
I can disable analytics manually by changing config.js with:

window.env = { DISABLE_ANALYTICS: 'true' };