webstaff: EXPAND_WEB_IMPORTS = 0 no longer works

Bug #1770212 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

As a consequence of the patches for bug 1739803, a minimized CSS file (e.g., evergreen-staff-client-deps.0.0.1.min.css) is no longer ever produced for the web staff client. As a consequence, setting EXPAND_WEB_IMPORTS to 0 (as was initially attempted in the branch for bug 1766716) no longer works at all, as it causes web staff client CSS to never be loaded.

Either EXPAND_WEB_IMPORTS should be remove entirely from the templates or CSS minification added back as an option.

Evergreen 3.1+

Galen Charlton (gmc)
Changed in evergreen:
importance: Undecided → Medium
milestone: none → 3.1.2
Revision history for this message
Bill Erickson (berick) wrote :

Since EXPAND_WEB_IMPORTS only affects CSS now, with webpack doing the JS-side aggregation, I propose we teach webpack to create evergreen-staff-client-deps.0.0.1.min.css, have the base template load it by default, and deprecate EXPAND_WEB_IMPORTS. Basically, the same thing we did with the JS. I don't see any particular benefit to loading the individual CSS files.

Bill Erickson (berick)
Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
status: New → Confirmed
Revision history for this message
Bill Erickson (berick) wrote :

Branch pushed:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1770212-webpack-for-css

This uses webpack for generating a combined, minified "vendor" css file. This file is imported by default in the base.tt2 template. The EXPAND_WEB_IMPORTS test has been removed. The individual CSS files are still copied into the web css directory if needed, but they will be unused unless explicitly referenced.

Installing this branch requires running 'npm update' in the staff JS directory.

tags: added: pullrequest
Changed in evergreen:
assignee: Bill Erickson (berick) → nobody
Changed in evergreen:
milestone: 3.1.2 → 3.1.3
Changed in evergreen:
milestone: 3.1.3 → 3.1.4
Changed in evergreen:
milestone: 3.1.4 → 3.1.5
Changed in evergreen:
milestone: 3.1.5 → 3.1.6
Changed in evergreen:
milestone: 3.1.6 → 3.2.1
Changed in evergreen:
milestone: 3.2.1 → 3.2.2
Changed in evergreen:
milestone: 3.2.2 → 3.2.3
Changed in evergreen:
milestone: 3.2.3 → 3.3-beta1
Changed in evergreen:
milestone: 3.3-beta1 → 3.3-rc
Changed in evergreen:
milestone: 3.3-rc → 3.3.1
Changed in evergreen:
milestone: 3.3.1 → 3.3.2
Changed in evergreen:
milestone: 3.3.2 → 3.3.3
Changed in evergreen:
milestone: 3.3.3 → 3.3.4
Changed in evergreen:
milestone: 3.3.4 → 3.3.5
Changed in evergreen:
milestone: 3.3.5 → 3.4.2
Changed in evergreen:
milestone: 3.4.2 → 3.4.3
Changed in evergreen:
milestone: 3.4.3 → 3.4.4
Changed in evergreen:
milestone: 3.4.4 → 3.5.1
Changed in evergreen:
milestone: 3.5.1 → 3.5.2
Changed in evergreen:
milestone: 3.5.2 → 3.6.1
tags: added: cleanup
Changed in evergreen:
milestone: 3.6.1 → 3.6.2
Changed in evergreen:
milestone: 3.6.2 → 3.6.3
Changed in evergreen:
milestone: 3.6.3 → 3.6.4
Changed in evergreen:
milestone: 3.6.4 → 3.7.2
no longer affects: evergreen/3.1
no longer affects: evergreen/3.2
no longer affects: evergreen/3.3
no longer affects: evergreen/3.4
no longer affects: evergreen/3.5
Changed in evergreen:
milestone: 3.7.2 → 3.7.3
no longer affects: evergreen/3.6
Changed in evergreen:
milestone: 3.7.3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.