Open hughes opened 9 years ago
I have had this argument with coworkers several times, and finally came across an opinion that all your dependencies should be checked into the repo, even if you use bower. It seems like it might be a best practice. http://addyosmani.com/blog/checking-in-front-end-dependencies/ . PS. cool program.
The reason to that script is that the development of every library is simultaneos, I develop Webglstudio and when I miss a feature I go to litegui or litegl or litescene and add that feature. Everytime I modify one of the files I only have to call that script to pack© the resulting files, but if I used something like bower then I will have to add/commit and push for every modification, so I prefeer to use it this way.
But I do not discard to have something like bower once a stable version is reached
Good choice moving to git!
Ideally, there wouldn't be a need to commit files that aren't part of the project itself, such as all these library files.
Using front-end package management like bower could allow you to remove these from the project and only commit the code that'd directly related to webgl studio. You'd only need to maintain a list of dependencies.