"_ssgManifest.js" & _buildManifest.js missing from a nextjs app hosted on Google Cloud Platform

user_2910211 0
Viewed 2226

sometimes the console shows these errors on opening the website

GET https://example.com/subpath/_next/static/9ufj5kFJf/_buildManifest.js
[HTTP/3 404 Not Found 311ms]

GET https://example.com/subpath/_next/static/9ufj5kFJf/_ssgManifest.js
[HTTP/3 404 Not Found 334ms]

Loading failed for the <script> with source “https://example.com/subpath/_next/static/9ufj5kFJf/_buildManifest.js”. 1434-247:1:1
Loading failed for the <script> with source “https://example.com/subpath/_next/static/9ufj5kFJf/_ssgManifest.js”.

the app does use ISR and that seems to be working, it does get updated, what do these files do? what could happen if they are missing?

  • "react": "17.0.2"
  • "next": "10.1.3",
  • "node" "15.1.2"
gcloud next.js reactjs google-cloud-platform javascript
2 Answers

I had the same problem with GCP (Kubernetes engine) with pods count > 1. I resolved the issue by restarting the deployment (all pods).

user_52280650

On that Github issue @Prabir linked to in a comment, someone posted a way to use the generateBuildId function within the Next.js config file:

const execSync = require("child_process").execSync;

const lastCommitCommand = "git rev-parse HEAD";

module.exports = {
  async generateBuildId() {
    return execSync(lastCommitCommand).toString().trim();
  },
};

I work with an app that uses some combination of AWS CodeBuild and Docker images, which prevents direct access to all the git commands so that snippet above didn't work. But using CODEBUILD_BUILD_ID or really any environment variable (unique to either that commit or the build itself) did. I'm not as familiar with the GCP-equivalents but this Cloud Build Docs page makes it seem like $COMMIT_SHA would be a good option to try.

user_7729850
Related