support glob in bower main property

[gernsdorfer]

Support globing for files in main property of bower.json.
With that change we want eliminate dist directory, so no build is necessary and no dist is under version control. This avoids unnecessary conflicts and tags which contain the wrong version (if build forgotten).

See also bower/bower#935 and bower/spec#30

[ruyadorno]

I would rather wait for the official spec update from the @bower team before landing this on wiredep.

[stephenplusplus]

I actually don't mind supporting this. The more time that goes on, the more it seems the Bower community isn't waiting on decisions, and instead using what makes sense.

[stephenplusplus]

Please follow the code style - 2 space indentation.

[stephenplusplus]

I made some changes -- can you check if this works: c70d1f3

if it does, I'll merge that branch in instead of this PR.

[gernsdorfer]

work's fine.:thumbsup:

[stephenplusplus]

Cool, merged that in. 👍 Thanks for this!

[CWSpear]

I actually don't mind supporting this. The more time that goes on, the more it seems the Bower community isn't waiting on decisions, and instead using what makes sense.

Poor Bower :-( But I don't disagree. That's the theme of my first PR (overrides). And I think wiredep is gaining enough traction that people can tell other plugins, "but wiredep does it!" and maybe implement it.

But with the added wiredep().js syntax, I've changed my approach and don't even need those other plugins that use the overrides syntax =)

[stephenplusplus]

"but wiredep does it!"

👯 💃 👍 🎉 🎈 🎂

[ruyadorno]

Great! TBH I do agree that wiredep should have a more active role, taking stances like this, specially in the stalled state of bower lately. I just didn't expected you guys would think the same 😊

[zarno]

Nice work! Thanks heaps.