df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
25 lines
1.2 KiB
JavaScript
25 lines
1.2 KiB
JavaScript
// This gets assigned as a side-effect during app initialization. Because it
|
|
// represents the build used to create the JS bundle, it should never change
|
|
// after being set, so we store it in a global variable.
|
|
//
|
|
// When performing RSC requests, if the incoming data has a different build ID,
|
|
// we perform an MPA navigation/refresh to load the updated build and ensure
|
|
// that the client and server in sync.
|
|
//
|
|
// Starts as an empty string. In practice, because setNavigationBuildId is called during initialization
|
|
// before hydration starts, this will always get reassigned to the actual ID before it's ever needed
|
|
// by a navigation. If for some reasons it didn't, due to a bug or race condition, then on
|
|
// navigation the build comparision would fail and trigger an MPA navigation.
|
|
//
|
|
// Note that this can also be initialized with the deployment id instead (if available). So it's not
|
|
// the same as "the build id", but we are running out of alternative names for "build id or
|
|
// deployment id".
|
|
let globalBuildId = '';
|
|
export function setNavigationBuildId(buildId) {
|
|
globalBuildId = buildId;
|
|
}
|
|
export function getNavigationBuildId() {
|
|
return globalBuildId;
|
|
}
|
|
|
|
//# sourceMappingURL=navigation-build-id.js.map
|