Rocky_Mountain_Vending/.pnpm-store/v10/files/e2/501c164b801f880eb4728ee82b61c03fb9c58db221e6b6dce2382e90188c493fe9f6f059d3b24c74216a15d54b0d325d2a588e05d732b512e2297a983c9098
DMleadgen 46d973904b
Initial commit: Rocky Mountain Vending website
Next.js website for Rocky Mountain Vending company featuring:
- Product catalog with Stripe integration
- Service areas and parts pages
- Admin dashboard with Clerk authentication
- SEO optimized pages with JSON-LD structured data

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 16:22:15 -07:00

21 lines
No EOL
985 B
Text

// 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 setAppBuildId is called
// during initialization before hydration starts, this will always get
// reassigned to the actual build 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.
let globalBuildId = '';
export function setAppBuildId(buildId) {
globalBuildId = buildId;
}
export function getAppBuildId() {
return globalBuildId;
}
//# sourceMappingURL=app-build-id.js.map