jquery/.eslintrc-browser.json

{
	"root": true,

	"extends": "jquery",

	"reportUnusedDisableDirectives": true,

	"parserOptions": {
		"ecmaVersion": 5
	},

	// The browser env is not enabled on purpose so that code takes
	// all browser-only globals from window instead of assuming
	// they're available as globals. This makes it possible to use
	// jQuery with tools like jsdom which provide a custom window
	// implementation.
	"env": {},

	"globals": {
		"window": true
	},

	"rules": {
		"one-var": ["error", {"var": "always"}],
		"strict": ["error", "function"]
	}
}
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: Drop support for IE <11, iOS <11, Firefox <65, Android Browser & PhantomJS Also, update support comments format to match format described in: https://github.com/jquery/contribute.jquery.org/issues/95#issuecomment-69379197 with the change from: https://github.com/jquery/contribute.jquery.org/issues/95#issuecomment-448998379 (open-ended ranges end with `+`). Fixes gh-3950 Fixes gh-4299 Closes gh-4347 2019-04-29 20:56:09 +00:00			`"ecmaVersion": 5`
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			`},`

			`// The browser env is not enabled on purpose so that code takes`
			`// all browser-only globals from window instead of assuming`
			`// they're available as globals. This makes it possible to use`
			`// jQuery with tools like jsdom which provide a custom window`
			`// implementation.`
			`"env": {},`

			`"globals": {`
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			`"window": 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			`},`

			`"rules": {`
Build: Enable ESLint one-var rule for var declarations in browser code Node.js code is written more & more commonly in ES6+ so it doesn't make sense to enable it there. There are many violations in test code so it's disabled there as well. Closes gh-4615 2020-03-02 21:25:35 +00:00			`"one-var": ["error", {"var": "always"}],`
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			`"strict": ["error", "function"]`
			`}`
			`}`