Added bower support

[joshhornby]

Added a task which will take js or css files from the bower components directory and add them into the public directory.

One think worth noting is I have to require the packge 'main-bower-files' in the JS as I can't use 'gulp-load-plugins' See this issue for more details

ck86/main-bower-files#29

[JeffreyWay]

I think Taylor and I will need to sit down and figure out how many things like this we want to add. Will keep you posted. :)

[syhol]

To add to this, I think the bower_components directory could sit nicely in the resources or resources/assets directory using bowers directory config (http://bower.io/docs/config/#directory). This could be configured using a .bowerrc located in top level of the project.

Big +1 to this PR. This would complete my front end workflow

[joshhornby]

Nice idea @syholloway.

And yes I agree, I defiantly think this is something Elixir should have :)

[Crinsane]

I'd also really like this to be included. Bower is such an important part of my 'frontend workflow'.

[michgeek]

Yeah ! Just discovered Elixir and I was wondering if bower will be supported.

[stalmok]

Great work Jeff!
Bower could be used together with Elixir if it wouldn't force to put style files into sass and less directories. In that case we could mix bower components and our styles by choosing files individually:

mix.sass(['bower/foundation/scss/foundation.scss', 'sass/styles.scss'])

I could prepare a PR.
Let me know what you think.

[michgeek]

Do you mean that in addition to use of bower, we have to manually specify which component we wish to mix ?

I had the idea that everything in the bower components folder would be mixed automatically and we wouldn't worry about selecting the component individually. Plus injecting the components to the different views. What about simply use mix.bower() ?

[stalmok]

I was suggesting other way for Elixir to allow us to use bower packages, but now I see it's a wrong approach anyway, just ignore it. Sorry.

As for the initial idea, I would like to suggest for mix.bower() to accept config object and pass it on to 'main-bower-files' plugin. That would allow us to ignore packages, include dev dependencies and so on.

[gvsrepins]

Bower will be a nice feature if included as default.

[thangchung]

Yes, I also agree that Bower should be included into default ingredient for Elixir

[joshhornby]

Guessing this can be closed @JeffreyWay as we can now build extensions unless you want this as something for the core?

[randomor]

+1 for out-of-box bower support. I'm now downloading packages into resources directory and include them, but wondering if there is a nicer way.

[xjrcode]

+1. I'm totally with @syholloway

[loganhenson]

Im curious as to what this would look like, bower is used so many different ways it seems almost impossible

—
Sent from Mailbox

On Sat, Oct 18, 2014 at 7:42 AM, Xavi notifications@github.com wrote:

+1. I'm totally with @syholloway

Reply to this email directly or view it on GitHub:
#6 (comment)

[joshhornby]

It would work by pulling in all your bower files and bundling them into one vendor.css folder. Same can be done for js.

@JeffreyWay Any thoughts on this? Seems a popular choice.

[Crinsane]

For anyone interested, I took this code and made in into an extension.

https://www.npmjs.org/package/laravel-elixir-bower
https://github.com/Crinsane/laravel-elixir-bower

[Foxandxss]

Bower gives me shivers but I think it should probably be core.

[wutmikee]

Bower is a must. Make or break. Period.