-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Bower Support / No need to compile library dependencies #166
base: master
Are you sure you want to change the base?
Conversation
Not sure that jquery-ui needs to be added to this dest directory. |
Is there a reason it is there in the first place? I never changed anything to the grunt file. So whatever is in the dist/dest was there in the build processes originally. |
They're just here for the demo page, which is included in the package. I can remove them, I probably will. The problem of this bower support is that it uses git for storing minified versions of source files. And I do not want to do this. It's like requiring to store binary executables in the same place as source code in C (or whatever). I don't like the idea. Plus, it's a pain to maintain. Now, if you come with a better idea, I'll agree to consider it and support bower. |
We can add whatever you want to ignore to the .gitignore and bower ignore list Let me know what should be in the ignore list. |
Removing dest / dist files that are not a end product for bower .
I don't completely get your point, but as I'm not an user of bower, if you
|
I just modified the .gitignore to not add non "end product" library files that are in the dest directory after a build. This way only what should be registered to be in bower is more to the point. I cleaned up the dest directory as well. |
including dest and prebuilt js files
Please see this post with regards to bower standards.
http://stackoverflow.com/questions/17170500/how-make-bower-build-the-package