Registry / devops / eslint-import-resolver-vite

eslint-import-resolver-vite

JSON →
library2.1.1jsnpmunverified

Vite module resolution plugin for eslint-plugin-import and eslint-plugin-import-x (resolver interface v3). Current stable version v2.1.1 (released 2025-04). Supports ESM, CJS, and mixed setups. Handles `resolve.alias` from Vite config. Critically, v2.x requires users to provide the config object explicitly, avoiding require() issues in mixed setups. Active development. Key differentiator: lightweight alternative to eslint-import-resolver-typescript when using Vite's alias feature.

npm install eslint-import-resolver-vite
INSTALL
IMPORT
SIG · ESLINT-IMPORT-RESO
E
eslint-import-resolver-vite
devopsjavascriptv2.1.1
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.

default export
import resolver from 'eslint-import-resolver-vite'
const resolver = require('eslint-import-resolver-vite')
default export works as a resolver for eslint-plugin-import settings
createViteImportResolver
import { createViteImportResolver } from 'eslint-import-resolver-vite'
import createViteImportResolver from 'eslint-import-resolver-vite'
Named export for eslint-plugin-import-x resolver interface v3
ResolverConfig
import type { ResolverConfig } from 'eslint-import-resolver-vite'
TypeScript type for the resolver config object

Setup eslint-import-resolver-vite with a Vite alias config and use it in ESLint settings.

// vite.config.ts export const viteConfigObj = { resolve: { alias: { _: path.resolve(__dirname, 'src') } } }; // .eslintrc.cjs module.exports = { settings: { 'import/resolver': { vite: { viteConfig: require('./vite.config').viteConfigObj } } } };
Debug
Known issues
breakingIn v2.0.0, the resolver no longer loads the Vite config automatically. You must pass `viteConfig` explicitly.
fix
Provide `viteConfig` option: `{ viteConfig: require('./vite.config').config }`
affects: >=2.0.0
gotchaMixing ESM and CJS may cause issues when importing the Vite config if it's ESM and you use `require()`. Use dynamic import or provide config as plain object.
fix
Use a separate CJS config file or convert to ESM config and use `import()` in a dynamic context.
affects: >=2.0.0
gotchaThe resolver only handles `resolve.alias`; it does not handle Vite plugins or other resolve options.
fix
For other custom resolution, consider using eslint-import-resolver-typescript or other resolvers.
affects: >=1.0.0
deprecatedFor `eslint-plugin-import-x` resolver interface v2 (deprecated), use default export. For v3, use `createViteImportResolver`.
fix
Use `createViteImportResolver` for v3, or upgrade to the latest version of eslint-plugin-import-x.
affects: >=2.0.0
Errors
Common errors & fixes
Failed to resolve a module with alias
Resolver cannot find the alias mapping because the Vite config is not provided or is incorrect.
fix
Check that you have passed the correct `viteConfig` object with `resolve.alias` defined.
Cannot find module 'eslint-import-resolver-vite'
Package not installed or ESLint cannot locate it.
fix
Run `npm install --save-dev eslint-import-resolver-vite` and ensure the module is in `node_modules`.
TypeError: viteConfig is not an object
The `viteConfig` option is empty or not an object.
fix
Provide a valid Vite config object: `{ viteConfig: { resolve: { alias: { ... } } } }`
Upgrade
Version history
2.1.1latest on npm
Audit
Dependencies
eslintrequiredpeer dependency for plugin integration
eslint-plugin-importoptionalprimary target for resolver
eslint-plugin-import-xoptionalalternative target for resolver v3
Agent activity
4 hits · last 30 days
node
4
Resources
eslint-import-resolver-vite — npm install eslint-import-resolver-vite · libregistry