When fetchContent.mjs ran during the SSR build process, it accurately synchronized the issues and issue-archive folders from the main repository. However, it failed to synchronize the tickets.json store file. Because middleware-v2 consumes the tickets.json packaged within the published neo.mjs npm dependency (which may trail behind the main repository by hours or days), any recently archived tickets (e.g. #9484-#9491) were still pointing to the issues/ path according to the outdated tickets.json.
When the SSR renderer attempted to fetch these Markdown files from the issues/ folder, it crashed with ENOENT because the updated fetchContent.mjs had physically placed them in issue-archive/. This crash caused the renderer to abort, leaving behind empty HTML directories for these ticket routes.
Solution: Update buildScripts/fetchContent.mjs to dynamically pull the latest tickets.json and releases.json (from Portal resources/data/) from the cloned main repository alongside the Markdown files, guaranteeing absolute path consistency between the JSON data store and the physical file tree.
When
fetchContent.mjsran during the SSR build process, it accurately synchronized theissuesandissue-archivefolders from the main repository. However, it failed to synchronize thetickets.jsonstore file. Becausemiddleware-v2consumes thetickets.jsonpackaged within the publishedneo.mjsnpm dependency (which may trail behind the main repository by hours or days), any recently archived tickets (e.g. #9484-#9491) were still pointing to theissues/path according to the outdatedtickets.json.When the SSR renderer attempted to fetch these Markdown files from the
issues/folder, it crashed withENOENTbecause the updatedfetchContent.mjshad physically placed them inissue-archive/. This crash caused the renderer to abort, leaving behind empty HTML directories for these ticket routes.Solution: Update
buildScripts/fetchContent.mjsto dynamically pull the latesttickets.jsonandreleases.json(from Portalresources/data/) from the cloned main repository alongside the Markdown files, guaranteeing absolute path consistency between the JSON data store and the physical file tree.