library-mirrors/jquery
1
0
Fork 0
mirror of https://github.com/jquery/jquery.git synced 2024-10-05 11:34:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
1ad66aeb6d
jquery/package.json

163 lines
5.6 KiB
JSON
Raw Normal View History

Initial grunt implementation
2012-04-18 20:07:35 +00:00
{
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
"name": "jquery",
"title": "jQuery",
"description": "JavaScript library for DOM operations",
Build: Update the master version to 4.0.0-pre
2019-04-08 16:21:36 +00:00
"version": "4.0.0-pre",
Build: Add `exports` to package.json, export slim & esm builds Summary of the changes: * define the `exports` field in `package.json`; `jQuery` & `$` are also exported as named exports in ESM builds now * declare `"type": "module"` globally except for the `build` folder * add the `--esm` option to `grunt custom`, generating jQuery as an ECMAScript module into the `dist-module` folder * expand `node_smoke_tests` to test the slim & ESM builds and their various combinations; also, test both jQuery loaded via a path to the file as well as from module specifiers that should be parsed via the `exports` feature * add details about ESM usage to the release package README * run `compare_size` on all built minified files; don't run it anymore on unminified files where they don't provide lots of value * remove the remove_map_comment task; SWC doesn't insert the `//# sourceMappingURL=` pragma by default so there's nothing to strip Fixes gh-4592 Closes gh-5255
2023-07-10 17:14:08 +00:00
"type": "module",
"exports": {
".": {
"node": {
"module": "./dist-module/jquery.module.js",
"import": "./dist-module/jquery.node-module-wrapper.js",
"require": "./dist/jquery.js"
},
"production": "./dist-module/jquery.module.min.js",
"development": "./dist-module/jquery.module.js",
"script": "./dist/jquery.min.js",
"default": "./dist-module/jquery.module.min.js"
},
"./slim": {
"node": {
"module": "./dist-module/jquery.slim.module.js",
"import": "./dist-module/jquery.node-module-wrapper.slim.js",
"require": "./dist/jquery.slim.js"
},
"production": "./dist-module/jquery.slim.module.min.js",
"development": "./dist-module/jquery.slim.module.js",
"script": "./dist/jquery.slim.min.js",
"default": "./dist-module/jquery.slim.module.min.js"
},
Core: Move the factory to separate exports Since versions 1.11.0/2.1.0, jQuery has used a module wrapper with one strange addition - in CommonJS environments, if a global `window` with a `document` was not present, jQuery exported a factory accepting a `window` implementation and returning jQuery. This approach created a number of problems: 1. Properly typing jQuery would be a nightmare as the exported value depends on the environment. In practice, typing definitions ignored the factory case. 2. Since we now use named exports for the jQuery module version, it felt weird to have `jQuery` and `$` pointing to the factory instead of real jQuery. Instead, for jQuery 4.0 we leverage the just added `exports` field in `package.json` to expose completely separate factory entry points: one for the full build, one for the slim one. Exports definitions for `./factory` & `./factory-slim` are simpler than for `.` and `./slim` - this is because it's a new entry point, we only expose a named export and so there's no issue with just pointing Node.js to the CommonJS version (we cannot use the module version for `import` from Node.js to avoid double package hazard). The factory entry points are also not meant for the Web browser which always has a proper `window` - and they'd be unfit for an inclusion in a regular script tag anyway. Because of that, we also don't generate minified versions of these entry points. The factory files are not pushed to the CDN since they are mostly aimed at Node.js. Closes gh-5293
2023-09-19 16:58:24 +00:00
"./factory": {
"node": "./dist/jquery.factory.js",
"default": "./dist-module/jquery.factory.module.js"
},
"./factory-slim": {
"node": "./dist/jquery.factory.slim.js",
"default": "./dist-module/jquery.factory.slim.module.js"
},
Build: Add `exports` to package.json, export slim & esm builds Summary of the changes: * define the `exports` field in `package.json`; `jQuery` & `$` are also exported as named exports in ESM builds now * declare `"type": "module"` globally except for the `build` folder * add the `--esm` option to `grunt custom`, generating jQuery as an ECMAScript module into the `dist-module` folder * expand `node_smoke_tests` to test the slim & ESM builds and their various combinations; also, test both jQuery loaded via a path to the file as well as from module specifiers that should be parsed via the `exports` feature * add details about ESM usage to the release package README * run `compare_size` on all built minified files; don't run it anymore on unminified files where they don't provide lots of value * remove the remove_map_comment task; SWC doesn't insert the `//# sourceMappingURL=` pragma by default so there's nothing to strip Fixes gh-4592 Closes gh-5255
2023-07-10 17:14:08 +00:00
"./src/*.js": "./src/*.js"
},
Fixes #14548. Add main property to package.json
2013-11-15 22:07:12 +00:00
"main": "dist/jquery.js",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"scripts": {
"babel:tests": "babel test/data/core/jquery-iterability-transpiled-es6.js --out-file test/data/core/jquery-iterability-transpiled.js",
"build": "node ./build/command.js",
"build:all": "node -e \"require('./build/tasks/build.js').buildDefaultFiles()\"",
"build:main": "node -e \"require('./build/tasks/build.js').build()\"",
Build: run pretest in jenkins script
2023-09-20 22:07:35 +00:00
"jenkins": "npm run pretest && npm run test:browserless",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"lint:dev": "eslint --cache .",
"lint:json": "jsonlint --quiet package.json",
"lint": "concurrently -r \"npm:lint:dev\" \"npm:lint:json\"",
"npmcopy": "node build/tasks/npmcopy.js",
"prepare": "husky install",
"pretest": "npm run qunit-fixture && npm run babel:tests && npm run npmcopy",
"qunit-fixture": "node build/tasks/qunit-fixture.js",
"start": "node -e \"require('./build/tasks/build.js').buildDefaultFiles({ watch: true })\"",
Build: Run pretest before test:* npm scripts Build was already happening in scripts like `test:browser` but those scripts were missing `pretest`, meaning that running `npm install && npm test:browser` may have failed if `pretest` wasn't run before or if its results were out of date. Even worse, with such stale data some tests may erroneously succeed. This also removes a separate `pretest` step from GitHub Actions as it's no longer needed. Closes gh-5338
2023-10-16 16:54:54 +00:00
"test:browserless": "npm run pretest && npm run test:node_smoke_tests && npm run test:promises_aplus && npm run test:jsdom",
"test:browser": "npm run pretest && npm run build:all && grunt karma:main",
"test:esmodules": "npm run pretest && npm run build:main && grunt karma:esmodules",
"test:jsdom": "npm run pretest && npm run build:main && grunt test:jsdom",
"test:no-deprecated": "npm run pretest && npm run build -- -e deprecated && grunt karma:main",
"test:selector-native": "npm run pretest && npm run build -- -e selector && grunt karma:main",
"test:slim": "npm run pretest && npm run build -- --slim && grunt karma:main",
"test:node_smoke_tests": "npm run pretest && npm run build:all && node build/tasks/node_smoke_tests.js",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"test:promises_aplus": "npm run build:main && node build/tasks/promises_aplus_tests.js",
"test": "npm run build:all && npm run lint && npm run test:browserless && npm run test:browser && npm run test:esmodules && npm run test:slim && npm run test:no-deprecated && npm run test:selector-native"
},
Docs: Updated links to https where they are supported. Close gh-2746
2015-11-29 17:41:37 +00:00
"homepage": "https://jquery.com",
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
"author": {
Docs: Change JS Foundation mentions to OpenJS Foundation Closes gh-4711
2020-05-18 16:41:32 +00:00
"name": "OpenJS Foundation and other contributors",
Build: Rename master to main across the repository The default branch was updated, this updates the remaining occurrences in code & comments. Closes gh-4838
2021-02-05 21:00:56 +00:00
"url": "https://github.com/jquery/jquery/blob/main/AUTHORS.txt"
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
},
"repository": {
"type": "git",
"url": "https://github.com/jquery/jquery.git"
},
"keywords": [
"jquery",
"javascript",
Build: Spaces vs tabs * Use tabs instead of spaces in jscs config * Always use spaces in package.json (really hope this is temporary)
2014-04-24 19:38:38 +00:00
"browser",
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
"library"
],
"bugs": {
Misc: Update all references to bugs.jquery.com Fixes gh-1681 Closes gh-1716
2014-10-17 05:01:37 +00:00
"url": "https://github.com/jquery/jquery/issues"
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
},
Build: Update the license attribute Specifying the type and URL is deprecated: https://docs.npmjs.com/files/package.json#license http://npm1k.org/ Fixes gh-2331 Closes gh-2330
2015-05-19 11:05:21 +00:00
"license": "MIT",
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
"devDependencies": {
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"@babel/cli": "7.22.9",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"@babel/core": "7.10.5",
"@babel/plugin-transform-for-of": "7.10.4",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"@prantlf/jsonlint": "14.0.3",
"@swc/core": "1.3.78",
CSS: Make the reliableTrDimensions support test work with Bootstrap CSS Bootstrap 5 includes the following CSS on the page: ```css *, *::before, *::after { box-sizing: border-box; } ``` That threw our `reliableTrDimensions` support test off. This change fixes the support test and adds a unit test ensuring support test values on a page including Bootstrap 5 CSS are the same as on a page without it. Fixes gh-5270 Closes gh-5278 Ref gh-5279
2023-07-10 16:33:05 +00:00
"bootstrap": "5.3.0",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"chalk": "5.3.0",
Tests: lock colors version to 1.4.0
2022-01-10 17:54:02 +00:00
"colors": "1.4.0",
Update node dependencies (sans jsdom, qunit, and sinon) Close gh-4098
2018-06-20 16:06:45 +00:00
"commitplease": "3.2.0",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"concurrently": "8.2.0",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"core-js-bundle": "3.6.5",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"eslint": "8.44.0",
"eslint-config-jquery": "3.0.1",
"eslint-plugin-import": "2.27.5",
"express": "4.18.2",
"globals": "13.20.0",
Build: Update Grunt from 1.4.1 to 1.5.3 This will resolve the following security issues: * Path Traversal in Grunt: https://github.com/advisories/GHSA-j383-35pm-c5h4 * Race Condition in Grunt: https://github.com/advisories/GHSA-rm36-94g8-835r Closes gh-5134
2022-10-03 21:06:37 +00:00
"grunt": "1.5.3",
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
"grunt-cli": "1.4.3",
Build: Update dependencies (except jsdom)
2016-04-23 17:25:47 +00:00
"grunt-git-authors": "3.2.0",
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
"grunt-karma": "4.0.2",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"husky": "8.0.3",
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
"jsdom": "19.0.0",
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
"karma": "6.4.1",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"karma-browserstack-launcher": "1.6.0",
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
"karma-chrome-launcher": "3.1.1",
"karma-firefox-launcher": "2.1.2",
Tests: add IE launcher for debugging IE11 on Windows
2018-11-12 16:49:44 +00:00
"karma-ie-launcher": "1.0.0",
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
"karma-jsdom-launcher": "12.0.0",
"karma-qunit": "4.1.2",
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
"karma-webkit-launcher": "2.1.0",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"load-grunt-tasks": "5.1.0",
Ajax: Support binary data (including FormData) Two changes have been applied: * prefilters are now applied before data is converted to a string; this allows prefilters to disable such a conversion * a prefilter for binary data is added; it disables data conversion for non-string non-plain-object `data`; for `FormData` bodies, it removes manually-set `Content-Type` header - this is required as browsers need to append their own boundary to the header Ref gh-4150 Closes gh-5197
2023-02-01 12:48:35 +00:00
"multiparty": "4.2.3",
Build: Update npm deps, fix Sinon npmcopy config 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
2016-01-27 11:54:39 +00:00
"native-promise-only": "0.8.1",
Selector: Stop relying on CSS.supports( "selector(...)" ) `CSS.supports( "selector(...)" )` has different semantics than selectors passed to `querySelectorAll`. Apart from the fact that the former returns `false` for unrecognized selectors and the latter throws, `qSA` is more forgiving and accepts some invalid selectors, auto-correcting them where needed - for example, mismatched brackers are auto-closed. This behavior difference is breaking for many users. To add to that, a recent CSSWG resolution made `:is()` & `:where()` the only pseudos with forgiving parsing; browsers are in the process of making `:has()` parsing unforgiving. Taking all that into account, we go back to our previous try-catch approach without relying on `CSS.supports( "selector(...)" )`. The only difference is we detect forgiving parsing in `:has()` and mark the selector as buggy. The PR also updates `playwright-webkit` so that we test against a version of WebKit that already has non-forgiving `:has()`. Fixes gh-5194 Closes gh-5206 Ref gh-5098 Ref gh-5107 Ref w3c/csswg-drafts#7676 Co-authored-by: Richard Gibson <richard.gibson@gmail.com>
2023-02-14 09:11:40 +00:00
"playwright-webkit": "1.30.0",
Build: Update promises-aplus-tests for compat with Node 7 The older promises-aplus-tests was relying on old Mocha that, in turn, used an obsolete graceful-fs version that is not guaranteed to work fine with the upcoming Node 7 and later.
2016-09-12 17:27:56 +00:00
"promises-aplus-tests": "2.1.2",
Update node dependencies (sans jsdom, qunit, and sinon) Close gh-4098
2018-06-20 16:06:45 +00:00
"q": "1.5.1",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"qunit": "2.10.1",
"raw-body": "2.4.1",
Build: Update most dependencies The only packages not fully updated are: - qunitjs & karma-qunit as that's a QUnit 2.x update that will require some changes and we'll do that later - jsdom as we need to first rewrite the test with the Symbol polyfill - newer jsdom versions don't work with such a hacked Symbol instance - sinon as the v2 -> v7 upgrade requires to update our unit tests - uglify-js & grunt-contrib-uglify as latest uglify-js versions slightly worsen the minified gzipped size Closes gh-4227 Closes gh-4228 Closes gh-4230 Closes gh-4232
2018-11-11 04:52:13 +00:00
"requirejs": "2.3.6",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"rimraf": "3.0.2",
"rollup": "2.21.0",
Build: Update Sinon from 2.3.7 to 7.3.1, other updates Closes gh-4341
2019-04-04 14:53:38 +00:00
"sinon": "7.3.1",
Build: Update dependencies This also resolves a security warning from GitHub about a vulnerable `request` version - the new `testswarm` package version depends on a fixed `request`. Closes gh-4732
2020-07-15 14:17:41 +00:00
"strip-json-comments": "3.1.1",
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
"testswarm": "1.1.2",
"yargs": "17.7.2"
Build: Specify valid components for commit messages Closes gh-1909
2014-12-07 06:46:25 +00:00
},
"commitplease": {
Build: use commitplease via husky, prohibit #NNNN github-style tickets Closes gh-3176
2016-06-16 09:42:26 +00:00
"nohook": true,
Build: Specify valid components for commit messages Closes gh-1909
2014-12-07 06:46:25 +00:00
"components": [
"Docs",
"Tests",
"Build",
Build: add "Support" module to commitplease list
2016-03-28 13:11:10 +00:00
"Support",
Build: Specify valid components for commit messages Closes gh-1909
2014-12-07 06:46:25 +00:00
"Release",
"Core",
"Ajax",
"Attributes",
"Callbacks",
"CSS",
"Data",
"Deferred",
Deprecated: fix amd mode for the deprecated module
2015-10-18 15:02:16 +00:00
"Deprecated",
Build: Specify valid components for commit messages Closes gh-1909
2014-12-07 06:46:25 +00:00
"Dimensions",
"Effects",
"Event",
"Manipulation",
"Offset",
"Queue",
"Selector",
"Serialize",
Build: Sanctify the component name status of Wrap
2015-01-12 03:24:02 +00:00
"Traversing",
"Wrap"
Build: use commitplease via husky, prohibit #NNNN github-style tickets Closes gh-3176
2016-06-16 09:42:26 +00:00
],
Build: fix markerPattern and ticketPattern regexes in package.json Commit messages used to fail the style check if they contained a word starting with "ref", like reformat or reference, in their message body. Close gh-3437 Ref jzaefferer/commitplease#91
2017-01-09 16:45:30 +00:00
"markerPattern": "^((clos|fix|resolv)(e[sd]|ing))|^(refs?)",
"ticketPattern": "^((Closes|Fixes) ([a-zA-Z]{2,}-)[0-9]+)|^(Refs? [^#])"
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
}
Initial grunt implementation
2012-04-18 20:07:35 +00:00
}
Reference in New Issue Copy Permalink