Configure Webpack to preserve original asset filenames #4
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.
This PR resolves MIME type errors and deployment issues by configuring Webpack to preserve original filenames for assets instead of generating hashed names.
Problem
Previously, Webpack was generating hashed filenames for all assets (images, fonts, SVGs), causing:
smalltabletview.pngto be renamed to random hashes like70d3469e44bcde70f835.pngSolution
Modified the Webpack configuration to preserve original asset filenames by adding a
generatorconfiguration to theasset/resourcerule:Changes
generator.filename: "[name][ext]"to preserve original asset namesdistdirectorysmalltabletview.pngand other assets are properly copied with readable namesVerification
smalltabletview.pngis correctly copied to dist directoryThis change improves maintainability, reduces deployment complexity, and resolves potential MIME type issues while maintaining all existing functionality.
Created from VS Code via the GitHub Pull Request extension.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.