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 build should be reproducible when code splitting and CSS modules are being used at the same time.
Reproducible means the hashes in the filenames should remain the same if nothing has been changed between the builds.
😯 Current Behavior
The build is NOT reproducible. The hashes in the filenames change every time I build, even nothing has been changed between the builds.
💁 Possible Solution
🔦 Context
I have a CI setup that builds a Docker image that contains parcel-built assets on every push to any branches. So the same commit hash could be built multiple time and then pushed to the registry. Since the build is not reproducible, the content of the Docker image changes even the tag (the git commit in this case) is the same. Thus pulling the Docker image at different time may actually fetch a different image.
In my deployment, I have several k8s pods running the image. If a node fails, a node is spawn. k8s will fetch the image again, which could be different in content with the same hash. So we now have two pods serving two different index.html. The requests to the pods are in a round-robin fashion. The final outcome is that many requests to assets will result in 404 because some assets is available in a pod but not in another.
🐛 bug report
🎛 Configuration (.babelrc, package.json, cli command)
No configuration is required to trigger this bug.
🤔 Expected Behavior
The build should be reproducible when code splitting and CSS modules are being used at the same time.
Reproducible means the hashes in the filenames should remain the same if nothing has been changed between the builds.
😯 Current Behavior
The build is NOT reproducible. The hashes in the filenames change every time I build, even nothing has been changed between the builds.
💁 Possible Solution
🔦 Context
I have a CI setup that builds a Docker image that contains parcel-built assets on every push to any branches. So the same commit hash could be built multiple time and then pushed to the registry. Since the build is not reproducible, the content of the Docker image changes even the tag (the git commit in this case) is the same. Thus pulling the Docker image at different time may actually fetch a different image.
In my deployment, I have several k8s pods running the image. If a node fails, a node is spawn. k8s will fetch the image again, which could be different in content with the same hash. So we now have two pods serving two different index.html. The requests to the pods are in a round-robin fashion. The final outcome is that many requests to assets will result in 404 because some assets is available in a pod but not in another.
💻 Code Sample
I made a code repository to repoduce this issue at https://github.com/louischan-oursky/parcel-bug-codesplit-css-modules
🌍 Your Environment
The text was updated successfully, but these errors were encountered: