`entryImportMap` Failed to find a valid digest in the integrity attribute

[tomsdob]

Environment

---

• Nuxt Version: 4.1.2

---

Reproduction

Describe the bug

Failed to find a valid digest in the 'integrity' attribute for resource 'https://somedomain.com/_nuxt/PeQVlOgK.js' with computed SHA-384 integrity 'xBIudfkVkGKemQ5krLETsP8rpyEg97VDA7HctIzgdnTtoaRvTl6oYE5iCrzfVY5W'. The resource has been blocked.

Uncaught (in promise) TypeError: Failed to fetch dynamically imported module: https://somedomain.com/_nuxt/PeQVlOgK.js

Additional context

After deployment of a website, I received these errors in the console.
Out of Firefox, Chrome, Safari, Brave, the Brave browser was the only browser which I experienced this issue on. After refreshing the website without cache, the issue was gone.
Sometimes these errors appear right after deployment, sometimes after several hours.
When entryImportMap is set to false, this issue seems to be gone.

Logs

[github-actions]

Would you be able to provide a minimal reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

Please use a template below to create a minimal reproduction

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[Frank3K]

We're experiencing the same issue on Nuxt 3.19.0 and have identified the root cause.

Root Cause Analysis:

The problem stems from inconsistent file content despite identical filenames across builds:

1. Caching Headers: JS files are served with cache-control: public, max-age=31536000, immutable
2. Content Inconsistency: The same filename contains different content across builds

Example:
File CQgm5sEd.js initially contained:

const __vite__mapDeps=(i,m=__vite__mapDeps,d=(m.f||(m.f=["./_HPk0LvB.js","./DCk3jssP.js","./BBW1Tyrc.js","./Dpip4xdi.js","./C0f8Qfu5.js","./CMkwb9EP.js","./DOqUlYTz.js"])))=>i.map(i=>d[i]);
// ... truncated

After a few builds, the same filename now contains:

const __vite__mapDeps=(i,m=__vite__mapDeps,d=(m.f||(m.f=["./_HPk0LvB.js","./CNoyN8ms.js","./BBW1Tyrc.js","./Dpip4xdi.js","./C0f8Qfu5.js","./CMkwb9EP.js","./DOqUlYTz.js"])))=>i.map(i=>d[i]);
// ... truncated

Notice "./DCk3jssP.js" changed to "./CNoyN8ms.js" in the dependency array. The truncated part is the same in both files.

The Issue:

• The browser caches the file with immutable directive
• Subsequent builds generate different content for the same filename
• The integrity hash changes, but the browser serves the cached version
• This causes integrity validation to fail and breaks dynamic imports

Suspected Cause:
This appears related to the importmap changes introduced in PR #33075.

Temporary Workaround:
Setting entryImportMap: false resolves the issue, confirming the connection to the import map feature.

This violates the fundamental assumption of immutable caching - that identical filenames always contain identical content.

[github-actions]

Would you be able to provide a minimal reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

Please use a template below to create a minimal reproduction

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[danielroe]

this seems like a browser bug.

the importmap shouldn't affect the browser's knowledge of the file - it's pointing #entry -> the actual file (which does have a unique name bound by a hash)

[genisd]

the file content is consistent except for the file list to be loaded, that changes, which in essence changes the hash of the file itself.

the asset is delivered with high cache-ttl && immutable so the browser caches it.

when on the next rebuild the file content changes as described, the integrity hash which comes with the html doesn't match the previously cached javascript content anymore and hence the browser denies execution due to the integrity mismatch.

one does need to apply some code change to trigger this scenario i believe as without the code change the fault will not reveal it self (i believe it's deterministic in this regard)

[github-actions]

Would you be able to provide a minimal reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

Please use a template below to create a minimal reproduction

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[danielroe]

the hash of the entry does change.

please provide a reproduction so I can see the issue. 🙏