feat(blog): add file-based blog with dynamic slugs, MDX content and layout shell
- Introduced blog routing using Next.js App Router - Implemented dynamic [slug] pages for blog posts - Added MDX-based content loading via lib/posts - Integrated shared TopBar layout with navigation - Established clear content, lib and component separation
This commit is contained in:
21
apps/public-web/node_modules/next/dist/esm/client/app-build-id.js
generated
vendored
Normal file
21
apps/public-web/node_modules/next/dist/esm/client/app-build-id.js
generated
vendored
Normal file
@@ -0,0 +1,21 @@
|
||||
// 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
|
||||
Reference in New Issue
Block a user