| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Node.js 0.12 is no longer supported by upstream. So far we had to keep
a workaround that would skip running ESLint there (or even load its task)
as it no longer supports Node.js <4; the same applied to Node smoke tests
as jsdom has also dropped support for those old Node versions. Those
workarounds have been removed now.
Ref 030191ae32dfcb7ecb2efb61d17a4964a3633e44
Closes gh-3478
|
|
|
|
|
|
|
| |
1. Use the short name of the preset in the config.
2. Run ESLint first on non-minified files.
3. Explicitly specify environments in every config file (those settings cascade
which means we've been assuming a Node.js environment where we shouldn't have).
|
|
|
|
| |
Close gh-3414
|
|
|
|
|
| |
Node.js 0.10 loses upstream support today (see https://github.com/nodejs/LTS/)
so let's stop testing against it as well.
|
|
|
|
| |
Fixes gh-3246
|
|
|
|
|
| |
Currently the "all" target for the eslint task includes way more than
the "dev" & "dist" targets combined and those 2 tasks are the one run in
`npm test`.
|
|
|
|
|
|
|
|
|
| |
ESLint 3.0 drops support for Node.js older than 4.x. To be able to update
to this version and yet not block our contributors from building jQuery
on older Node.js (at least until it's supported by upstream) this commit
makes ESLint skipped on older Node; a proper message is displayed then.
Fixes gh-3222
|
|
|
|
|
|
|
|
|
| |
* Bump eslint-config-jquery package to 0.1.4 version
* Add subtask "dist" to "eslint" task and add it to the build task list
* Make gitignore globs more flexible for the "dist" folder
Fixes gh-3169
|
|
|
|
|
|
| |
Use eslint pragmas, fix new errors, etc
Closes gh-3148
|
| |
|
|
|
|
|
|
|
|
|
| |
The husky Git precommit hook was linting not only the source but also the
built file. Normally it's expected, we want to run basic checks on what's
built but in the precommit hook we're not building the file so we might
be linting some previous, broken version.
Fixes gh-3091
|
|
|
|
| |
This reverts commit fa610da68440530e73bba296a1f982f94dfeac99.
|
|
|
|
|
|
|
|
|
| |
This commit increases the gzipped size by 90 bytes so a better solution
is needed but, at the same time, it disables the very optimizations
that are causing strict mode violations in Firefox 45, Safari 9 & IE 10.
Refs 76084372c29a59b3fa790ea4d2687f0767514999
Refs mishoo/UglifyJS2#1052
|
|
|
|
|
|
|
|
|
| |
- Make jQuery.ready promise-compatible
- Gives up sync guarantee for post-ready callbacks
Fixes gh-1778
Fixes gh-1823
Close gh-2891
|
|
|
|
| |
Fixes gh-2841
|
| |
|
| |
|
|
|
|
|
| |
Fixes gh-2577
Closes gh-2881
|
|
|
|
|
|
|
|
|
|
|
|
| |
All deps were updated except:
* jsdom - tests using a Symbol polyfill are hacky and break with newer jsdom;
we need to re-do them properly first
* qunitjs - versions 1.19.0 & 1.20.0 introduce race conditions to the tests,
making the fail randomly
Those two packages will be updated once issues related to them get resolved.
Fixes gh-2877
|
| |
|
| |
|
|
|
|
|
| |
Fixes gh-2653
Close gh-2711
|
|
|
|
|
|
| |
Ref #1740
Yeah.
|
|
|
|
|
|
|
|
| |
Unit test changes some uses of .show() and .hide() to .css( "display", ... ),
there was already an implicit assumption in several of the existing tests.
Fixes gh-2193
Close gh-2648
|
|
|
|
|
|
| |
Fixes gh-2505
Closes gh-2509
Refs gh-2483
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
jsdom 3 requires Python & Visual Studio on Windows which is a significant
barrier to contributors. Newer jsdom versions don't require pre-compiling
but work only on io.js. This commit installs the new jsdom everywhere (it
does install in old Node.js, it just won't work) and executes Node-related
tests only on newer Nodes or if a working jsdom version is installed. The
latter can be achieved by running the `old_jsdom` task.
Node.js is merging with io.js soon so this will become a smaller problem over
time.
One drawback is our Jenkins setup runs on Node 0.10 so it won't be running
Node tests anymore. We have Travis set up on io.js, though so all PRs
have those tests run. When the new LTS Node.js arrives (as it soon merges
with io.js) we should update our Jenkins infrastructure so that it runs on this
new version.
Fixes gh-2519
Closes gh-2526
|
|
|
|
|
| |
Fixes gh-2283
Closes gh-2292
|
|
|
|
|
|
| |
Also fix lint error in `data` module.
It seems this command was removed from the list during merge
|
| |
|
|
|
|
| |
Fixes gh-2056
|
|
|
|
|
|
|
|
|
|
| |
It might not be obvious to everyone that IE 9 & Android 4.0 are not
ES5-compliant browsers (by a large margin) so it's better to add a support
comment. This requires slight changes in parsing the config file
as it's not a pure JSON anymore. JSHint understands such files without
problems.
Closes gh-2520
|
|
|
|
| |
Closes gh-2326
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Make iterating over jQuery objects possible using ES 2015 for-of:
for ( node of $( "<div id=narwhal>" ) ) {
console.log( node.id ); // "narwhal"
}
Fixes gh-1693
|
|
|
|
| |
Ref 26eca143c2dd857b9e3d1c446a467fed16e903d2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is a lot of logic in intro.js; now we test four cases:
1. (implicitly, via QUnit tests) A real browser with window being the global
2. Browserify where there are both global & window variables.
3. Node with jsdom where window is passed manually to the jQuery factory.
4. Pure Node with incorrect window passed; jQuery should throw then.
Previously the second & fourth case was not tested and the third was tested
in a way that interfered with the main test environment.
We now also test if in the Browserify case we're not creating a jQuery global
by default.
Fixes gh-2181
Closes gh-2234
|
|
|
|
|
| |
Fixes gh-1722
Closes gh-1996
|
|
|
|
| |
Fixes gh-1707
|
|
|
|
|
| |
Ref 76df9e4e389d80bff410a9e5f08b848de1d21a2f
Closes gh-1980
|
|
|
|
| |
Closes gh-1983
|
|
|
|
|
| |
Fixes gh-1950
Closes gh-1949
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fixes #15186
Closes gh-1620
|
| |
|
| |
|
|
|
|
| |
Closes gh-1593
|
| |
|
|
|
|
| |
Fixes #15126
|