As it seems, airbnb and others have migrate to eslint v7, it is now safe to upgrade to v7.

Related issues

• eslint v7 support airbnb/javascript#2223
• https://eslint.org/docs/user-guide/migrating-to-7.0.0#additional-lint-targets

Possibly these errors can come up if you use v1.x.x of this package with eslint v7.x.x

Node.js/Commonjs Rules have been deprecated(read more) in favour of eslint-plugin-node

This plugin will be used from v2.x.x of thi config package

Released in v2.2.3

For anyone who's migrating from v1.x.x to v2.x.x that uses Eslint v7 by default,

1. Remove everything(it is better)

yarn remove @abhijithvijayan/eslint-config @typescript-eslint/eslint-plugin @typescript-eslint/parser babel-eslint eslint eslint-config-airbnb eslint-config-prettier eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-prettier eslint-plugin-react eslint-plugin-react-hooks prettier

2. Reinstall with new dependencies

# npm
npx install-peerdeps @abhijithvijayan/eslint-config --dev

# yarn
npx install-peerdeps @abhijithvijayan/eslint-config --dev --yarn

3. Optional (if using TypeScript)

.eslintrc.json

{
	"extends": [
		...
		"@abhijithvijayan/eslint-config/typescript"
		...
	],
	// add this line
	"parserOptions": {
		"project": "./tsconfig.json",
		"sourceType": "module" // https://github.com/mysticatea/eslint-plugin-node#-configs
	},
	"rules": {
		// custom overrides
	}
}

As it seems like eslint-plugin-node throws a lot of errors even when it is not used for Node.js Apps.

Maybe it could be used as an option module to be used just like typescript or react

Update: config now exposes separate node module config as well

The node/file-extension-in-import rule in eslint-plugin-node adds the extension of file imported(as for --experimental-modules in Node.js 12) but TypeScript seems to cause issues when having "moduleResolution": "node" in tsconfig.json.

It might be set to explicit by the TypeScript team.

See related issues:

• Provide a way to add the '.js' file extension to the end of module specifiers microsoft/TypeScript#16577
• Allow to control the output file extension of the generated javascript file during compilation microsoft/TypeScript#39303

For now I can't seem to make both Eslint & TypeScript happy.

I am temporarily disabling the rule.