Next.js: Support array of webpack configs in next.config.js
Issues like #774 & #972 are fine as long as the new entry-point can have vendors & commons.js extracted the same as main.js.
Resolving this _requires exporting a different webpack config_, but the signature requires return config;, as return [config, otherEntryConfig]; fails.
If an array of configs were supported by default, having separate build targets (e.g. #1245) & entry-points could be possible.
ericclemmons
All 4 comments
@ericclemmons Yep. That should be possible.
But it might cause a duplication of modules in two bundles.
arunoda
on 28 Feb 2017
@arunoda That's correct and to be expected by multiple configs (potentially) referencing shared modules.
What next does today by remove duplicates between pages is smart, but isn't necessarily applicable to all scenarios (server, or providing <script> tags to 3rd parties).
ericclemmons
on 28 Feb 2017
My current project would greatly benefit from this. I am happy to contribute if given a direction.
dylanjt
on 26 Feb 2018
Having multiple build targets manually by manipulating webpack is not something we want to expose to users. We do want to expose build targets however. This will be added in the near future.
This is a rather old issue, but since Next.js 5.0 we run webpack on both server and client code, solving most issues related to universal compilation.
timneutkens
on 12 Nov 2018
Related issues
flybayer
路
3Comments
jesselee34
路
3Comments
ghost
路
3Comments
kenji4569
路
3Comments
wagerfield
路
3Comments
Most helpful comment
@arunoda That's correct and to be expected by multiple configs (potentially) referencing shared modules.
What
nextdoes today by remove duplicates between pages is smart, but isn't necessarily applicable to all scenarios (server, or providing<script>tags to 3rd parties).