Self-hosters who skip Cesium Ion token setup get a globe that boots fine, then 401s on world terrain and base imagery from `api.cesium.com`. The cause is invisible — Cesium ships a default Ion token inside its npm package that they periodically revoke when usage spikes — and most users don't realize the build inlined an empty `NEXT_PUBLIC_CESIUM_ION_TOKEN` until they're staring at network logs. Add a `prebuild` step that prints an actionable warning (token name, why it matters, where to get a free one) when the var is missing, so the gap is surfaced when it can still be fixed cheaply. Non-fatal — build continues — because demo and existing setups may legitimately rely on the bundled default until it stops working for them. Co-authored-by: Sapphire <sapphire@tiktokcoach> Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
31 lines
1.2 KiB
JavaScript
31 lines
1.2 KiB
JavaScript
/**
|
|
* Pre-build sanity check for build-time public env vars.
|
|
*
|
|
* Some NEXT_PUBLIC_* vars are inlined into the client bundle by Next.js at
|
|
* build time, so they must be set when `next build` runs (not just at runtime).
|
|
* Missing ones don't fail the build — most have library defaults — but they
|
|
* surface as opaque runtime 401s / blank panes that are painful to diagnose.
|
|
*
|
|
* This script prints actionable warnings instead.
|
|
*/
|
|
|
|
const checks = [
|
|
{
|
|
name: "NEXT_PUBLIC_CESIUM_ION_TOKEN",
|
|
why: "Cesium ships a built-in default Ion token, but Cesium periodically revokes it. Without your own token, base imagery and world terrain may return 401 Unauthorized at runtime.",
|
|
how: "Get a free token at https://ion.cesium.com and set NEXT_PUBLIC_CESIUM_ION_TOKEN before building (e.g. in .env).",
|
|
},
|
|
];
|
|
|
|
const missing = checks.filter(c => !process.env[c.name]);
|
|
if (missing.length === 0) process.exit(0);
|
|
|
|
const yellow = (s) => `\x1b[33m${s}\x1b[0m`;
|
|
console.warn(yellow("\n⚠ Build-time env vars not set:"));
|
|
for (const c of missing) {
|
|
console.warn(yellow(`\n ${c.name}`));
|
|
console.warn(` ${c.why}`);
|
|
console.warn(` Fix: ${c.how}`);
|
|
}
|
|
console.warn(yellow("\nContinuing build — these are warnings, not errors.\n"));
|