-
Notifications
You must be signed in to change notification settings - Fork 117
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
Keep file structure when using exportsOverride #21
Comments
I guess you can use |
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. |
Can you bring in an example of exportsOverride you have? |
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 |
I would like to see this, too. |
+1 |
1 similar comment
+1 |
+1 |
+1 |
+1 |
1 similar comment
+1 |
Yes! Please stop messing with packages' layouts! |
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. |
Any news on this one? |
+1 |
+1 This is very important indeed |
+1 |
Remove main as grunt-bower-task not complex enough for the layout I want. Monitor issue 21; yatskevich/grunt-bower-task#21
+1 |
1 similar comment
+1 |
Obnoxious comment but, +1 |
+1 it need for copy boost less files structure. Please. |
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.The text was updated successfully, but these errors were encountered: