-
-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
contenthash is unstable #3174
Comments
不好意思, 刚刚的仓库包含了 内网域名, 已经被移除, 已经更新了最新的仓库地址 |
contenthash 计算目前确实有些问题,可以开启 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
ye, same issue |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
No, it can be workaround by real content hash, but it's different with this issue |
This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Just take another look in this reproduce, after upgrading less to v4.2.0, the contenthash is stable, before is less v4.1.3, seems related to less/less.js#3567 so close this issue, feel free to re-open it if you have any further questions |
System Info
System: mac os 13.3.1
npmPackages: pnpm 8.1.0
Details
复现仓库
反复多次执行 npm run build , 进入 detail/statics 文件夹, 观察 chunk-shineout.[contenthash:8].js 的文件名 hash 值是不稳定的, 每次都会产生变化
Reproduce link
https://github.com/sheinsight/rspack-demo-contenthash
Reproduce Steps
The text was updated successfully, but these errors were encountered: