Consolidate JS dependency install with npm
Bug #1680624 reported by
Dan Scott
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We currently use npm to install development dependencies and bower to install front end dependencies. While this reflected common practices a few years ago, many projects are now consolidating the two methods of installing dependencies by simply using npm. Removing one build step would remove one more potential source of errors.
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
See http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/lp1680624_ bower_to_ npm for a first stab at this. Tests pass, and there appear to be no regressions in the handful of staff client interfaces I've tried to date.