fix(ui): stop forcing the webpack vendor chunk output path#4868
Merged
another-rex merged 1 commit intogoogle:masterfrom Feb 23, 2026
Merged
fix(ui): stop forcing the webpack vendor chunk output path#4868another-rex merged 1 commit intogoogle:masterfrom
another-rex merged 1 commit intogoogle:masterfrom
Conversation
Currently, starting the local development web server with `npm start` reaches this error: ``` <e> [webpack-dev-middleware] Error: Conflict: Multiple chunks emit assets to the same filename static/vendors.js (chunks vendorsJs-node_modules_mini-css-extract-plugin_dist_hmr_hotModuleReplacement_js-node_modules_-335b30 and vendorsJs-node_modules_hotwired_turbo_dist_turbo_es2017-esm_js-node_modules_github_clipboard--ac61ee) <e> at /home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/Compilation.js:5154:12 <e> at /home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/Cache.js:98:34 <e> at Array.<anonymous> (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/cache/MemoryCachePlugin.js:44:13) <e> at /home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/Cache.js:98:19 <e> at Hook.eval [as callAsync] (eval at create (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/tapable/lib/HookCodeFactory.js:31:10), <anonymous>:19:1) <e> at Cache.get (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/Cache.js:82:18) <e> at ItemCacheFacade.get (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/CacheFacade.js:115:15) <e> at /home/timzh/osv.dev/gcp/website/frontend3/node_modules/webpack/lib/Compilation.js:5096:22 <e> at arrayEach (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/neo-async/async.js:2405:9) <e> at Object.each (/home/timzh/osv.dev/gcp/website/frontend3/node_modules/neo-async/async.js:2846:9) ``` The issue as I understand it is that webpack tries to write to the same vendor.js file twice independently. I think ed504ac introduced the issue when it added a second entry point: google@ed504ac#diff-9f8239968359c3509ed79cdc472a92a08b4aea2446077d8cd8453fcb59ffd711R11. Using `name` groups by a logical ID. It doesn't change any build artifacts' paths, so shouldn't affect the frontend's deployment, I think.
cuixq
approved these changes
Feb 22, 2026
Contributor
|
Not sure why you are running |
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
3 participants
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.
Currently, starting the local development web server in
gcp/website/frontend3withnpm startreaches this error:The issue as I understand it is that webpack tries to write to the same vendor.js file twice independently.
I think ed504ac introduced the issue when it added a second entry point: ed504ac#diff-9f8239968359c3509ed79cdc472a92a08b4aea2446077d8cd8453fcb59ffd711R11.
Using
namegroups by a logical ID. It doesn't change any build artifacts' paths, so shouldn't affect the frontend's deployment, I think.