Registry / testing / eslint-import-resolver-jsconfig

eslint-import-resolver-jsconfig

JSON →
library1.1.0jsnpmunverified

Resolver for eslint-plugin-import that resolves import aliases defined in jsconfig.json. Version 1.1.0 is current; the package is stable and updated irregularly. It enables ESLint to understand path aliases in jsconfig (common in Create React App projects) without Webpack configuration. Unlike eslint-import-resolver-webpack or eslint-import-resolver-alias, this resolver directly reads jsconfig.json and is lightweight with no heavy dependencies.

npm install eslint-import-resolver-jsconfig
INSTALL
IMPORT
SIG · ESLINT-IMPORT-RESO
E
eslint-import-resolver-jsconfig
testingjavascriptv1.1.0
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

jsconfig resolver
settings: { 'import/resolver': { jsconfig: { config: 'jsconfig.json' } } }
settings: { 'import/resolver': { 'eslint-import-resolver-jsconfig': { config: 'jsconfig.json' } } }
The resolver key in settings should be 'jsconfig', not the package name. Configure in .eslintrc or eslint config.
extensions option
settings: { 'import/resolver': { jsconfig: { extensions: ['.js', '.jsx', '.ts', '.tsx'] } } }
Specify file extensions for the resolver to check when resolving modules. Defaults to '.js' and '.jsx'.

Configures ESLint to resolve aliases from jsconfig.json, enabling import/no-unresolved to understand path aliases.

// Install: npm install eslint-import-resolver-jsconfig --save-dev // .eslintrc.js module.exports = { settings: { 'import/resolver': { jsconfig: { config: 'jsconfig.json', }, }, }, rules: { 'import/no-unresolved': 'error', }, };
Debug
Known issues
gotchaThe resolver key in settings must be 'jsconfig', not the full package name. Common mistake: using 'eslint-import-resolver-jsconfig' as key.
fix
Use 'jsconfig' as the key in settings.import/resolver.
affects: >=1.0.0
gotchaRequires jsconfig.json to be present and valid. If config path is wrong or file missing, resolver fails silently.
fix
Ensure jsconfig.json exists and path is correct (default: './jsconfig.json').
affects: >=1.0.0
deprecatedPackage has not been updated since 2020; may not support newer ESLint or eslint-plugin-import versions.
fix
Consider alternative resolvers like eslint-import-resolver-typescript or eslint-import-resolver-alias if compatibility issues arise.
affects: >=1.0.0
Errors
Common errors & fixes
Error: Cannot find module 'eslint-import-resolver-jsconfig'
Package not installed or not in node_modules.
fix
Run 'npm install eslint-import-resolver-jsconfig --save-dev'.
Error: Unable to resolve path to module 'components/Button'
Alias not defined in jsconfig.json or resolver not configured properly.
fix
Check that jsconfig.json includes 'compilerOptions.paths' with the alias mapping, and that the resolver settings key is 'jsconfig'.
Upgrade
Version history
1.1.0latest on npm
Audit
Dependencies
eslint-plugin-importrequiredPeer dependency required for resolver functionality
debugrequiredUsed for logging resolver activity
resolverequiredUsed to resolve module paths
Agent activity
2 hits · last 30 days
node
2
Resources
eslint-import-resolver-jsconfig — npm install eslint-import-resolver-jsconfig · libregistry