webpack.config.vendor.js and Tree-Shaking #1501

New Issue

fergalmoran · 2025-08-09T17:20:22Z

fergalmoran commented

2025-08-09 17:20:22 +00:00

Originally created by @avanderhoorn on 7/18/2016

As an observation, how will webpack.config.vendor.js work as Tree-Shaking becomes more common. Quickly looking at webpack.config.vendor.js it doesn't seem to have knowledge about whats being used vs not... If this is the case, maybe the prod build could work in vender dependencies there (hence webpack.config.vendor.js is only used at dev time) and webpack.config.prod.js could output the vendor as a separate file then, hence getting the best of both worlds.

*Originally created by @avanderhoorn on 7/18/2016* As an observation, how will `webpack.config.vendor.js` work as Tree-Shaking becomes more common. Quickly looking at `webpack.config.vendor.js` it doesn't seem to have knowledge about whats being used vs not... If this is the case, maybe the prod build could work in vender dependencies there (hence `webpack.config.vendor.js` is only used at dev time) and `webpack.config.prod.js` could output the vendor as a separate file then, hence getting the best of both worlds.

fergalmoran closed this issue

2025-08-09 17:20:22 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1501