We've been using bower for dependency management but it'/ showing signs of disrepair and we should switch back to npm like the rest of the js community. Facebook just announced Yarn, which looks like a good upgrade to npm, so that's worth a look too: https://code.facebook.com/posts/1840075619545360
Also: easy to do while we're at it, let's clean up the dashiki folder structure.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Migrate from bower to npm instead of yarn | analytics/dashiki | master | +5 K -2 K | |
| Clean up folder hierarchy | analytics/dashiki | master | +292 -571 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T148053 Switch to fetch away from jquery | |||
| Resolved | Milimetric | T147884 Migrate from bower to npm and clean up folder hierarchy |
Dependencies need to exist on npm after the replacement is a drop in.
Remove references to bower.
Change 316834 had a related patch set uploaded (by Milimetric):
Clean up folder hierarchy
Change 316904 had a related patch set uploaded (by Milimetric):
[WIP] Migrate from bower to npm instead of yarn
Related discussion on frontend library management: T107561: MediaWiki support for Composer equivalent for JavaScript packages