代码:

1. 
   
2. 
   
3. [jQuery](http://jquery.com/) - New Wave JavaScript
   
4. ==================================================
   
5. 
   
6. Contribution Guides
   
7. --------------------------------------
   
8. 
   
9. 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:
   
10. 
    
11. 1. [Getting Involved](http://docs.jquery.com/Getting_Involved)
    
12. 2. [Core Style Guide](http://docs.jquery.com/JQuery_Core_Style_Guidelines)
    
13. 3. [Tips For Bug Patching](http://docs.jquery.com/Tips_for_jQuery_Bug_Patching)
    
14. 
    
15. 
    
16. What you need to build your own jQuery
    
17. --------------------------------------
    
18. 
    
19. In order to build jQuery, you need to have Node.js/npm latest and git 1.7 or later.
    
20. (Earlier versions might work OK, but are not tested.)
    
21. 
    
22. For Windows you have to download and install [git](http://git-scm.com/downloads) and [Node.js](http://nodejs.org/download/).
    
23. 
    
24. Mac OS users should install [Homebrew](http://mxcl.github.com/homebrew/). Once Homebrew is installed, run `brew install git` to install git,
    
25. and `brew install node` to install Node.js.
    
26. 
    
27. Linux/BSD users should use their appropriate package managers to install git and Node.js, or build from source
    
28. if you swing that way. Easy-peasy.
    
29. 
    
30. 
    
31. How to build your own jQuery
    
32. ----------------------------
    
33. 
    
34. Clone a copy of the main jQuery git repo by running:
    
35. 
    
36. ```bash
    
37. git clone git://github.com/jquery/jquery.git
    
38. ```
    
39. 
    
40. Enter the jquery directory and run the build script:
    
41. ```bash
    
42. cd jquery && npm run-script build
    
43. ```
    
44. The built version of jQuery will be put in the `dist/` subdirectory, along with the minified copy and associated map file.
    
45. 
    
46. If you want create custom build or help with jQuery development, it would be better to install <a href="https://github.com/gruntjs/grunt-cli">grunt command line interface</a> as a global package:
    
47. 
    
48. ```
    
49. npm install -g grunt-cli
    
50. ```
    
51. Make sure you have `grunt` installed by testing:
    
52. ```
    
53. grunt -v
    
54. ```
    
55. 
    
56. Now by running `grunt` command, in the jquery directory, you could build full version of jQuery, just like with `npm run-script build` command:
    
57. ```
    
58. grunt
    
59. ```
    
60. 
    
61. There are many other tasks avaliable for jQuery Core:
    
62. ```
    
63. grunt -help
    
64. ```
    
65. 
    
66. ### Modules
    
67. 
    
68. Special builds can be created that exclude subsets of jQuery functionality.
    
69. This allows for smaller custom builds when the builder is certain that those parts of jQuery are not being used.
    
70. For example, an app that only used JSONP for `$.ajax()` and did not need to calculate offsets or positions of elements could exclude the offset and ajax/xhr modules.
    
71. 
    
72. Any module may be excluded except for `core`, and `selector`. To exclude a module, pass its path relative to the `src` folder (without the `.js` extension).
    
73. 
    
74. Some example modules that can be excluded are:
    
75. 
    
76. - **ajax**: All AJAX functionality: `$.ajax()`, `$.get()`, `$.post()`, `$.ajaxSetup()`, `.load()`, transports, and ajax event shorthands such as `.ajaxStart()`.
    
77. - **ajax/xhr**: The XMLHTTPRequest AJAX transport only.
    
78. - **ajax/script**: The `<script>` AJAX transport only; used to retrieve scripts.
    
79. - **ajax/jsonp**: The JSONP AJAX transport only; depends on the ajax/script transport.
    
80. - **css**: The `.css()` method plus non-animated `.show()`, `.hide()` and `.toggle()`. Also removes **all** modules depending on css (including **effects**, **dimensions**, and **offset**).
    
81. - **deprecated**: Methods documented as deprecated but not yet removed; currently only `.andSelf()`.
    
82. - **dimensions**: The `.width()` and `.height()` methods, including `inner-` and `outer-` variations.
    
83. - **effects**: The `.animate()` method and its shorthands such as `.slideUp()` or `.hide("slow")`.
    
84. - **event**: The `.on()` and `.off()` methods and all event functionality. Also removes `event/alias`.
    
85. - **event/alias**: All event attaching/triggering shorthands like `.click()` or `.mouseover()`.
    
86. - **offset**: The `.offset()`, `.position()`, `.offsetParent()`, `.scrollLeft()`, and `.scrollTop()` methods.
    
87. - **wrap**: The `.wrap()`, `.wrapAll()`, `.wrapInner()`, and `.unwrap()` methods.
    
88. - **exports/amd**: Exclude the AMD definition.
    
89. - **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.
    
90. - **deferred**: Exclude jQuery.Deferred. This also removes jQuery.Callbacks. *Note* that modules that depend on jQuery.Deferred(AJAX, effects, core/ready) will not be removed and will still expect jQuery.Deferred to be there. Include your own jQuery.Deferred implementation or exclude those modules as well (`grunt custom:-deferred,-ajax,-effects,-core/ready`).
    
91. 
    
92. As a special case, you may also replace Sizzle by using a special flag `grunt custom:-sizzle`.
    
93. 
    
94. - **sizzle**: The Sizzle selector engine. When this module is excluded, it is replaced by 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.
    
95. 
    
96. *Note*: Excluding Sizzle will also exclude all jQuery selector extensions (such as `effects/animatedSelector` and `css/hiddenVisibleSelectors`).
    
97. 
    
98. The build process shows a message for each dependent module it excludes or includes.
    
99. 
    
100. To create a custom build of the latest stable version, first check out the version:
     
101. 
     
102. ```bash
     
103. git pull; git checkout $(git describe --abbrev=0 --tags)
     
104. ```
     
105. 
     
106. Then, make sure all Node dependencies are installed:
     
107. 
     
108. ```bash
     
109. npm install
     
110. ```
     
111. 
     
112. Create the custom build, use the `grunt custom` option, listing the modules to be excluded. Examples:
     
113. 
     
114. Exclude all **ajax** functionality:
     
115. 
     
116. ```bash
     
117. grunt custom:-ajax
     
118. ```
     
119. 
     
120. Excluding **css** removes modules depending on CSS: **effects**, **offset**, **dimensions**.
     
121. 
     
122. ```bash
     
123. grunt custom:-css
     
124. ```
     
125. 
     
126. Exclude a bunch of modules:
     
127. 
     
128. ```bash
     
129. grunt custom:-ajax,-css,-deprecated,-dimensions,-effects,-event/alias,-offset,-wrap
     
130. ```
     
131. 
     
132. For questions or requests regarding custom builds, please start a thread on the [Developing jQuery Core](https://forum.jquery.com/developing-jquery-core) section of the forum. Due to the combinatorics and custom nature of these builds, they are not regularly tested in jQuery's unit test process. The non-Sizzle selector engine currently does not pass unit tests because it is missing too much essential functionality.
     
133. 
     
134. Running the Unit Tests
     
135. --------------------------------------
     
136. 
     
137. Make sure you have the necessary dependencies:
     
138. 
     
139. ```bash
     
140. npm install
     
141. ```
     
142. 
     
143. Start `grunt watch` or `npm start` to auto-build jQuery as you work:
     
144. 
     
145. ```bash
     
146. cd jquery && grunt watch
     
147. ```
     
148. 
     
149. 
     
150. 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:
     
151. 
     
152. - Windows: [WAMP download](http://www.wampserver.com/en/)
     
153. - Mac: [MAMP download](http://www.mamp.info/en/index.html)
     
154. - Linux: [Setting up LAMP](https://www.linux.com/learn/tutorials/288158-easy-lamp-server-installation)
     
155. - [Mongoose (most platforms)](http://code.google.com/p/mongoose/)
     
156. 
     
157. 
     
158. 
     
159. 
     
160. Building to a different directory
     
161. ---------------------------------
     
162. 
     
163. To copy the built jQuery files from `/dist` to another directory:
     
164. 
     
165. ```bash
     
166. grunt && grunt dist:/path/to/special/location/
     
167. ```
     
168. With this example, the output files would be:
     
169. 
     
170. ```bash
     
171. /path/to/special/location/jquery.js
     
172. /path/to/special/location/jquery.min.js
     
173. ```
     
174. 
     
175. To add a permanent copy destination, create a file in `dist/` called ".destination.json". Inside the file, paste and customize the following:
     
176. 
     
177. ```json
     
178. 
     
179. {
     
180. "/Absolute/path/to/other/destination": true
     
181. }
     
182. ```
     
183. 
     
184. Additionally, both methods can be combined.
     
185. 
     
186. 
     
187. 
     
188. Essential Git
     
189. -------------
     
190. 
     
191. As the source code is handled by the version control system Git, it's useful to know some features used.
     
192. 
     
193. ### cleaning ###
     
194. 
     
195. If you want to purge your working directory back to the status of upstream, following commands can be used (remember everything you've worked on is gone after these):
     
196. 
     
197. ```bash
     
198. git reset --hard upstream/master
     
199. git clean -fdx
     
200. ```
     
201. 
     
202. ### rebasing ###
     
203. 
     
204. 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 following to automate this:
     
205. 
     
206. ```bash
     
207. git config branch.autosetuprebase local
     
208. ```
     
209. (see `man git-config` for more information)
     
210. 
     
211. ### handling merge conflicts ###
     
212. 
     
213. If you're getting merge conflicts when merging, instead of editing the conflicted files manually, you can use the feature
     
214. `git mergetool`. Even though the default tool `xxdiff` looks awful/old, it's rather useful.
     
215. 
     
216. Following are some commands that can be used there:
     
217. 
     
218. * `Ctrl + Alt + M` - automerge as much as possible
     
219. * `b` - jump to next merge conflict
     
220. * `s` - change the order of the conflicted lines
     
221. * `u` - undo a merge
     
222. * `left mouse button` - mark a block to be the winner
     
223. * `middle mouse button` - mark a line to be the winner
     
224. * `Ctrl + S` - save
     
225. * `Ctrl + Q` - quit
     
226. 
     
227. [QUnit](http://docs.jquery.com/QUnit) Reference
     
228. -----------------
     
229. 
     
230. ### Test methods ###
     
231. 
     
232. ```js
     
233. expect( numAssertions );
     
234. stop();
     
235. start();
     
236. ```
     
237. 
     
238. 
     
239. 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
     
240. 
     
241. ### Test assertions ###
     
242. 
     
243. 
     
244. ```js
     
245. ok( value, [message] );
     
246. equal( actual, expected, [message] );
     
247. notEqual( actual, expected, [message] );
     
248. deepEqual( actual, expected, [message] );
     
249. notDeepEqual( actual, expected, [message] );
     
250. strictEqual( actual, expected, [message] );
     
251. notStrictEqual( actual, expected, [message] );
     
252. raises( block, [expected], [message] );
     
253. ```
     
254. 
     
255. 
     
256. Test Suite Convenience Methods Reference (See [test/data/testinit.js](https://github.com/jquery/jquery/blob/master/test/data/testinit.js))
     
257. ------------------------------
     
258. 
     
259. ### Returns an array of elements with the given IDs ###
     
260. 
     
261. ```js
     
262. q( ... );
     
263. ```
     
264. 
     
265. Example:
     
266. 
     
267. ```js
     
268. q("main", "foo", "bar");
     
269. 
     
270. => [ div#main, span#foo, input#bar ]
     
271. ```
     
272. 
     
273. ### Asserts that a selection matches the given IDs ###
     
274. 
     
275. ```js
     
276. t( testName, selector, [ "array", "of", "ids" ] );
     
277. ```
     
278. 
     
279. Example:
     
280. 
     
281. ```js
     
282. t("Check for something", "//[a]", ["foo", "baar"]);
     
283. ```
     
284. 
     
285. 
     
286. 
     
287. ### Fires a native DOM event without going through jQuery ###
     
288. 
     
289. ```js
     
290. fireNative( node, eventType )
     
291. ```
     
292. 
     
293. Example:
     
294. 
     
295. ```js
     
296. fireNative( jQuery("#elem")[0], "click" );
     
297. ```
     
298. 
     
299. ### Add random number to url to stop caching ###
     
300. 
     
301. ```js
     
302. url( "some/url.php" );
     
303. ```
     
304. 
     
305. Example:
     
306. 
     
307. ```js
     
308. url("data/test.html");
     
309. 
     
310. => "data/test.html?10538358428943"
     
311. 
     
312. 
     
313. url("data/test.php?foo=bar");
     
314. 
     
315. => "data/test.php?foo=bar&10538358345554"
     
316. ```
     
317. 
     
318. 
     
319. ### Load tests in an iframe ###
     
320. 
     
321. Loads a given page constructing a url with fileName: `"./data/" + fileName + ".html"`
     
322. and fires the given callback on jQuery ready (using the jQuery loading from that page)
     
323. and passes the iFrame's jQuery to the callback.
     
324. 
     
325. ```js
     
326. testIframe( fileName, testName, callback );
     
327. ```
     
328. 
     
329. Callback arguments:
     
330. 
     
331. ```js
     
332. callback( jQueryFromIFrame, iFrameWindow, iFrameDocument );
     
333. ```
     
334. 
     
335. ### Load tests in an iframe (window.iframeCallback) ###
     
336. 
     
337. Loads a given page constructing a url with fileName: `"./data/" + fileName + ".html"`
     
338. The given callback is fired when window.iframeCallback is called by the page
     
339. The arguments passed to the callback are the same as the
     
340. arguments passed to window.iframeCallback, whatever that may be
     
341. 
     
342. ```js
     
343. testIframeWithCallback( testName, fileName, callback );
     
344. ```
     
345. 
     
346. Questions?
     
347. ----------
     
348. 
     
349. If you have any questions, please feel free to ask on the
     
350. [Developing jQuery Core forum](http://forum.jquery.com/developing-jquery-core) or in #jquery on irc.freenode.net.
     
351. 
     
352.