Fix: remove duplicate component imports breaking production build - #1905
Open
webgo-oss wants to merge 1 commit into
Open
Fix: remove duplicate component imports breaking production build#1905webgo-oss wants to merge 1 commit into
webgo-oss wants to merge 1 commit into
Conversation
|
@webgo-oss is attempting to deploy a commit to the souma9830's projects Team on Vercel. A member of the Team first needs to authorize it. |
Owner
|
Open source programme name @webgo-oss |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
npm run build fails outright with an esbuild syntax error and never produces a production bundle:
[vite:esbuild] Transform failed with 1 error:
ERROR: The symbol "ExifMetadataInspector" has already been declared
Three page components each import the same child component twice at the top level. esbuild treats a duplicate top-level binding as a hard syntax error, not a warning — so the build fails completely rather than just showing a lint warning.
npm run dev doesn't catch this (looser dev-server transform), which is likely why it went unnoticed until someone tried a production build.
Root cause
Duplicate import statements for the same component in:
Fix
Removed the redundant second import line in each file. No logic changes — the components are still used exactly as before via their first (original) import.
Testing
cd frontend
npm install
npm run build
Build now completes successfully (built in ~13s), no esbuild errors.
Changes