Bug Tracker

Opened 2 years ago

Closed 2 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:


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 2 years ago by timmywil

  • Component changed from unfiled to build
  • Milestone changed from None to 1.11/2.1
  • Owner set to timmywil
  • Priority changed from undecided to high
  • Status changed from new to assigned

comment:2 Changed 2 years ago by Timmy Willison

  • Resolution set to fixed
  • Status changed from assigned to closed

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.

Changeset: f9ad13c9ec8967916427642db2883a1bf3bccd86

Note: See TracTickets for help on using tickets.