yatskevich
Keep file structure when using exportsOverride
I load a requireJs based lib. As all files that mentioned in the exportsOverride block are put at the main level of lib/js/myDependency/ I cant build the lib with requireJs as the require paths are broken now.
I guess you can use layout option that could be a function, that responsible for strategy of files copying. See docs here https://github.com/yatskevich/grunt-bower-task#optionslayout
Sure, but wouldn't it be the expected behavior that the file structure keeps the same as in the original repo instead of flatting all files in the same folder.
Ok, I have problem with this repo: https://github.com/rsolomon/JSV. It has a nested file structure and us requirejs. So when I load this grunt-bower all files put in the same folder and I have to move them afterwards in the right folder again. This will be a problem for every requirejs based repo.
Yes, now I see the problem. I guess this is something that was not considered in API. Good point for enhancement
Yes! Please stop messing with packages' layouts! AFAIK, there's basically no good way for packages to support having their directory structure reorganized by your tool. References to images+fonts within Less/CSS/Sass break, and then users often blame the package instead of grunt-bower-task.
In the meantime, for people trying to make this work with their grunt setup: grunt-bower does seem to support keeping the folder structure intact. Only thing it doesn't do is install bower packages, but grunt-exec could take care of that.
At this point it might make more sense to just use grunt-contrib-copy.
