npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-import-resolver-oxc

v0.15.0

Published

A simply wrapped `oxc-resolver` for `eslint-plugin-import-x` and `eslint-plugin-import`

Readme

eslint-import-resolver-oxc

npm version npm download npm bundle size License

A simply wrapped oxc-resolver for eslint-plugin-import-x and eslint-plugin-import.

[!NOTE]

As of now, eslint-import-resolver-typescript has been fully optimized for performance by using unrs-resolver.

We recommend prioritizing the officially maintained resolver.

Feature

A good replacement for eslint-import-resolver-node.

You can get more info about resolver in the README of eslint-plugin-import-x.

Usage

Installation

npm install eslint-import-resolver-oxc --save-dev

Add script for eslint.config.js

For eslint-plugin-import-x(>=4.5.0):

// eslint.config.js
export default [
  {
    settings: {
      'import-x/resolver-next': [
        createOxcImportResolver({
          // resolver options
        }),
        // other resolvers
      ]
    }
  }
]

[!NOTE]

According to https://github.com/un-ts/eslint-plugin-import-x/blob/master/src/utils/resolve.ts#L155

The settings prefix is hard coded as import-x/ even with flat config.

// eslint.config.js
export default [
  {
    settings: {
      'import-x/resolver': 'oxc'
    }
  }
]

or

// eslint.config.js
export default [
  {
    settings: {
      'import-x/resolver': {
        oxc: true
        // other resolvers...
      }
    }
  }
]

or

// eslint.config.js
export default [
  {
    settings: {
      'import-x/resolver': {
        oxc: {
          // resolver options...
        },
        // other resolvers...
      }
    }
  }
]

For eslint-plugin-import:

Replace import-x/resolver with import/resolver in the object above.

Options

Default options see normalizeOptions.ts

bundlerConfig (experimental, only supported in async function)

This option can be a string or an object.

String option:

the path of the bundler's config file.

Object option:

  • type: the type of the bundler.
  • path: the config of the bundler.
  • options: some special options for bundler config.

If only the type is specified, the configuration file in the root directory (cwd) will be automatically detected, similar to how tsconfig is handled.

If only the path is specified, thetype will be inferred based on the filename.

// eslint.config.js
import { createOxcImportResolver, transformViteConfig } from 'eslint-import-resolver-oxc'

export default [
  {
    settings: {
      'import-x/resolver-next': [
        await createOxcImportResolver({
          bundlerConfig: 'vite.config.ts',
        }),
      ]
    }
  }
]

others

The jsconfig.json and tsconfig.json in the root directory (cwd) will automatically detected.

More options see oxc-resolver

Motivation

Eslint is a bit slow in large projects. While I track the performance of the rules, I found that eslint-plugin-import-x took a lot of time. I thought change a resolver might bring some improvements.

Credit

I can't finish the project without the help of oxc-resolver.

Thanks @Boshen for his work on oxc-resolver.

License

MIT License © 2024-PRESENT Vida Xie