jQuery — New Wave JavaScript Meetings are currently held on the matrix.org platform. Meeting minutes can be found at meetings.jquery.org. The latest version of jQuery is available at https://jquery.com/download/. Version…
jQuery — New Wave JavaScript
Meetings are currently held on the matrix.org platform.
Meeting minutes can be found at meetings.jquery.org.
The latest version of jQuery is available at https://jquery.com/download/.
Version support
| Version | Branch | Support |
| ------- | ---------- | ------------- |
| 4.x | main | Full |
| 3.x | 3.x-stable | Critical-only |
| 2.x | 2.x-stable | None |
| 1.x | 1.x-stable | None |
jQuery 4.0.0 has been released!
The 3.x branch will now only receive critical updates. The 2.x and 1.x branches are no longer supported. We recommend that all users upgrade to the latest version of jQuery to ensure that they have the best performance, security, and features.
Commercial support for previous versions is available from HeroDevs.
Learn more about our version support.
Contribution Guides
In the spirit of open source software development, jQuery always encourages community code contribution. To help you get started and before you jump into writing code, be sure to read these important contribution guidelines thoroughly:
1. Getting Involved
2. Core Style Guide
3. Writing Code for jQuery Projects
References to issues/PRs
GitHub issues/PRs are usually referenced via gh-NUMBER, where NUMBER is the numerical ID of the issue/PR. You can find such an issue/PR under https://github.com/jquery/jquery/issues/NUMBER.
jQuery has used a different bug tracker - based on Trac - in the past, available under bugs.jquery.com. It is being kept in read only mode so that referring to past discussions is possible. When jQuery source references one of those issues, it uses the pattern trac-NUMBER, where NUMBER is the numerical ID of the issue. You can find such an issue under https://bugs.jquery.com/ticket/NUMBER.
Environments in which to use jQuery
- Browser support
- jQuery also supports Node, browser extensions, and other non-browser environments.
What you need to build your own jQuery
To build jQuery, you need to have the latest Node.js/npm and git 1.7 or later. Earlier versions might work, but are not supported.
For Windows, you have to download and install git and Node.js.
macOS users should install Homebrew. Once Homebrew is installed, run brew install git to install git,
and brew install node to install Node.js.
Linux/BSD users should use their appropriate package managers to install git and Node.js, or build from source
if you swing that way. Easy-peasy.
How to build your own jQuery
First, clone the jQuery git repo.
Then, enter the jquery directory, install dependencies, and run the build script:
bash
cd jquery
npm install
npm run build
The built version of jQuery will be placed in the dist/ directory, along with a minified copy and associated map file.
Build all jQuery release files
To build all variants of jQuery, run the following command:
bash
npm run build:all
This will create all of the variants that jQuery includes in a release, including jquery.js, jquery.slim.js, jquery.module.js, and jquery.slim.module.js along their associated minified files and sourcemaps.
jquery.module.js and jquery.slim.module.js are ECMAScript modules that export jQuery and $ as named exports are placed in the dist-module/ directory rather than the dist/ directory.
Building a Custom jQuery
The build script can be used to create a custom version of jQuery that includes only the modules you need.
Any module may be excluded except for core. When excluding selector, it is not removed but replaced with a small wrapper around native querySelectorAll (see below for more information).
Build Script Help
To see the full list of available options for the build script, run the following:
bash
npm run build -- --help
Modules
To exclude a module, pass its path relative to the src folder (without the .js extension) to the --exclude option. When using the --include option, the default includes are dropped and a build is created with only those modules.
Some example modules that can be excluded or included are:
- ajax: All AJAX functionality:
$.ajax(),$.get(),$.post(),$.ajaxSetup(),.load(), transports, and ajax event shorthands such as.ajaxStart(). - ajax/xhr: The XMLHTTPRequest AJAX transport only.
- ajax/script: The `
AJAX transport only; used to retrieve scripts. - ajax/jsonp: The JSONP AJAX transport only; depends on the ajax/script transport.
- css: The .css()
method. Also removes all modules depending on css (including effects, dimensions, and offset). - css/showHide: Non-animated .show()
,.hide()and.toggle(); can be excluded if you use classes or explicit.css()calls to set thedisplayproperty. Also removes the effects module. - deprecated: Methods documented as deprecated but not yet removed.
- dimensions: The .width()
and.height()methods, includinginner-andouter-variations. - effects: The .animate()
method and its shorthands such as.slideUp()or.hide("slow"). - event: The .on()
and.off()methods and all event functionality. - event/trigger: The .trigger()
and.triggerHandler()methods. - offset: The .offset()
,.position(),.offsetParent(),.scrollLeft(), and.scrollTop()methods. - wrap: The .wrap()
,.wrapAll(),.wrapInner(), and.unwrap()methods. - core/ready: Exclude the ready module if you place your scripts at the end of the body. Any ready callbacks bound with jQuery()
will simply be called immediately. However,jQuery(document).ready()will not be a function and.on("ready", ...)or similar will not be triggered. - deferred: Exclude jQuery.Deferred. This also excludes all modules that rely on Deferred, including ajax, effects, and queue, but replaces core/ready with core/ready-no-deferred.
- exports/global: Exclude the attachment of global jQuery variables ($ and jQuery) to the window.
- exports/amd: Exclude the AMD definition.
- selector: The full jQuery selector engine. When this module is excluded, it is replaced with a rudimentary selector engine based on the browser's querySelectorAll
method that does not support jQuery selector extensions or enhanced semantics. See the selector-native.js file for details.
module will also exclude all jQuery selector extensions (such as effects/animatedSelector and css/hiddenVisibleSelectors).
AMD name
You can set the module name for jQuery's AMD definition. By default, it is set to "jquery", which plays nicely with plugins and third-party libraries, but there may be cases where you'd like to change this. Pass it to the
--amd parameter:
bash
npm run build -- --amd="custom-name"
Or, to define anonymously, leave the name blank.
bash
npm run build -- --amd
File name and directory
The default name for the built jQuery file is
jquery.js; it is placed under the dist/ directory. It's possible to change the file name using --filename and the directory using --dir. --dir is relative to the project root.
bash
npm run build -- --slim --filename="jquery.slim.js" --dir="/tmp"
This would create a slim version of jQuery and place it under
tmp/jquery.slim.js.
ECMAScript Module (ESM) mode
By default, jQuery generates a regular script JavaScript file. You can also generate an ECMAScript module exporting
jQuery as the default export using the --esm parameter:
bash
npm run build -- --filename=jquery.module.js --esm
Factory mode
By default, jQuery depends on a global
window. For environments that don't have one, you can generate a factory build that exposes a function accepting window as a parameter that you can provide externally (see [README of the published package](build/fixtures/README.md) for usage instructions). You can generate such a factory using the --factory parameter:
bash
npm run build -- --filename=jquery.factory.js --factory
This option can be mixed with others like
--esm or --slim:
bash
npm run build -- --filename=jquery.factory.slim.module.js --factory --esm --slim --dir="/dist-module"
Custom Build Examples
Create a custom build using
npm run build, listing the modules to be excluded. Excluding a top-level module also excludes its corresponding directory of modules.
Exclude all ajax functionality:
bash
npm run build -- --exclude=ajax
Excluding css removes modules depending on CSS: effects, offset, dimensions.
bash
npm run build -- --exclude=css
Exclude a bunch of modules (
-e is an alias for --exclude):
bash
npm run build -- -e ajax/jsonp -e css -e deprecated -e dimensions -e effects -e offset -e wrap
There is a special alias to generate a build with the same configuration as the official jQuery Slim build:
bash
npm run build -- --filename=jquery.slim.js --slim
Or, to create the slim build as an esm module:
bash
npm run build -- --filename=jquery.slim.module.js --slim --esm
*Non-official custom builds are not regularly tested. Use them at your own risk.*
Running the Unit Tests
Make sure you have the necessary dependencies:
bash
npm install
Start
npm start to auto-build jQuery as you work:
bash
npm start
Run the unit tests with a local server that supports PHP. Ensure that you run the site from the root directory, not the "test" directory. No database is required. Pre-configured php local servers are available for Windows and Mac. Here are some options:
- Windows: WAMP download
- Mac: MAMP download
- Linux: Setting up LAMP
- Mongoose (most platforms)
Essential Git
As the source code is handled by the Git version control system, it's useful to know some features used.
Cleaning
If you want to purge your working directory back to the status of upstream, the following commands can be used (remember everything you've worked on is gone after these):
bash
git reset --hard upstream/main
git clean -fdx
Rebasing
For feature/topic branches, you should always use the
--rebase flag to git pull, or if you are usually handling many temporary "to be in a github pull request" branches, run the following to automate this:
bash
git config branch.autosetuprebase local
(see
man git-config for more information)
Handling merge conflicts
If you're getting merge conflicts when merging, instead of editing the conflicted files manually, you can use the feature
git mergetool. Even though the default tool xxdiff looks awful/old, it's rather useful.
The following are some commands that can be used there:
Ctrl + Alt + M - automerge as much as possibleb - jump to next merge conflicts - change the order of the conflicted linesu - undo a mergeleft mouse button - mark a block to be the winnermiddle mouse button - mark a line to be the winnerCtrl + S - saveCtrl + Q - quit
QUnit Reference
Test methods
js
expect( numAssertions );
stop();
start();
*Note*: QUnit's eventual addition of an argument to stop/start is ignored in this test suite so that start and stop can be passed as callbacks without worrying about their parameters.
Test assertions
js
ok( value, [message] );
equal( actual, expected, [message] );
notEqual( actual, expected, [message] );
deepEqual( actual, expected, [message] );
notDeepEqual( actual, expected, [message] );
strictEqual( actual, expected, [message] );
notStrictEqual( actual, expected, [message] );
throws( block, [expected], [message] );
Test Suite Convenience Methods Reference
Returns an array of elements with the given IDs
js
q( ... );
Example:
js
q( "main", "foo", "bar" );
=> [ div#main, span#foo, input#bar ]
Asserts that a selection matches the given IDs
js
t( testName, selector, [ "array", "of", "ids" ] );
Example:
js
t("Check for something", "//[a]", ["foo", "bar"]);
Fires a native DOM event without going through jQuery
js
fireNative( node, eventType );
Example:
js
fireNative( jQuery( "#elem" )[ 0 ], "click" );
Add random number to url to stop caching
js
url( "some/url" );
Example:
js
url( "index.html" );
=> "data/index.html?10538358428943"
url( "mock.php?foo=bar" );
=> "data/mock.php?foo=bar&10538358345554"
Run tests in an iframe
Some tests may require a document other than the standard test fixture, and
these can be run in a separate iframe. The actual test code and assertions
remain in jQuery's main test files; only the minimal test fixture markup
and setup code should be placed in the iframe file.
js
testIframe( testName, fileName,
function testCallback(
assert, jQuery, window, document,
[ additional args ] ) {
...
} );
This loads a page, constructing a url with fileName
"./data/" + fileName.
The iframed page determines when the callback occurs in the test by
including the "/test/data/iframeTest.js" script and calling
startIframeTest( [ additional args ] ) when appropriate. Often this
will be after either document ready or window.onload fires.
The
testCallback receives the QUnit assert object created by testIframe
for this test, followed by the global jQuery, window, and document from
the iframe. If the iframe code passes any arguments to startIframeTest,
they follow the document` argument.
Questions?
If you have any questions, please feel free to ask on the
Developing jQuery Core forum or in #jquery on libera.
-
jquery
jQuery JavaScript Library
JavaScript ★ 60k 1d agoExplain → -
jquery-ui
The official jQuery user interface library.
JavaScript ★ 11k 1d agoExplain → -
esprima
ECMAScript parsing infrastructure for multipurpose analysis
TypeScript ★ 7.1k 3y agoExplain → -
sizzle
A sizzlin' hot selector engine.
JavaScript ★ 6.3k 5mo agoExplain → -
jquery-mousewheel
A jQuery plugin that adds cross-browser mouse wheel support.
JavaScript ★ 3.9k 18d agoExplain → -
jquery-migrate
A development tool to help migrate away from APIs and features that have been or will be removed from jQuery core
JavaScript ★ 2.1k 22h agoExplain → -
jquery-color
jQuery plugin for color manipulation and animation support.
JavaScript ★ 1.6k 18d agoExplain → -
learn.jquery.com
jQuery Learning Center web site content
JavaScript ★ 917 1y agoExplain → -
api.jquery.com
API documentation for jQuery Core
HTML ★ 325 18d agoExplain → -
jquery-wp-content
WordPress themes and plugins for the jQuery sites
PHP ★ 260 3d agoExplain → -
jquery-simulate
jQuery Event Unit Testing Helpers
JavaScript ★ 171 24d agoExplain → -
themeroller.jquerymobile.com
ThemeRoller site for jQuery Mobile
CSS ★ 140 5mo agoExplain → -
jqueryui.com
jQuery UI web site content
HTML ★ 138 19d agoExplain → -
jquery-dist
Distribution repo for jQuery Core releases
JavaScript ★ 99 5mo agoExplain → -
download.jqueryui.com
Download Builder for jQuery UI
JavaScript ★ 89 29d agoExplain → -
jquery.com
jQuery web site content
HTML ★ 79 10d agoExplain → -
typesense-minibar
Fast 2kB autocomplete search bar. Alternative to Algolia DocSearch, InstantSearch, and autocomplete-js.
JavaScript ★ 75 1y agoExplain → -
api.jqueryui.com
API documentation for jQuery UI
HTML ★ 73 5mo agoExplain → -
codeorigin.jquery.com
jQuery CDN
JavaScript ★ 64 20d agoExplain → -
jquerymobile.com
jQuery Mobile web site content
HTML ★ 57 11d agoExplain → -
api.jquerymobile.com
API documentation for jQuery Mobile
HTML ★ 55 1y agoExplain → -
jquery.org
jQuery Foundation web site content
JavaScript ★ 51 2mo agoExplain → -
grunt-jquery-content
No description.
XSLT ★ 41 11d agoExplain → -
gsoc
Home for the jQuery Foundations ideas list for Google Summer of Code 2015
★ 41 5y agoExplain → -
eslint-config-jquery
jQuery's eslint config, enforcing the jQuery styleguide
JavaScript ★ 35 2y agoExplain → -
meetings.jquery.org
Calendar and minutes of public jQuery team meetings
JavaScript ★ 30 5d agoExplain → -
jquery-release
Release automation script for jQuery projects
JavaScript ★ 28 1mo agoExplain → -
contribute.jquery.org
Developer documentation common to jQuery projects
HTML ★ 28 11mo agoExplain → -
testswarm-browserstack
Integration layer between TestSwarm and BrowserStack
JavaScript ★ 27 3y agoExplain → -
demos.jquerymobile.com
jQuery Mobile demo site
HTML ★ 22 2y agoExplain → -
2012-dev-summit
Information regarding the 2012 Developer Summit in DC
★ 15 5y agoExplain → -
jquery-license ▣
jQuery Foundation License Verification
JavaScript ★ 13 5y agoExplain → -
infrastructure-puppet
Puppet configuration for jQuery Infrastructure servers.
HTML ★ 12 1d agoExplain → -
2015-developer-summit
a sandbox site for making mistakes
HTML ★ 12 7y agoExplain → -
brand.jquery.org
Information on jQuery's branding
HTML ★ 10 10d agoExplain → -
irc.jquery.org
jQuery Foundation IRC channels and logs site content
HTML ★ 10 2y agoExplain → -
events.jquery.org ▣
jQuery Events & Conferences web site content
HTML ★ 9 3y agoExplain → -
jquery.github.io ▣
No description.
HTML ★ 8 3y agoExplain → -
node-amd-builder
jQuery Mobile download builder, a Node.js service
JavaScript ★ 8 5mo agoExplain → -
healthyweb.org
Check any website for the latest version of jQuery
Svelte ★ 7 3mo agoExplain → -
alpha-omega ⑂
Protect society by improving the security of open source software through direct maintainer engagement and expert analysis.
Open Policy Agent ★ 6 1y agoExplain → -
jquery-compat-dist
Distribution repo for jQuery Core Compat releases
JavaScript ★ 6 5y agoExplain → -
ci-management
No description.
Shell ★ 6 3y agoExplain → -
podcast.jquery.com
No description.
HTML ★ 5 12d agoExplain → -
blog.jquery.com-theme ▣
Themes for blogs during transition period to https://github.com/jquery/jquery-wp-content
CSS ★ 4 5mo agoExplain → -
jquery-test-runner
A test runner built by the jQuery team to run QUnit tests in real browsers using Selenium and BrowserStack.
JavaScript ★ 4 18d agoExplain → -
content
Content Team
★ 4 5y agoExplain → -
hydra-link-checker ⑂
🐍 Hydra: a multithreaded site-crawling link checker in Python standard library
Python ★ 4 3y agoExplain → -
node-notifier-server ⑂
Lightweight, minimal, and secure GitHub webhook server with support for shell scripts.
JavaScript ★ 3 10d agoExplain → -
node-packager
Build a package for your library or application on the fly on Node.js
JavaScript ★ 3 2y agoExplain → -
jquery-wp-docker
Dockerized containers for running jquery-wp-content
PHP ★ 2 1y agoExplain → -
docs.jquery.com ▣
[Obsolete] MediaWiki configuration of docs.jquery.com. Replaced by https://api.jquery.com, https://learn.jquery.com and https://plugins.jquery.com. –
PHP ★ 2 13y agoExplain → -
healthyweb-worker
The browser rendering worker for healthyweb.org
TypeScript ★ 1 3mo agoExplain → -
plugins.jquery.com-static
Static archive of the old plugins.jquery.com site.
HTML ★ 1 24d agoExplain → -
bugs.jquery.com
Static archive of the bugs.jquery.com Trac site.
JavaScript ★ 1 20d agoExplain → -
bugs.jqueryui.com
Static archive of the old bugs.jqueryui.com Trac site.
JavaScript ★ 1 24d agoExplain → -
builder-amd
Generate the JS bundle of an AMD modular project on the fly on Node.js
JavaScript ★ 1 5mo agoExplain → -
.github
Default community health files for jQuery
★ 1 9mo agoExplain → -
node-web-git-proxy ⑂ ▣
Collection of node tools for creating an updating git proxy like https://view.jquery.com
JavaScript ★ 1 5y agoExplain → -
gilded-wordpress ⑂
Easily synchronize content between the file system and WordPress
JavaScript ★ 1 2y agoExplain → -
jquery-ui-box ⑂
jQuery Box Plugin
★ 0 14y agoExplain → -
infrastructure-issues
Parking space in-between old "infrastructure" repo (private) and new "infrastructure-puppet" repo (public)
★ 0 2y agoExplain → -
builder-jquery-css
Generate the CSS bundle of a jQuery project (JS comments to define CSS deps + AMD to define JS deps) on the fly on Node.js
JavaScript ★ 0 5mo agoExplain → -
builder-amd-css
Generate the CSS bundle of an AMD modular project on the fly on Node.js
JavaScript ★ 0 5mo agoExplain → -
requirejs-memfiles
requirejs with an additional static method `requirejs.setFiles()` that allows for passing in-memory files.
JavaScript ★ 0 5mo agoExplain →
No repos match these filters.