npm run build regression

[djixadin]

Environment

• Operating System: Linux
• Node Version: v18.18.1
• Nuxt Version: 3.8.0
• CLI Version: 3.9.1
• Nitro Version: 2.7.0
• Package Manager: npm@9.8.1
• Builder: -
• User Config: -
• Runtime Modules: -
• Build Modules: -

Reproduction

cant reproruce

Describe the bug

in version 3.7.4. when building application on a server rollup used to have same hash with the same repo and same branch.. on 3.8 the hash is different even though files are the same.. tried npx nuxi cleanup but its not a cache thing. the hash is different and js scripts dont load on frontend. its a bunch of 404 errors

Additional context

No response

Logs

No response

[github-actions]

Would you be able to provide a 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?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

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

[djixadin]

reproduction? just run npm run build 2 times one after the other and check .nuxt/dist/client/_nuxt hashes

[danielroe]

You say 'js scripts don't load on front-end'. I can't reproduce this. Would you provide a runnable reproduction?

[djixadin]

They don't load for me on multiple machines. the problem is that the rollup content hash is no longer content hash but appears to be a random generated string. It changes on every build even if the content of the components is the same. on 3.7.4 the hash in consistent

[danielroe]

The reason the hashes differ is that we now have a buildId that is different on each build, so the content is in fact different: #21641.

You can temporarily disable by setting experimental.appManifest to false.

We can improve behaviour here when we implement #23392.