canirequire › CommonJS › @react-native-community/eslint-config
Is @react-native-community/eslint-config ESM-only? Can you require() it?
ESLint config for React Native
Last verified Sep 9, 2026 against @react-native-community/eslint-config@3.2.0. JSON
CommonJS CommonJS — require() works on every Node.js version
@react-native-community/eslint-config ships CommonJS only. require("@react-native-community/eslint-config") works everywhere. import "@react-native-community/eslint-config" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Does @react-native-community/eslint-config@3.2.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@react-native-community/eslint-config") from a CommonJS file and import "@react-native-community/eslint-config" from an ES module.
| Runtime | require("@react-native-community/eslint-config") | import "@react-native-community/eslint-config" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4 | ✓ works | ✓ works |
How to import @react-native-community/eslint-config
ES modules (import)
import eslintConfig from "@react-native-community/eslint-config";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const eslintConfig = require("@react-native-community/eslint-config");Module format by version
Derived from the type, main and exports fields of every stable release on npm (16 versions; the newest 16 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.1 – 3.2.0 | CommonJS | Mar 5, 2019 |
Frequently asked
Is @react-native-community/eslint-config ESM-only?
@react-native-community/eslint-config@3.2.0 is a CommonJS package. @react-native-community/eslint-config ships CommonJS only. require("@react-native-community/eslint-config") works everywhere. import "@react-native-community/eslint-config" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import @react-native-community/eslint-config with ES module syntax?
Yes. import eslintConfig from "@react-native-community/eslint-config" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does @react-native-community/eslint-config work in Bun?
Yes. import "@react-native-community/eslint-config" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @react-native-community/eslint-config ship TypeScript types?
No. @react-native-community/eslint-config ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- webpack-stream 7.0.0CommonJS
- vue-property-decorator 9.1.2CommonJS
- loader.js 4.7.0CommonJS
- ember-load-initializers 3.0.1ESM-only
- gulp-mocha 10.0.1ESM-only
- load-grunt-tasks 5.1.0CommonJS
- karma-phantomjs-launcher 1.0.4CommonJS
- broccoli-asset-rev 3.0.0CommonJS