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-plugin-alias-paths

v0.0.2

Published

ESLint plugin for replacing deep relative import paths with project aliases.

Readme

eslint-plugin-alias-paths

ESLint plugin for replacing deep relative import paths with project aliases.

This plugin is useful when a project already uses path aliases such as @/. It detects imports like ../../utils/date and reports an autofix to rewrite them as alias imports such as @/utils/date.

Why

Deep relative imports make files harder to move and harder to read.

import { formatDate } from "../../../shared/date";

When the same project also supports an alias such as @/, the import can be written from the project root instead:

import { formatDate } from "@/shared/date";

eslint-plugin-alias-paths enforces that convention from a configurable import depth.

Installation

Requires Node.js >=24 and ESLint >=10.

pnpm add -D eslint-plugin-alias-paths
yarn add -D eslint-plugin-alias-paths
npm install -D eslint-plugin-alias-paths

Usage

Add the plugin and enable alias-paths/prefer-alias-paths in your ESLint configuration.

// eslint.config.js
import { defineConfig } from "eslint/config";
import aliasPaths from "eslint-plugin-alias-paths";

export default defineConfig([
  {
    plugins: {
      "alias-paths": aliasPaths,
    },
    rules: {
      "alias-paths/prefer-alias-paths": [
        "warn",
        {
          basePath: import.meta.dirname,
          targetPath: "src",
          aliasedPath: "@/",
          depth: 2,
        },
      ],
    },
  },
]);

With the configuration above, imports that go up at least two directories are rewritten to the configured alias.

// before
import { Button } from "../../components/Button";

// after
import { Button } from "@/components/Button";

Rule Options

basePath

Absolute base path for the project. In most eslint.config.js files this can be import.meta.dirname.

targetPath

Path below basePath that should be replaced by the alias. For example, use "./src" when @/ points to the src directory.

aliasedPath

Alias prefix used in import paths. For example, "@/".

depth

Minimum relative import depth to report.

Supported values are positive integers.

Examples:

| depth | Reports imports starting with | | ------- | ----------------------------- | | 1 | ../ | | 2 | ../../ | | 3 | ../../../ | | 4 | ../../../../ | | 5 | ../../../../../ |

Scope

This plugin only rewrites static import declarations. It does not configure TypeScript, bundlers, test runners, or runtime module resolution. Configure those tools separately so the alias in aliasedPath resolves correctly.

Currently, the plugin does not handle require(), dynamic import(), or export declarations.