jquery/.eslintrc-node.json

{
	"root": true,

	"extends": "jquery",

	"reportUnusedDisableDirectives": true,

	"parserOptions": {
		"ecmaVersion": 2018
	},

	"env": {
		"es6": true,
		"node": true
	},

	"rules": {
		"strict": ["error", "global"]
	}
}
Build: ESLint setup improvements 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). 2016-11-02 23:51:34 +00:00			`{`
			`"root": true,`

			`"extends": "jquery",`

Build: Enable reportUnusedDisableDirectives in ESLint This forbids unnecessary `eslint-disable` comments. Ref gh-4095 Closes gh-4520 2020-04-20 17:01:20 +00:00			`"reportUnusedDisableDirectives": true,`

Build: ESLint setup improvements 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). 2016-11-02 23:51:34 +00:00			`"parserOptions": {`
Core: Migrate from AMD to ES modules 🎉 Migrate all source AMD modules to ECMAScript modules. The final bundle is compiled by a custom build process that uses Rollup under the hood. Test files themselves are still loaded via RequireJS as that has to work in IE 11. Tests can now be run in "Load as modules" mode which replaces the previous "Load with AMD" option. That option of running tests doesn't work in IE and Edge as it requires support for dynamic imports. Some of the changes required by the migration: * check `typeof` of `noGlobal` instead of using the variable directly as it's not available when modules are used * change the nonce module to be an object as ECMASscript module exports are immutable * remove some unused exports * import `./core/parseHTML.js` directly in `jquery.js` so that it's not being cut out when the `ajax` module is excluded in a custom compilation Closes gh-4541 2019-11-18 20:15:03 +00:00			`"ecmaVersion": 2018`
Build: ESLint setup improvements 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). 2016-11-02 23:51:34 +00:00			`},`

			`"env": {`
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305 2019-03-04 17:30:51 +00:00			`"es6": true,`
Build: ESLint setup improvements 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). 2016-11-02 23:51:34 +00:00			`"node": true`
Build: Require strict mode in Node.js scripts via ESLint So far, only browser-based JS files were required to be in strict mode (in the function form). This commit adds such a requirement to Node.js scripts where the global form is preferred. All Node.js scripts in sloppy mode were converted to strict mode. Closes gh-4499 2019-10-08 22:17:55 +00:00			`},`

			`"rules": {`
			`"strict": ["error", "global"]`
Build: ESLint setup improvements 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). 2016-11-02 23:51:34 +00:00			`}`
			`}`