eslint-plugin-node
eslint-plugin-node copied to clipboard
mysticatea
Additional ESLint's rules for Node.js
If `package.json` file has "private" set to *true*, it will restrict the package from being published to the registry. Therefor having `node/no-unpublished-import` rule enabled does not make sense.
This commit adds support for the crypto.randomUUID method, which was added to the standard lib in v14.17.0. https://nodejs.org/docs/latest-v14.x/api/crypto.html#crypto_crypto_randomuuid_options
Should be either "X was deprecated in Y", or "X has been deprecated since Y", but not "was...since"
It seems `node/no-extraneous-import` should not report when using TypeScript `import type ...`. import type is used for compilation only, so there's no risk at all to hit runtime errors because...
Hello, I'm using Node 14 and all of my project is managed as a module (`"type": "module"` in package.json). Until now, using everywhere imports and exports, I didn't see this...
## Summary This attempts to resolve #250 by specifying the supported version for dynamic imports. I'll open some discussions on the code around some of my changes. I wasn't sure...
Oops, accidentally deleted my fork of this repo without realising #323 was still open
ESLint v8.0.0 is [released](https://eslint.org/blog/2021/10/eslint-v8.0.0-released) 🎉 It would be awesome to have official ESLint 8 support. 👊 I'm happy to help where I can of course 🙂 --- Follow-up of #223
Looks like the thing is `chalk v5` uses [`export`](https://github.com/chalk/chalk/blob/v5.0.0/package.json#L9) instead of `main`.
