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 🙏

© 2024 – Pkg Stats / Ryan Hefner

eslint-import-resolver-next

v0.4.1

Published

The next resolver for `eslint-plugin-import` or `eslint-plugin-import-x`

Downloads

281

Readme

eslint-import-resolver-next

npm npm npm

The next resolver plugin for eslint-plugin-import or eslint-plugin-import-x that resolves modules with oxc-resolver.

Features

  • Resolves modules using the oxc-resolver package.
  • Support mono-repos and pnpm-workspaces.yaml.
  • Support paths alias defined in tsconfig.compilerOptions.paths or jsconfig.compilerOptions.paths.

Usage

  1. Install the package:
npm install -D eslint-import-resolver-next
  1. Add it as a resolver to your ESLint configuration.

Example config:

module.exports = {
  // ... other configuration options
  settings: {
    "import/resolver": {
      next: {
        // Options for the resolver
      },
    },
  },
};

with Mono-repo:

module.exports = {
  // ... other configuration options
  settings: {
    "import/resolver": {
      next: {
        packages: ["packages/*"],
      },
    },
  },
};

pnpm-workspaces:

module.exports = {
  // ... other configuration options
  settings: {
    "import/resolver": {
      next: {
        packages: {
          pnpmWorkspace: true,
          includeRoot: true,
        },
      },
    },
  },
};
  1. For eslint-plugin-import-x resolver-next
const { createNextImportResolver } = require("eslint-import-resolver-next");

module.exports = {
  // ... other configuration options
  settings: {
    "import-x/resolver-next": [createNextImportResolver({
      // Options for the resolver
    })],
  },
};

Options

  • roots (Array): The directories to search for modules. Default: [process.cwd()].

  • alias (Record<string, string | string[]>): The paths alias. Default: undefined.

    • The alias can be set as relative paths. relative paths are resolved from the package directory.
  • tsconfig (boolean | string | object): Weather to use the tsconfig.json file. Default: true.

    • If true, the resolver will try to find the tsconfig.json file close to the source file.
    • If a string, it's the name of the file to search for.
    • If an object, see the tsconfig option in the oxc-resolver package.
  • jsconfig (boolean | string | object): Weather to use the jsconfig.json file. Default: true.

    • If true, the resolver will try to find the jsconfig.json file close to the source file.
    • If a string, it's the name of the file to search for.
  • packages (string[] | PackageOptions): The patterns or options to search for packages. Default: undefined.

    • If an array, the resolver will search for packages in the specified patterns.
    • If an object, see the PackageOptions.

All other options are passed to the oxc-resolver package. See the oxc-resolver documentation

PackageOptions

A folder with a package.json file is considered a package. The PackageOptions object can have the following properties:

  • patterns (string[]): The patterns to search for packages. Default: ["."].
  • ignore (string[]): The directories to ignore. Default: ["**/node_modules/**", "**/test/**", "**/tests/**"].
  • includeRoot (boolean): Weather to include the root directory. Default: false.
  • pnpmWorkspace (boolean | string): Weather to use the pnpm-workspace.yaml file to find packages. Default: false.
    • If true, the resolver will try to find the pnpm-workspace.yaml file in the package directory.
    • If a string, define the path to the pnpm-workspace.yaml file.