eslint-plugin-node
eslint-plugin-node copied to clipboard
mysticatea
Additional ESLint's rules for Node.js
Node docs allow you to use `||` in dependencies, and in our case here, engines field in package.json. If you have a semver range such as `>=8 = 14` it...
I would like to recommend to use extension as well as in `require(path)` To avoid shooting yourself in the foot for using extension-less path when someone later decides to switch...
ESLint v7.0.0 is [released](https://eslint.org/blog/2020/05/eslint-v7.0.0-released) 🎉 Dependencies should be compatible with ESLint 7 too before we can merge this one: - [x] [`eslint-plugin-es`](https://github.com/mysticatea/eslint-plugin-es) (https://github.com/mysticatea/eslint-plugin-es/issues/29) - [x] https://github.com/mysticatea/eslint-plugin-es/pull/30 - [x] [`v3.0.1`](https://github.com/mysticatea/eslint-plugin-es/releases/tag/v3.0.1) -...
This will create automatic PRs to update both dependencies + actions used in workflows, so we won't need manual PRs like #306 anymore --- As requested by @voxpelli in https://github.com/mysticatea/eslint-plugin-node/pull/224#issuecomment-982479160
Since this is already a breaking change, I also set Node to `>=10.0.0` whenever the `engines` field is not provided in `package.json` --- BREAKING CHANGE: Requires Node@^10.0.0 || ^12.0.0 ||...
I also fixed all ESLint errors/warnings this caused --- As requested by @voxpelli in https://github.com/mysticatea/eslint-plugin-node/pull/224#issuecomment-982479160
As requested by @voxpelli in https://github.com/mysticatea/eslint-plugin-node/pull/224#issuecomment-982479160
As requested by @voxpelli in https://github.com/mysticatea/eslint-plugin-node/pull/224#issuecomment-982479160
If a script requires a name exported using the [package.json "exports" field](https://medium.com/@nodejs/announcing-core-node-js-support-for-ecmascript-modules-c5d6dc29b663#3a15), it causes the [node/no-missing-require](https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-missing-require.md) rule to fail. For example: ```sh npm install yargs eslint eslint-plugin-node echo '{"extends":["plugin:node/recommended"]}' >...
