Add option to anonymise the build with env variable

[jacobpake]

Supports an ANONYMOUS=true environment variable at build time to produce a website with any identifying features removed

[antstei]

Thanks, @jacobpake!

We could also update package.json to support anonymous development and builds:

{
  "scripts": {
    "dev:anonymous": "cross-env ANONYMOUS=true vite dev",
    "build:anonymous": "cross-env ANONYMOUS=true vite build"
  }
}

This requires adding cross-env to devDependencies.

Additionally, we should update README.md to document the new anonymous development and build commands.

[antstei]

Could we define a shared SiteConfig type and use satisfies SiteConfig for both configuration objects, public_config and anon_config?

[jacobpake]

Is there any benefit in doing that?

[antstei]

I’d argue it gives us compile-time shape validation and safer refactors, all while preserving exact literal types—so I see it as a nice-to-have for safety and maintainability.

[jacobpake]

Thanks, @jacobpake!

We could also update package.json to support anonymous development and builds:

{
  "scripts": {
    "dev:anonymous": "cross-env ANONYMOUS=true vite dev",
    "build:anonymous": "cross-env ANONYMOUS=true vite build"
  }
}

This requires adding cross-env to devDependencies.

Is there a benefit in doing this vs just setting the environment variable? Is it worth the dependency?

[antstei]

Is there a benefit in doing this vs just setting the environment variable? Is it worth the dependency?

Adding cross-env is worth it if any of us develops on Windows or plans to. So for now, I think we can skip it.