Skip to content
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

Open
eskimoblood opened this issue Apr 8, 2013 · 22 comments
Open

Keep file structure when using exportsOverride #21

eskimoblood opened this issue Apr 8, 2013 · 22 comments

Comments

@eskimoblood
Copy link

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.

@fantactuka
Copy link
Collaborator

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

@eskimoblood
Copy link
Author

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.

@fantactuka
Copy link
Collaborator

Can you bring in an example of exportsOverride you have?

@eskimoblood
Copy link
Author

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.

@fantactuka
Copy link
Collaborator

Yes, now I see the problem. I guess this is something that was not considered in API. Good point for enhancement

@fantactuka fantactuka reopened this Jun 8, 2013
@hamishtaplin
Copy link

I would like to see this, too.

@DoCode
Copy link

DoCode commented Sep 12, 2013

+1

1 similar comment
@ghost
Copy link

ghost commented Nov 12, 2013

+1

@RishiRamraj
Copy link

+1

@yatskevich yatskevich mentioned this issue Dec 11, 2013
10 tasks
@cvn
Copy link

cvn commented Feb 24, 2014

+1

@kenwarner
Copy link

+1

1 similar comment
@dr-potato
Copy link

+1

@cvrebert
Copy link

cvrebert commented May 8, 2014

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.

@dr-potato
Copy link

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.

@kevin-smets
Copy link

Any news on this one?

@jeroenpelgrims
Copy link

+1

@jcano
Copy link

jcano commented Oct 20, 2014

+1 This is very important indeed

@MikeMengell
Copy link

+1

MikeMengell added a commit to MikeMengell/bower-jasmine-standalone that referenced this issue Jan 15, 2015
Remove main as grunt-bower-task not complex enough for the layout I want.  Monitor issue 21;
yatskevich/grunt-bower-task#21
@j3ffb
Copy link

j3ffb commented Jun 16, 2015

+1

1 similar comment
@afloyd
Copy link

afloyd commented Aug 25, 2015

+1

@andreicek
Copy link

Obnoxious comment but, +1

@black78
Copy link

black78 commented Nov 9, 2015

+1 it need for copy boost less files structure. Please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.