fix(webpack): add content hash to chunks and optimize dev builds #153
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add chunkFilename with contenthash to prevent browser cache conflicts between different explorer builds (e.g., hardhat plugin vs current) - Only minimize in production for faster dev builds - Add sleep before ignition deploy in test env script
|
🚀 Preview: https://pr-153--openscan.netlify.app |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix browser cache conflicts when switching between different explorer builds (e.g., hardhat plugin explorer vs current version) by adding content hashes to chunk filenames.
Related Issue
N/A
Type of Change
Changes Made
chunkFilenamewith[contenthash]to webpack output config[contenthash]to production bundle filenameScreenshots (if applicable)
N/A
Checklist
npm run format:fixandnpm run lint:fixnpm run typecheckwith no errorsnpm run test:runAdditional Notes
When switching between different explorer builds on the same port, the browser serves cached chunks from the old build. Since module IDs differ between builds, this causes "Cannot find module" errors. Using
[contenthash]ensures each build produces uniquely named files - same code = same hash (deterministic), different code = different hash (no cache conflicts).