Bower Support

[tjvantoll]

I figured I'd toss this out there so we have something to brainstorm about.

Here's what I see as the TODOs for external Bower support:

• Extract the jQuery core dependency so it is only declared once.
• Claim the jquery-ui component in Bower (Unregister package requests bower/bower#120).

[tjvantoll]

Per @scottgonzalez's suggestion I'm going to switch the manifest task to read the jQuery dependency from bower.json.

[tjvantoll]

Well that was shockingly easy (0a6598e).

[jzaefferer]

This looks good to me to land as is.

That said, claiming the component should happen before the 1.11 release - and we still have to figure out how to deal with existing apps relying on older versions that we can't provide, since we already have existing tags that don't include the bower.json.

[scottgonzalez]

Bower support will come with 1.11.0, whenever that lands, but datepicker will be odd. Please use IRC or the forums to continue discussions about use of Bower.

[jzaefferer]

Based on mailing list discussion, we shouldn't claim the existing component until we've talked to their maintainers, though if they're interested, we'd just keep them maintaing the package.

We can and still should add a bower.json: To allow installs via bower install jquery/jquery-ui coming directly from our repo, and to specify devDependencies, which we need for #9507.

[tjvantoll]

@jzaefferer I agree. Given that is this good to merge? I'd prefer to handle devDependencies separately.

[jzaefferer]

Yeah, I think this is good to land.

[jzaefferer]

Also components/jqueryui#22

[tjvantoll]

I'll bring this up at the team meeting tomorrow. Unless there are any objections I'll land this and close #9465.

The original commit message still makes sense too I think. We are adding Bower support, we're just not claiming the official jquery-ui repo for it.