Bug #25882: webpack plugin compilation ignores all but main index.js entry - Foreman

Bug #25882

webpack plugin compilation ignores all but main index.js entry

Added by Justin Sherrill about 1 year ago. Updated 12 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Justin Sherrill

Category:

JavaScript stack

Target version:

1.21.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/6436, https://github.com/theforeman/foreman/pull/6429, https://github.com/theforeman/foreman/pull/6421

Fixed in Releases:

1.21.0

Found in Releases:

Description

script/plugin_webpack_directories.rb#L28 supports plugins to have multiple 'bundles/entries' of assets, however during production compilation, these extra bundles are ignored:

https://github.com/theforeman/foreman/blob/develop/config/webpack.config.js#L73

Related issues

Associated revisions

Revision 202c65d0 (diff)
Added by Justin Sherrill 12 months ago

Fixes #25882 - compile extra bundles during plugin compile

Revision 92a0079a (diff)
Added by Justin Sherrill 12 months ago

Refs #25882 - use working iterator for webpack entries

Revision 22c7c988 (diff)
Added by Ewoud Kohl van Wijngaarden 12 months ago

Refs #25882 - Load additional plugin chunks

When loading the manifest.json from a plugin we need to include plugin
and plugin:*.

bc486dd62734be908cd3f95da1352cc1944eb34b attempted to make it possible
to create additional bundles. 202c65d0efc0345b883ba6d1e70aedc90b3d5294
then configured webpack to actually compile the bundle during build.
This completes the chain by loading it in the actual manifest so you can
use it in a production build where the development server isn't present.