86c0bb619d
This change sorts environment variables alphabetically before they're processed with import-meta-env that injects them into the index.html. This makes sure consistent hashes across pod restarts when there aren't any functional changes made to the `.env` file. The issue was affecting desktop app reconnections after k8s pod restarts. The cause was non-deterministic env var ordering (a sideeffect of `Map`) during the import-meta-env injection process. Even when the env vars themselves didn't change, their order in the injected JSON could change, ultimately resulting in different file hashes. This fix ensures that regardless of the order in which env vars are provided by the runtime, they will be sorted alphabetically before being written to the build.env file.
18 lines
505 B
JavaScript
Executable file
18 lines
505 B
JavaScript
Executable file
#!/usr/local/bin/node
|
|
import { execSync } from "child_process"
|
|
import fs from "fs"
|
|
|
|
const envFileContent = Object.entries(process.env)
|
|
.filter(([env]) => env.startsWith("VITE_"))
|
|
.sort(([envA], [envB]) => envA.localeCompare(envB))
|
|
.map(
|
|
([env, val]) =>
|
|
`${env}=${val.startsWith('"') && val.endsWith('"') ? val : `"${val}"`}`
|
|
)
|
|
.join("\n")
|
|
|
|
fs.writeFileSync("build.env", envFileContent)
|
|
|
|
execSync(`npx import-meta-env -x build.env -e build.env -p "/site/**/*"`)
|
|
|
|
fs.rmSync("build.env")
|