在文件内容没有变化的情况下，每次打包出来的构建产物javascript文件的hash值都不一致

[DecadeFarewell]

Environment

Operating System: Linux
Node Version: v20.13.0
Nuxt Version: ^3.11.1
CLI Version: 3.11.1
Nitro Version: 2.9.5
Package Manager: npm@10.5.2
Builder: -
Build Modules: ["@pinia/nuxt", "@element-plus/nuxt", "@vite-pwa/nuxt"]

Reproduction

Describe the bug

在文件内容没有变化的情况下，每次执行nuxt build,打包出来的js文件hash值都不一致，这导致我在使用docker进行多实例部署时，每个镜像中的构建产物名称不同，用户在请求js资源时，部分资源出现请求404的情况。

Additional context

No response

Logs

No response

[DecadeFarewell]

现在我可以通过更改构建和发布流程来解决这个问题，我必须在jenkins流水线中完成项目的打包流程，然后在docker镜像启动时运行命令: CMD ["npm", "run", "app"], 但是这样我无法在docker镜像中注入相关的环境变量以供构建过程中使用，因为构建过程已经结束了

package.json:
...
"scripts": {
"build": "nuxt build",
"dev": "nuxt dev --host",
"start": "node ./.output/server/index.mjs",
"app": "pm2 start npm --no-daemon --name portal -- run start",
"generate": "nuxt generate",
"preview": "nuxt preview",
"postinstall": "nuxt prepare"
},

[markthree]

This seems to be a rollup problem, for which there is no good solution at the moment.

But maybe in the future we can solve it with nuxt-build-cache

[warflash]

#27258 looks like your issue might be solved by this?

[yxw007]

现在我可以通过更改构建和发布流程来解决这个问题，我必须在jenkins流水线中完成项目的打包流程，然后在docker镜像启动时运行命令: CMD ["npm", "run", "app"], 但是这样我无法在docker镜像中注入相关的环境变量以供构建过程中使用，因为构建过程已经结束了

package.json: ... "scripts": { "build": "nuxt build", "dev": "nuxt dev --host", "start": "node ./.output/server/index.mjs", "app": "pm2 start npm --no-daemon --name portal -- run start", "generate": "nuxt generate", "preview": "nuxt preview", "postinstall": "nuxt prepare" },

告诉你一个解决方案

1. jenkins 打包时，有个选项：将环境变量注入至构建过程（配置环境变量）
2. 在jenkins 打包前执行一个shell，将注入的环境变量生成一个.env
3. docker 打包项目时，将此.env copy 进app中
4. docker 运行时加载.env 配置文件即可（在Dockerfile 中添加如下启动命令）

# lock the startup env config file 
CMD ["npm","start","--env-file",".env"]

[danielroe]

As @warflash spotted, this issue is resolved in #27258 in the nightly release, or in the next release.

Let me know if not and I'll reopen.