eslint-plugin-no-use-extend-native
eslint-plugin-no-use-extend-native copied to clipboard
ESLint plugin to prevent use of extended native objects
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 🙂
It'd be great if you could support ESLint's flat config: 1. https://eslint.org/docs/latest/use/configure/configuration-files-new 1. https://eslint.org/blog/2022/08/new-config-system-part-1/ 1. https://eslint.org/blog/2022/08/new-config-system-part-2/ 1. https://eslint.org/docs/latest/use/configure/migration-guide
Any advice on using with react-native, i tried but so many rules collided like " to ' and ' to "
As mentioned in https://github.com/sindresorhus/module-requests/issues/25. Investigate possibility of looking at variable declarations and assignments to understand the type. This way things such as: ``` javascript var test = []; // some-library.js...
https://github.com/sindresorhus/xo/issues/61 Potentially not JS file types? I'd assume ESLint wouldn't emit the right Node types for this plugin to even get hit, but worth looking into.
ESLint [recommends](https://eslint.org/docs/latest/use/configure/configuration-files#configuration-naming-conventions) a name for flat configs. Tools like https://github.com/eslint/config-inspector can use this to indicate the source of rules.
This should be linted with https://www.npmjs.com/package/eslint-plugin-n
Using eslint v9.10.0 On macOS with homebrew I get some warnings, but eslint runs ```sh (node:51025) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time...