Multi config webpack to use same template

[gaje]

If i have a multiple config webpack (https://webpack.js.org/configuration/configuration-types/#exporting-multiple-configurations), I'm looking for a way to be able to share a common template and inject all assets built by all configurations into the same template.

Currently, the template just gets overwritten.

Use case: I am trying to generate two separate bundles: modern and legacy (one gets loaded via type="module" other uses nomodule attribute. I need to be able to run different babel configurations against these, so i need to use separate configs - but i want both assets to be included into the same template

[goodmind]

any updates?

[ghost]

I'd also appreciate such a feature

[jantimon]

I am not sure if a webpack plugin can be shared for multiple instances.
@Sparki2002 @goodmind @gaje could you please try to find out if thats possible?

[davilima6]

I don't know if a plugin instance can be shared but, discussing another approach, what if filename is the same in multiple plugin instances but we add an update boolean option like in assets-webpack-plugin? Do you think it'd be possible having multiple compilations incrementally writing the file?

I'm not sure whether we'd get race conditions (e.g. can't open file for write) because from my tests multi-target compilation is async. I can't say if one waits the other to be finished but at minimum you cannot guarantee the order in which each compilation happens, when you tap into done hook for inspection, for example (even though it's only documented developer should input them as an array, which hints to another expectation, shrugs). Anyway that's the approach suggested in https://calendar.perfplanet.com/2018/doing-differential-serving-in-2019/ And also discussed in gatsbyjs/gatsby#2114

---

PS: Here are two example of working around the absence of this flag, tapping into htmlWebpackPluginBeforeHtmlGeneration and htmlWebpackPluginAlterAssetTags, htmlWebpackPluginAfterHtmlProcessing hooks in the first case and htmlWebpackPluginAlterAssetTags and htmlWebpackPluginAfterHtmlProcessing only in the other:

• https://github.com/variejs/varie-bundler/blob/76a2dc6a3c54135c9f8c003fcd34f07ccaad5338/plugins/MultiBuild.js
• https://github.com/nuxt/nuxt.js/blob/fc4abddc5a831141d7387134f0f40cae08e6b83c/packages/webpack/src/plugins/vue/modern.js

They also change link and script tags attributes (and both inject a safari 10 fix) and I understand html-webpack-plugin prefers doing One Thing Only so I'm currently relying on script-ext-html-webpack-plugin but may change that.

[davilima6]

Even though I do support adding such flag I should say I'm currently outputting to different files in each config and plan to use user agent sniffing at Nginx or backend to serve the safe version because the type="module" + nomodule strategy is pretty limited and hits my use case. For example, the two latest versions of Edge (17-18 currently) do not handle it correctly and execute three (!) downloads: one nomodule and twice the same module one 🤦‍♂️ See: philipwalton/webpack-esnext-boilerplate#1 (comment) and https://twitter.com/benjamn/status/1005104014944538624

[stale]

This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days.

[nishant-labs]

I would love to have this feature, specially when I need to get asset files generated by array of configuration passed to webpack.
Also it will be great if that is available in assets parameter in templateParameters function as well.

[sshrshnv]

Is there any progress?

[stale]

This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days.