Use NPM+Webpack to manage external assets (js, css, fonts)
It would be beneficial to use bower to maintain those assets for the following reasons:
- Reduce packaging work.
- Allow more frequent updates of included assets, as updates will not require separate repackaging.
- Allow simple updates to assets which don't have a gemified version.
- Allow timely updates to assets who's gemified versions are not up to date.
Fixes #12364 - Use NPM+Webpack to handle external assets
This commit introduces NPM and Webpack to handle external assets.
It also provides ES6 support and a live reload dev server that can be
used by running `foreman start` instead of `rails start`.
Do not forget to run `npm install` before starting the server.
This commit also contains some code that was created by Ohad Levy
Refs #12364 - Allow running webpack dev server on any hostname
Currently, SecureHeaders only allows running the webpack dev server from
localhost or 0.0.0.0, and only using http. This leads to issues when
attempting to run foreman inside a virtual machine or using https. This
patch will generate the correct headers during runtime, to allow the dev
server to be run on the same host and protocol as the request uses.
Refs #12364 - Only load the dev server js if it's enabled
Also allow disabling the dev server from the settings file
#2 Updated by Tomer Brisker about 4 years ago
- Subject changed from Use bower to maintain external assets (js, css, fonts) to Use NPM+Webpack to manage external assets (js, css, fonts)
- Status changed from New to Assigned
Changed this to NPM+Webpack following discussion in https://github.com/theforeman/rfcs/pull/3