Opened 5 years ago
Closed 5 years ago
#14615 closed feature (fixed)
Manage bower dependencies with grunt-bowercopy
| Reported by: | timmywil | Owned by: | timmywil |
|---|---|---|---|
| Priority: | high | Milestone: | 1.11/2.1 |
| Component: | build | Version: | 1.10.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
grunt-bowercopy allows us to be specific about where we'd like to put bower dependencies in a very readable and maintainable format. This also lends itself to track bower dependencies, about which some team members have expressed concern.
Change History (2)
comment:1 Changed 5 years ago by
| Component: | unfiled → build |
|---|---|
| Milestone: | None → 1.11/2.1 |
| Owner: | set to timmywil |
| Priority: | undecided → high |
| Status: | new → assigned |
comment:2 Changed 5 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Manage bower dependencies with grunt-bowercopy
Tracked bower dependencies are located at "src/sizzle" and "test/libs". The source-destination mapping is in the Gruntfile.
When updating a bower dependency, update the version in bower.json, run
grunt bower, and then commit the result. When adding a dependency, update the bowercopy task accordingly.Fixes #14615. Closes gh-1452.