jQuery getting too big?
The primary goal of this project would be for the feedback/demand to kickstart jquery.com into re-organizing its code-base so it's more modular since we believe we've proved the most useful parts of jQuery is a fraction of its code-base.
To this end, follow this project if you want jquery.com to measure the demand for this. Another project with similar goals is http://ender.no.de/ - for node.js.
Based on recent posts it does looks like jQuery wants to build a slimmer jQuery. Although instead of just giving a trim, we hope they perform larger re-structural changes allowing us to use most of the useful parts at a fraction of their cost. Their recent conversations into future file size reduction sound promising.
Disclaimer: This is NOT an official jQuery.com project. Also some things are not fully implemented, please report back issues so we can measure the API popularity of missing pieces.
- New! - Build customizable jquip packages with the new jQuip Library Builder service.
- Node js build scripts added to minify jquip with UglifyJS.
- We want jquip core to work well
Spine.js so as a minium, we'll need:
- Improved $().find
- More plugins!
Introducing jquip - aka jQuery-in-parts.
Smaller, Lighter, Faster, more modular jQuery - include only the parts you want! Don't use it, Don't include it.
The core jquip.js is only 4.28KB (minified and gzipped) only 13% of the size of jQuery.
Has 90% of the good parts of jQuery (rest to be added plugins as needed), small enough to drop-in as source saving an external js reference.
Includes 7-8x Faster DOM traversal for <= IE7. (i.e. where there's no querySelector) *see limitations below.
Most code has been ported from jQuery and optimized where possible, e.g. internals use underscore's native
_.each over jquery's slower
What's in the box? - i.e. the 90% good parts
Methods marked with * are only partially implemented.
- $(selector, context), $(element), $(array)
- $(callback) requires docready plugin.
Methods operating on a
- hide, show, fadeIn and fadeOut - does so without animation, consider using jquery.animate-enhanced plugin*
- val - does not do checkbox, select, etc.
blur focus focusin focusout load resize scroll unload click dblclick mousedown mouseup mousemove mouseover mouseout mouseenter mouseleave change select submit keydown keypress keyup error
static methods off $
- $.each and Underscore's faster $._each
- $.fromHtml - creates a document fragment from a html string
- $.walk - traveres all descendents including self (predicateFn, [[, context], results])
- $.queryAll - querySelector || Sizzle if exists otherwise limitedQueryAll*
- $.attrs - an elements attributes
- $.unique - return a unique list of elements in document order
Pick and choose the parts of jQuery when and add you use them.
Other parts of jQuery can be Added via Plugins which is simply a matter of copying or including the
script after the core
yep, it's a plugin!
based on David Flanagan HttpUtils modfied to work like jQuery's ajax.
- $.queryString - cached map of queryString variables
- $.is[Tab|Enter|Shift|...] - static functions to detect named keys pressed, e.g.
if ($.isEnter(e)) console.log("pressed enter")
- $.cancelEvent - cross-browser fn to
stopPropogation(), returns false.
Parts of jQuery that aren't ported over (because of code size) throw a "not implemented exception". At the moment this only gets thrown for complex filters that filter (i.e $().find) on more than a tagName.
- For <= IE7 all selectors require an Id (i.e. #) Tag (e.g. INPUT) or class name in each child selector.
- TBODY TD.c1 INPUT
- TH.c1 STRONG
- #btnSubmit SPAN
- FORM INPUT[name='chkProcess']
- FORM INPUT[type='text']
- FORM INPUT[type]
- FORM#id .a.b
Events passed to your event handers are the 'real' browser DOM events. You can use the jquip.custom $.namedKey() feature for cross-browser key detection.
jquip Library Builder Service
The project now includes the node.js /server/jquip.builder.js so you can host your own jquip Library builder service internally.
I'd love help with this so Contributors and pull requests are very welcome!
The main task that needs doing is to get all the missing jQuery parts in as plugins and a comprehensive test suite so we can properly identify the parts of jQuery supported.
Feedback is welcome, drop me a line on @demisbellot.