Skip to main content

Bug Tracker

Side navigation

#177 closed feature (wontfix)

Opened September 04, 2006 10:04AM UTC

Closed March 31, 2011 03:44PM UTC

Buildable jQuery

Reported by: john Owned by: corey (ml at synthet
Priority: low Milestone:
Component: build Version: 1.4.3
Keywords: dependencies build Cc:
Blocked by: Blocking:

Make jQuery build-able, by choosing a number of components and plugins.

Attachments (0)
Change History (11)

Changed October 15, 2006 03:01AM UTC by john comment:1

component: coresite

Changed November 17, 2006 08:10PM UTC by john comment:2

cc: →
milestone: → 1.1
owner: johncorey (ml at
version: → 1.1

Changed December 31, 2006 02:34PM UTC by joern comment:3

milestone: 1.1
version: 1.1

Changed January 07, 2007 11:10PM UTC by john comment:4

description: It seems as if when you try to build a version of jQuery on the web site, it only gives one version of the code.Make jQuery build-able, by choosing a number of components and plugins.
summary: Build jQueryBuildable jQuery
type: bugfeature

Changed March 11, 2009 04:44PM UTC by dantman comment:5

This is actually something I'm interested in, even in working on.

I can note that AJAX and FX are two core parts which could definitely be turned into "recommended" modules that you could optionally eject to get a smaller jQuery bundle if you don't need them.

As well, there are some official plugins like color animation support which could nicely be used as optional modules that could be built into jQuery.

A nice builder could support exporting a single jQuery file with everything inside, a minified version of that, or an archive (zip, .tar.gz, ...) containing individual script files which could be concatenated and minified on the fly by some script ported to different languages.

Changed November 01, 2009 03:09PM UTC by wilhemd comment:6

Why not building jQuery with maven ?

Here is an example of a builder i am working on with David Meunier :

In this project i suggest you to see JSbuilder, a maven Plugin for JS/CSS Importing, Building, Testing and Reporting.

The idea is to build our JavaScript application from many sources (extra libs or personal) as jQuery, jQuery-ui, plugins and many others by importing the sources we want. Then we build and test the application and release it into our repository.

If you are interested by this project you can subscribe to the mailing list here :

Changed February 05, 2010 09:09PM UTC by john comment:7

component: sitebuild
need: → Review

Changed October 21, 2010 06:38PM UTC by SlexAxton comment:8

keywords: → dependencies build
milestone: → 1.5
priority: majorlow
status: newopen
version: → 1.4.3

John has addressed this on several occasions, he doesn't really have any plans to break apart the dependencies fully, but he's said that AJAX and fx may come out eventually.

I'll keep this ticket as open, only because he's shown _some_ interest in getting those two parts out.

Related, jQuery is now testable (as of 1.4.3) as individual files in the src directory (no build step needed...)

Changed January 02, 2011 09:16PM UTC by snover comment:9

milestone: 1.5

Changed January 03, 2011 03:29AM UTC by comment:10

For posterity's sake, this ticket was originally intended to be a web interface where someone could select the jQuery pieces they wanted and a server-side script would spit out a custom version. I personally would close it because the library landscape (both jQuery and it's "competitors") has changed so dramatically from where we were four years ago. IIRC this ticket was originally inspired by a UI library that had a similar web interface to what I just described.

Changed March 31, 2011 03:44PM UTC by addyosmani comment:11

resolution: → wontfix
status: openclosed

Because as John's said on numerous occasions that he would prefer not to break apart core and it's dependencies, but also due to 1) jQuery's dependancies being quite tightly coupled right now, 2) the age of this ticket and the fact that at this time, I can't see there being a change in mindset on a web interface based build of jQuery being made available, I think it would be best if we closed this ticket.

If it's the case that enough of the community request this type of build during the roadmap and feature discussions, I'm sure some additional consideration will be given to it, but I think this decision will probably revolve around a much larger future discussion if John does decide to go down that path with it.