eslint-plugin-node
eslint-plugin-node copied to clipboard
mysticatea
Additional ESLint's rules for Node.js
For scripts that need to be run with `babel-node`, the shebang line should be ``` #!/usr/bin/env babel-node ``` The current `node/shebang` rule does not allow this. I suggest modifying the...
Node.js 16 has stable implementations of promised based timers, see https://nodejs.org/api/timers.html#timers_timers_promises_api It would be nice to have a rule to enforce this, similar to other "prefer-promises" rules.
https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-unpublished-import.md says: > ECMAScript 2015 (ES6) does not define the lookup logic and Node does not support modules yet. So this rule spec might be changed in future. This is...
```ts import type { ArrayExpression as _ArrayExpression, ObjectExpression as _ObjectExpression, ObjectProperty as _ObjectProperty, StringLiteral, } from '@babel/types' ```
Motivation: I'm always using `TypeScript` personally, for most packages we can use following settings: ```js { resolvePaths: [path.resolve('node_modules/@types')], tryExtensions: [ '.ts', '.tsx', '.d.ts', '.vue', '.js', '.jsx', '.json', '.node', ], }...
Prior to this, `eslint-plugin-node` would raise a `no-unpublished-*` if a file was not published, even if the package itself was set to private. This PR fixes that by making `util/check-publish`...
Ability to use a string or regex for allowModules. For example, say I have a directory I alias in typescript/webpack/whatever to `@foo`, I want to to allow everything in that...
`file-extension-in-import` when configured to require an extension reports the following import as invalid: ```js import "firebase/app"; ``` Using `--fix` changes the import to ```js import "firebase/app.js"; ``` Which is not...
We all know that usage of promises (and especially async/await) is superior to using non-promises in code. As such, would it not make sense to add these two to node-recommended,...