JS hash changes when src folder moved

[jakearchibald]

• Rollup Version: 1.32.0
• Operating System (or Browser): OSX
• Node Version (if applicable): v12.16.1
• Link to reproduction: https://github.com/jakearchibald/rollup-hash-bug-2

Expected Behavior

The two src folders have identical contents, their output filenames should not differ between builds.

Actual Behavior

All three files change hash.

#2839 may be related.

[lukastaegert]

Interesting point. My feeling is that implementing the improved hashing I outlined in #2872 (comment) might solve this as well, definitely worth keeping as a test case for a new algorithm.

[jakub-g]

I don't know if related, but I was hitting the same kind of issue with webpack, and the problem was that a loader (plugin) transforming an import request used absolute disk path of the file as an internal import identifier (relying on __dirname, path.resolve() and other similar things can lead to this), leading to non-deterministic input (when building inside a different folder for example).

[myarcane]

It is worth mentioning that the bug only exists with code splitting configurations when input takes an array of files :

 input: [`src${num}/index.js`, `src${num}/profile.js`]

Obviously if rollup builds each of these files separately :

// rolllup.config.js
export default ["index.js", "profile.js"].reduce((config, file) => {
 [1, 2].forEach((num) => {
   config.push({
     input: `src${num}/${file}`,
     output: {
       entryFileNames: "[name]-[hash].js",
       dir: "build/" + num,
       format: "esm",
     },
   });
 });
 return config;
}, []);

the hash names remain the same for each source folder.

Maybe a "code splitting" label should be added ?

[lukastaegert]

Fix finally at #4543

[lukastaegert]

Fix finally at #4543

[rollup-bot]

This issue has been resolved via #4543 as part of rollup@3.0.0-7. Note that this is a pre-release, so to test it, you need to install Rollup via npm install rollup@3.0.0-7 or npm install rollup@beta. It will likely become part of a regular release later.

[rollup-bot]

This issue has been resolved via #4543 as part of rollup@3.0.0-8. Note that this is a pre-release, so to test it, you need to install Rollup via npm install rollup@3.0.0-8 or npm install rollup@beta. It will likely become part of a regular release later.

[rollup-bot]

This issue has been resolved via #4543 as part of rollup@3.0.0. You can test it via npm install rollup.