Webpack is a tool to compile our frontend dependencies into one or more bundles.
Webpacker is a rails project, handling the integration of webpack into rails, including helpers like
Code living under
Unless you’re doing UI changes, this should be a no-op for you, as long as you run
bin/update after updating ui-classic, or changing branches there, you should be fine -
rake update:ui now not only installs bower & yarn dependencies, it also recompiles these UI assets.
No changes in
This can be done manually, by running
rake webpack:compile, or it can happen automatically on any change, as long as you’re running
bin/webpack --watch from ui-classic.
So… please make sure you’re always running
bin/webpack --watch when doing UI changes (from ui-classic). You will also need to run the rake task at least once, or any time you add/remove a UI plugin.
Webpacker itself doesn’t support rails engines, we have a
rake webpack:paths task which creates an
config/webpack/paths.json config file, with the paths to all the engines, including ManageIQ for output.
Right now, any Rails engine with an
yarn will be called in it), later, this may apply only to plugins which explicitly ask for it.
For more details, please go to https://github.com/ManageIQ/manageiq-ui-classic/pull/1132 .