library-mirrors/jquery
1
0
Fork 0
mirror of https://github.com/jquery/jquery.git synced 2024-11-23 02:54:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
1a4d87afa0
jquery/package.json

118 lines
3.2 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: Updating the 3.x-stable version to 3.7.0-pre.
2022-12-13 23:48:46 +00:00
"version": "3.7.0-pre",
Fixes #14548. Add main property to package.json
2013-11-15 22:07:12 +00:00
"main": "dist/jquery.js",
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 (cherry picked from 11611967adf2bd9ff4304132f917629ec1134049)
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 (cherry picked from commit 8ae477a432f0924cd4bd3bdeaef2c4c15e483a8f)
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: 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
"@babel/core": "7.3.3",
"@babel/plugin-transform-for-of": "7.2.0",
Tests: lock colors version to 1.4.0
2022-01-10 20:40:24 +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: 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
"core-js": "2.6.5",
Build: Update eslint-config-jquery, fix linting violations Closes gh-4696 Ref jquery/eslint-config-jquery#15 Ref jquery/eslint-config-jquery#16 (cherry picked from commit ef4d6ca6c3a1b276fedc27b1f3a18823276f01a3)
2020-05-18 20:25:49 +00:00
"eslint-config-jquery": "3.0.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 (cherry picked from commit aa231cd21421503d319ad6068e7df0fb3baa7fea)
2022-10-03 21:06:37 +00:00
"grunt": "1.5.3",
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
"grunt-babel": "8.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 (cherry picked from commit 2525cffc42934c0d5c7aa085bc45dd6a8282e840)
2022-03-14 16:58:41 +00:00
"grunt-cli": "1.4.3",
Build: Fix grunt-compare-size branch-tip storage
2016-04-24 01:52:00 +00:00
"grunt-compare-size": "0.4.2",
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
"grunt-contrib-uglify": "3.4.0",
Update node dependencies (sans jsdom, qunit, and sinon) Close gh-4098
2018-06-20 16:06:45 +00:00
"grunt-contrib-watch": "1.1.0",
Build: Lint the minified jQuery file as well While we have absolutely no style-related expectations to our minified file, we do care that it's valid ES 5.1. This is now verified. Also, update grunt-eslint as a newer ESLint version is required to be able to use "extends" inside of the "overrides" section. Fixes gh-3075 Closes gh-4594 Ref gh-4598
2020-01-21 12:51:03 +00:00
"grunt-eslint": "22.0.0",
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 (cherry picked from commit 2525cffc42934c0d5c7aa085bc45dd6a8282e840)
2022-03-14 16:58:41 +00:00
"grunt-jsonlint": "2.1.2",
"grunt-karma": "4.0.2",
Build: update node dependencies; commit package-lock.json - Also ignore yarn.lock Close gh-3669
2017-06-26 15:03:45 +00:00
"grunt-newer": "1.3.0",
Build: Fix Travis build on Node.js 15 with npm 7 The `grunt-karma` version we used required Karma 3.x and it's now enforced in npm 7. Update a few Karma & Grunt-related packages to resolve the issue. Closes gh-4810
2020-11-17 16:05:41 +00:00
"grunt-npmcopy": "0.2.0",
Package: Sort devDependencies
2014-02-21 11:53:00 +00:00
"gzip-js": "0.3.2",
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 (cherry picked from commit 2525cffc42934c0d5c7aa085bc45dd6a8282e840)
2022-03-14 16:58:41 +00:00
"husky": "4.2.5",
"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 (cherry picked from commit b02a257f98688aa890e06a85672cd1a54c3ffa3a)
2023-01-23 22:49:44 +00:00
"karma": "6.4.1",
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 (cherry picked from commit 2525cffc42934c0d5c7aa085bc45dd6a8282e840)
2022-03-14 16:58:41 +00:00
"karma-browserstack-launcher": "1.6.0",
"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 (cherry picked from commit 2525cffc42934c0d5c7aa085bc45dd6a8282e840)
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 (cherry picked from commit b02a257f98688aa890e06a85672cd1a54c3ffa3a)
2023-01-23 22:49:44 +00:00
"karma-webkit-launcher": "2.1.0",
Build: Fix Travis build on Node.js 15 with npm 7 The `grunt-karma` version we used required Karma 3.x and it's now enforced in npm 7. Update a few Karma & Grunt-related packages to resolve the issue. Closes gh-4810
2020-11-17 16:05:41 +00:00
"load-grunt-tasks": "5.1.0",
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-5207 Ref gh-5206 Ref gh-5098 Ref gh-5107 Ref w3c/csswg-drafts#7676
2023-02-14 10:42:29 +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 QUnit from 1.23.1 to 2.9.2 Closes gh-4307
2019-03-04 19:10:21 +00:00
"qunit": "2.9.2",
Update node dependencies (sans jsdom, qunit, and sinon) Close gh-4098
2018-06-20 16:06:45 +00:00
"raw-body": "2.3.3",
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 sinon, husky, and qunitjs
2017-07-03 18:03:49 +00:00
"sinon": "2.3.7",
Build: Update dependencies (except jsdom)
2016-04-23 17:25:47 +00:00
"strip-json-comments": "2.0.1",
Build: Fix Travis build on Node.js 15 with npm 7 The `grunt-karma` version we used required Karma 3.x and it's now enforced in npm 7. Update a few Karma & Grunt-related packages to resolve the issue. Closes gh-4810
2020-11-17 16:05:41 +00:00
"testswarm": "1.1.2",
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
"uglify-js": "3.4.7"
Update requirejs to compatible version, remove r.js
2013-10-15 13:51:09 +00:00
},
"scripts": {
Use grunt and bower packages as local dependencies. Close gh-1433.
2013-11-14 15:17:18 +00:00
"build": "npm install && grunt",
"start": "grunt watch",
Build: Only run browser tests in one Node version on Travis Ref gh-3744 Closes gh-3894
2018-01-03 08:41:46 +00:00
"test:browserless": "grunt && grunt test:slow",
"test:browser": "grunt && grunt karma:main",
Build: Make Karma work in AMD mode Also, run such a suite in CI to make sure modules are working as expected when used directly. (partially cherry picked from 341c6d1b5abe4829f59fbc32e93f6a6a1afb900f) (partially cherry picked from 437f389a24a6bef213d4df507909e7e69062300b) Closes gh-4595 Ref gh-4550 Ref gh-4574
2020-01-21 12:26:47 +00:00
"test:amd": "grunt && grunt karma:amd",
Build:Tests: Fix custom build tests, verify on Travis; name Travis jobs This commit fixes unit tests for the following builds: 1. The no-deprecated build: `custom:-deprecated` 2. The current slim build: `custom:-ajax,-effects` 3. The 4.0 (#4553) slim build: `custom:-ajax,-callbacks,-deferred,-effects` It also adds separate Travis jobs for the no-deprecated & slim builds. Apart from that, add intuitive names to Travis jobs. Otherwise it's hard to see at a glance that a particular job is running on Firefox ESR, for example. Ref gh-4577 Ref gh-4596 Closes gh-4600
2020-01-27 17:54:47 +00:00
"test:no-deprecated": "grunt test:prepare && grunt custom:-deprecated && grunt karma:main",
Selector: Inline Sizzle into the selector module: 3.x version (#5113) This commit removes Sizzle from jQuery, inlining its code & removing obsolete workarounds where applicable. The Sizzle AUTHORS.txt file has been merged with the jQuery one - people are sorted by their first contributions to either of the two repositories. The main `selector` module can be disabled in favor of `selector-native` via: grunt custom:-selector For backwards compatibility, the legacy `sizzle` alias is also supported (it will be dropped in jQuery `4.0.0`): grunt custom:-selector Sizzle tests have been ported to jQuery ones. Ones that are not compatible with the `selector-native` module are disabled if the regular selector module is excluded. Backwards compatibility is still kept for all `Sizzle` utils - they continue to be available under `jQuery.find` - but the primary implementation is now attached directly to jQuery. Some selector utils shared by `selector` & `selector-native` have been extracted & deduplicated. `jQuery.text` and `jQuery.isXMLDoc` have been moved to the `core` module. The commit reduces the gzipped jQuery size by 851 bytes compared to the `3.x-stable` branch. Closes gh-5113 Ref gh-4395 Ref gh-4406
2022-12-14 00:41:31 +00:00
"test:selector-native": "grunt test:prepare && grunt custom:-selector && grunt karma:main",
Build:Tests: Fix custom build tests, verify on Travis; name Travis jobs This commit fixes unit tests for the following builds: 1. The no-deprecated build: `custom:-deprecated` 2. The current slim build: `custom:-ajax,-effects` 3. The 4.0 (#4553) slim build: `custom:-ajax,-callbacks,-deferred,-effects` It also adds separate Travis jobs for the no-deprecated & slim builds. Apart from that, add intuitive names to Travis jobs. Otherwise it's hard to see at a glance that a particular job is running on Firefox ESR, for example. Ref gh-4577 Ref gh-4596 Closes gh-4600
2020-01-27 17:54:47 +00:00
"test:slim": "grunt test:prepare && grunt custom:slim && grunt karma:main",
Selector: Inline Sizzle into the selector module: 3.x version (#5113) This commit removes Sizzle from jQuery, inlining its code & removing obsolete workarounds where applicable. The Sizzle AUTHORS.txt file has been merged with the jQuery one - people are sorted by their first contributions to either of the two repositories. The main `selector` module can be disabled in favor of `selector-native` via: grunt custom:-selector For backwards compatibility, the legacy `sizzle` alias is also supported (it will be dropped in jQuery `4.0.0`): grunt custom:-selector Sizzle tests have been ported to jQuery ones. Ones that are not compatible with the `selector-native` module are disabled if the regular selector module is excluded. Backwards compatibility is still kept for all `Sizzle` utils - they continue to be available under `jQuery.find` - but the primary implementation is now attached directly to jQuery. Some selector utils shared by `selector` & `selector-native` have been extracted & deduplicated. `jQuery.text` and `jQuery.isXMLDoc` have been moved to the `core` module. The commit reduces the gzipped jQuery size by 851 bytes compared to the `3.x-stable` branch. Closes gh-5113 Ref gh-4395 Ref gh-4406
2022-12-14 00:41:31 +00:00
"test": "npm run test:slim && npm run test:no-deprecated && npm run test:selector-native && grunt && grunt test:slow && grunt karma:main && grunt karma:amd",
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
"jenkins": "npm run test:browserless"
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? [^#])"
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
},
"husky": {
"hooks": {
Build: Fix commitplease husky config Fixes gh-4735 Closes gh-4737 (cherry picked from commit 3a1b338a7a579a45543b031a003abdce4dc6ac67)
2020-07-20 17:06:39 +00:00
"commit-msg": "commitplease .git/COMMIT_EDITMSG",
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
"pre-commit": "grunt lint:newer qunit_fixture"
}
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