Dealing with git, generated files and bower

Question

I know that it is considered a bad practice to commit generated files to a git repository. But how to deal with bower?

Currently my library is built into a dist/ directory which gets ignored by a .gitignore file. I don't want generated files pushed to the repository. The problem is that the library is also distributed as a bower component.

How can I reference the generated assets into my bower component when a new version got released? Should I create another repository to store those files? Should I commit those files to the git tagged version?

Related: ignore `bower_components` or not: http://stackoverflow.com/questions/22327758/bower-shouldnt-we-gitignore-something — Ciro Santilli OurBigBook.com, Jun 17 '14 at 08:52

score 4 · Accepted Answer · answered Sep 26 '13 at 23:34

4

You've already mentioned your choices. There aren't really a best way. Choose what you prefer. Either create a new repo or commit the /dist folder. Both have upsides and downsides. Creating a repo makes it more cumbersome to update and committing makes the repo more bloated.

The Bower team is working on a way to publish releases to a server, which will resolve this issue.

answered Sep 26 '13 at 23:34

Sindre Sorhus

62,972
39
168
232

3

any movement on this? We're starting to use bower as a way of install javascript libs and the bloat is astronomical. – obie Apr 08 '14 at 16:06
@Sindre can you link to a source for the release server initiative? – Ciro Santilli OurBigBook.com Jun 17 '14 at 08:51

score 0 · Answer 2 · edited May 23 '17 at 12:23

0

I would like to challenge the idea that committing built files is a bad practice, and I do that in this question.

About handling built files with git, check also this excellent post.

edited May 23 '17 at 12:23

Community

1
1

answered Jan 21 '14 at 13:30

danza

11,511
8
40
47

Dealing with git, generated files and bower

2 Answers2

Linked