Actions
Refactor #12364
closed
Use NPM+Webpack to manage external assets (js, css, fonts)
Difficulty:
Triaged:
Description
Currently, some assets are manually inserted into `vendor/assets` and not automatically updated, while others are added as gem files which do update automatically but require additional packaging work every time they change.
It would be beneficial to use bower to maintain those assets for the following reasons:
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.
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Added by Tomer Brisker over 8 years ago
Added by Tomer Brisker over 8 years ago
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.
Added by Tomer Brisker over 8 years ago
Refs #12364 - Only load the dev server js if it's enabled
Also allow disabling the dev server from the settings file
Added by Marek Hulán over 8 years ago
Refs #12364 - webpack server can serve assets on https
Actions
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
<ohadlevy@gmail.com>