Ticket #9465 (closed feature: fixed)

Opened 17 months ago

Last modified 10 months ago

Add Bower Support

Reported by: scott.gonzalez Owned by:
Priority: blocker Milestone: 1.11.0
Component: [meta] ui.dev Version: 1.10.3
Keywords: Cc:
Blocking: Blocked by:

Description (last modified by joern.zaefferer) (diff)

bower install jquery-ui should install the individual source files with @VERSION replaced. Bower users will be expected to handle minification and concatenation on their own. This should be easily accomplies with the addition of AMD (#9464).

When this is ready, we'll need to claim ownership of the jquery-ui component in the Bower registry:  https://github.com/bower/bower/issues/120

We decided to keep the "jqueryui" package as-is, instead of trying to take it over. That avoids various problems with backwards compatibility for existing bower users.

Change History

comment:1 Changed 17 months ago by scott.gonzalez

  • Priority changed from minor to blocker
  • Status changed from new to open
  • Milestone changed from none to 1.11.0

comment:2 Changed 16 months ago by joern.zaefferer

  • Milestone changed from 1.11.0 to 1.12.0

Not super useful without AMD support, so moving this as well.

comment:3 Changed 11 months ago by scott.gonzalez

  • Milestone changed from 1.12.0 to 1.11.0

comment:4 Changed 11 months ago by tj.vantoll

I looked into this a bit. This is more or less the bower.json we need (minus the dev dependencies, which are covered by #9507):

{
	"name": "jquery-ui",
	"version": "1.11.0pre",
	"ignore": [
		"**/.*",
		"build",
		"demos",
		"dist",
		"external",
		"tests"
	],
	"dependencies": {
		"jquery": ">=1.6"
	}
}

Other than the version, I'm not sure how much value there is in generating this file. The name will almost certainly never change, and we don't have a list of ignorable files, or our jQuery core version dependency stored anywhere currently.

comment:5 Changed 11 months ago by scott.gonzalez

We do have the jQuery core dependency listed  in a grunt task. We should either move that to a separate file and populate both from that or just have the manifest pull the version out of bower.json. Once we start using Bower, I'm ok with treating it as a canonical source for information that doesn't belong in package.json.

Last edited 11 months ago by scott.gonzalez (previous) (diff)

comment:7 Changed 10 months ago by joern.zaefferer

  • Description modified (diff)

comment:8 Changed 10 months ago by TJ VanToll

  • Status changed from open to closed
  • Resolution set to fixed

All: Add Bower support

Fixes #9465 Closes gh-1189

Changeset: e837d11d6b3c8517e322ded24faaa400443402ef

Note: See TracTickets for help on using tickets.