Project

General

Profile

Actions

Refactor #12364

closed

Use NPM+Webpack to manage external assets (js, css, fonts)

Added by Tomer Brisker over 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Packaging
Target version:

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:
  1. Reduce packaging work.
  2. Allow more frequent updates of included assets, as updates will not require separate repackaging.
  3. Allow simple updates to assets which don't have a gemified version.
  4. Allow timely updates to assets who's gemified versions are not up to date.

Related issues 5 (0 open5 closed)

Related to Foreman - Bug #16046: "Don't know how to build task 'webpack:compile'" running jenkins:integration taskClosedDominic Cleal08/10/2016Actions
Related to Foreman - Bug #16074: development version listens on 0.0.0.0:3000 and 0.0.0.0:3808 by defaultClosedShlomi Zadok08/11/2016Actions
Related to Foreman - Feature #16160: Add shell script to start foreman-webpackClosedLukas Zapletal08/18/2016Actions
Related to Foreman - Bug #17236: webpack source maps do not workClosedOhad Levy11/06/2016Actions
Related to Discovery - Bug #19403: js error of missing jquery.cookieClosedTomer Brisker04/27/2017Actions
Actions #1

Updated by Tomer Brisker over 8 years ago

It would seem that bower is no longer being actively developed
So it would seem we should look into other options for handling assets, possibly npm.

Actions #2

Updated by Tomer Brisker about 8 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

Actions #3

Updated by The Foreman Bot about 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Assignee set to Tomer Brisker
  • Pull request https://github.com/theforeman/foreman/pull/3433 added
Actions #4

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version set to 1.7.1
Actions #5

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version deleted (1.7.1)
Actions #6

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version set to 1.7.1
Actions #7

Updated by Tomer Brisker almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #8

Updated by Dominic Cleal almost 8 years ago

  • Translation missing: en.field_release set to 160
Actions #9

Updated by Dominic Cleal almost 8 years ago

  • Related to Bug #16046: "Don't know how to build task 'webpack:compile'" running jenkins:integration task added
Actions #10

Updated by The Foreman Bot almost 8 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3721 added
Actions #11

Updated by The Foreman Bot almost 8 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3722 added
Actions #12

Updated by Dominic Cleal almost 8 years ago

  • Related to Bug #16074: development version listens on 0.0.0.0:3000 and 0.0.0.0:3808 by default added
Actions #13

Updated by The Foreman Bot almost 8 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3734 added
Actions #14

Updated by Lukas Zapletal almost 8 years ago

  • Related to Feature #16160: Add shell script to start foreman-webpack added
Actions #15

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version changed from 1.7.1 to 1.6.2
Actions #16

Updated by Daniel Lobato Garcia almost 8 years ago

  • Target version changed from 1.6.2 to 1.7.1
Actions #17

Updated by Ohad Levy over 7 years ago

  • Related to Bug #17236: webpack source maps do not work added
Actions #18

Updated by Ohad Levy about 7 years ago

  • Related to Bug #19403: js error of missing jquery.cookie added
Actions

Also available in: Atom PDF