You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content hash seems to include the absolute path of the file. So for the same content, but built in a different directory, a different hash is created.
This causes a problem in e.g. CI build environments where the build directory is different for every build. Since all files get new hashes on every build, the cache is always invalidated.
🐛 bug report
The content hash seems to include the absolute path of the file. So for the same content, but built in a different directory, a different hash is created.
This causes a problem in e.g. CI build environments where the build directory is different for every build. Since all files get new hashes on every build, the cache is always invalidated.
🎛 Configuration (.babelrc, package.json, cli command)
Default configuration.
🤔 Expected Behavior
The hash should be the same for the same file content, no matter what directory it is built in.
😯 Current Behavior
The hash changes when built in a different directory.
💁 Possible Solution
Don't include the current directory when calculating the hash.
🔦 Context
When bundling in CI where the build directory is different for every build, all bundles will always get a new hash.
💻 Code Sample
🌍 Your Environment
The text was updated successfully, but these errors were encountered: