Eslint - Revision history

M: /* also */

2023-12-29T17:53:33Z

also

← Older revision		Revision as of 17:53, 29 December 2023
Line 14:		Line 14:
	** An eslint dialog should pop up, click Allow. Should be all you need.		** An eslint dialog should pop up, click Allow. Should be all you need.

	===== ~~also~~ =====		===== Custom formatting =====
	[https://www.digitalocean.com/community/tutorials/linting-and-formatting-with-eslint-in-vs-code Per-project setup]		First do [https://www.digitalocean.com/community/tutorials/linting-and-formatting-with-eslint-in-vs-code Per-project setup].

			Then you can edit this in your project:
			.eslintrc.json

	==== Configuration ====		==== Configuration ====

2023-12-29T17:52:45Z

Installation

← Older revision		Revision as of 17:52, 29 December 2023
Line 13:		Line 13:
	** Restart vscode and open a project with JS files.		** Restart vscode and open a project with JS files.
	** An eslint dialog should pop up, click Allow. Should be all you need.		** An eslint dialog should pop up, click Allow. Should be all you need.

			===== also =====
			[https://www.digitalocean.com/community/tutorials/linting-and-formatting-with-eslint-in-vs-code Per-project setup]

	==== Configuration ====		==== Configuration ====

2020-09-20T20:21:40Z

eslint rules

← Older revision		Revision as of 20:21, 20 September 2020
Line 39:		Line 39:
	eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:		eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:
	* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.		* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.
			* No trailing spaces, even in comments
			* String literals must use single quotes; JSX strings must use double quotes.
			I'm not even sure which rule is causing some of those restrictions. It gets complicated. So don't go too crazy.

2020-09-18T22:25:02Z

Configuration

← Older revision		Revision as of 22:25, 18 September 2020
Line 32:		Line 32:
	},		},
	};		};
	Otherwise, ~~this will~~ step you through it. Use the google format as a baseline:		Otherwise, use one of these to step you through it. Use the google format as a baseline:
	~~cd myproject~~		* Run the vscode command EsLint: Create EsLint configuration
	eslint --init		* Run the [eslint --init] command from the root of your project

	==== eslint rules ====		==== eslint rules ====
	eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:		eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:
	* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.		* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.

2020-09-18T22:23:26Z

Installation

← Older revision		Revision as of 22:23, 18 September 2020
Line 8:		Line 8:
	# Then from your project...		# Then from your project...
	npm install --save-dev eslint-config-google		npm install --save-dev eslint-config-google
	* Configure eslint ~~in one of these ways:~~		* Configure eslint (see below)
	** Run the vscode command EsLint: Create EsLint configuration
	** Run the [eslint --init] command from the root of your project
	** Copy an .eslintrc.js file from another project into the root of your project.
	* Install the eslint vscode extension.		* Install the eslint vscode extension.
	** Get the eslint extension		** Get the eslint extension

2020-09-18T22:22:56Z

Installation

← Older revision		Revision as of 22:22, 18 September 2020
Line 8:		Line 8:
	# Then from your project...		# Then from your project...
	npm install --save-dev eslint-config-google		npm install --save-dev eslint-config-google
	* Install the eslint vscode extension.
	* Configure eslint in one of these ways:		* Configure eslint in one of these ways:
	** Run the vscode command EsLint: Create EsLint configuration		** Run the vscode command EsLint: Create EsLint configuration
	** Run the [eslint --init] command from the root of your project		** Run the [eslint --init] command from the root of your project
	** Copy an .eslintrc.js file from another project into the root of your project.		** Copy an .eslintrc.js file from another project into the root of your project.
	* Restart ~~the~~ project~~, and~~ eslint should ~~prompt~~ you ~~to allow it to be enabled~~.		* Install the eslint vscode extension.
			** Get the eslint extension
			** Restart vscode and open a project with JS files.
			** An eslint dialog should pop up, click Allow. Should be all you need.

	==== Configuration ====		==== Configuration ====

2020-09-18T22:21:21Z

vscode integration

← Older revision		Revision as of 22:21, 18 September 2020
Line 36:		Line 36:
	cd myproject		cd myproject
	eslint --init		eslint --init

	~~==== vscode integration ====~~
	* Get the eslint extension
	* Restart vscode and open a project with JS files.
	* An eslint dialog should pop up, click Allow. Should be all you need.

	==== eslint rules ====		==== eslint rules ====
	eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:		eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:
	* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.		* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.

2020-09-18T22:20:13Z

Installation

← Older revision		Revision as of 22:20, 18 September 2020
Line 3:		Line 3:
	==== Installation ====		==== Installation ====
	Do NOT USE APT, it is available and seems to work but this is a node module. Don't be stupid, use npm. Note the mind-bogglingly-insane number of dependencies. Node world, you scare me...		Do NOT USE APT, it is available and seems to work but this is a node module. Don't be stupid, use npm. Note the mind-bogglingly-insane number of dependencies. Node world, you scare me...
			* Install eslint node module
	# From anywhere...		# From anywhere...
	npm install -g eslint		npm install -g eslint
	# ~~From~~ your project		# Then from your project...
	npm install --save-dev eslint-config-google		npm install --save-dev eslint-config-google
			* Install the eslint vscode extension.
			* Configure eslint in one of these ways:
			** Run the vscode command EsLint: Create EsLint configuration
			** Run the [eslint --init] command from the root of your project
			** Copy an .eslintrc.js file from another project into the root of your project.
			* Restart the project, and eslint should prompt you to allow it to be enabled.

	==== Configuration ====		==== Configuration ====

2020-09-18T19:25:45Z

← Older revision		Revision as of 19:25, 18 September 2020
Line 34:		Line 34:
	* Restart vscode and open a project with JS files.		* Restart vscode and open a project with JS files.
	* An eslint dialog should pop up, click Allow. Should be all you need.		* An eslint dialog should pop up, click Allow. Should be all you need.

			==== eslint rules ====
			eslint rules are generally ridiculously aggressive, truly for the OCD. But you get used to it, for better or worse. There are some pretty stupid ones, eg:
			* [https://eslint.org/docs/rules/no-mixed-operators No mixed operators]! Durrr... learn to program.

2020-09-02T17:44:11Z

Configuration

← Older revision		Revision as of 17:44, 2 September 2020
Line 15:		Line 15:
	'es2020': true,		'es2020': true,
	},		},
	'extends': ['eslint:recommended', 'google'],		// this is insane: 'extends': ['eslint:recommended', 'google'],
			'extends': ['google'],
	'parserOptions': {		'parserOptions': {
	'ecmaVersion': 11,		'ecmaVersion': 11,