Meetings are currently held on the [matrix.org platform](https://matrix.to/#/#jquery_meeting:gitter.im).

Meeting minutes can be found at [meetings.jquery.org](https://meetings.jquery.org/category/core/).

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:

jQuery has used a different bug tracker - based on Trac - in the past, available under [bugs.jquery.com](https://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`.

- [Browser support](https://jquery.com/browser-support/)

- jQuery also supports Node, browser extensions, and other non-browser environments.

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.

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.

First, [clone the jQuery git repo](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository).

- **ajax/script**: The `<script>` 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**).

- **deprecated**: Methods documented as deprecated but not yet removed.

- **dimensions**: The `.width()` and `.height()` methods, including `inner-` and `outer-` variations.

- **effects**: The `.animate()` method and its shorthands such as `.slideUp()` or `.hide("slow")`.

*Non-official custom builds are not regularly tested. Use them at your own risk.*

Make sure you have the necessary dependencies:

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](https://www.wampserver.com/en/)

- Mac: [MAMP download](https://www.mamp.info/en/downloads/)

- Linux: [Setting up LAMP](https://www.linux.com/training-tutorials/easy-lamp-server-installation/)

- [Mongoose (most platforms)](https://code.google.com/p/mongoose/)

As the source code is handled by the Git version control system, it's useful to know some features used.

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):

git clean -fdx

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:

git config branch.autosetuprebase local

(see `man git-config` for more information)

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:

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.

ok( value, [message] );

throws( block, [expected], [message] );

q( ... );

Example:

=> [ div#main, span#foo, input#bar ]

t( testName, selector, [ "array", "of", "ids" ] );

t("Check for something", "//[a]", ["foo", "bar"]);

Example:

url( "some/url" );

Example:

=> "data/index.html?10538358428943"

=> "data/mock.php?foo=bar&10538358345554"

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

the iframe. If the iframe code passes any arguments to `startIframeTest`,

they follow the `document` argument.

If you have any questions, please feel free to ask on the

[Developing jQuery Core forum](https://forum.jquery.com/developing-jquery-core) or in #jquery on [libera](https://web.libera.chat/).