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-for-sort-import

v1.0.5

Published

ESLint plugin for sorting imports

Readme


theme: z-blue

编写思路

  • 通过编写 eslint 插件
  • 在 ast 遍历过程中筛选出所有导入语句
  • 记录排序前导入语句代码块内容
  • 对导入语句进行排序
  • 比对排序前后导入语句代码块
  • 若不一样则进行替换

排序规则

  • 对导入语句进行分组
    • npm 包
    • 相对路径/绝对路径
      • 判断路径中是否携带指定路径类型(ex.['components', 'api']),若携带则划分至该路径类型组
      • ex. import aa from './../seller/components/aa',划分至 components 组
      • 若不携带,则正向遍历找到第一个路径,划分至该路径分组
      • ex. import aa from './../hooks/aa',划分至 hooks 组
      • 若存在分组内仅有一条导入语句,划分至合并分组
    • import type
  • 属性排序
    • 针对具名导入,属性由短至长排序
  • 组内排序
    • 导入语句由短至长排序
  • 组间排序
    • npm 包最前,合并分组 & 类型导入分组位于最后
    • 其余分组按照导入语句数量由短至长排序
    • 组间空一行

插件使用

pnpm add eslint-plugin-for-sort-import -D
// eslint.config.js
import importSortPlugin from 'eslint-plugin-for-sort-import'

export default [
  importSortPlugin(),
]

若未生效可重启编辑器 or

ctrl + shift + p,输入 restart eslint server

参数说明

export interface PluginConfig {
  /** 行尾风格: 'lf' 或 'crlf' */
  end_of_line: 'lf' | 'crlf'
  /** 缓存大小限制 */
  max_cache_size: number
  /** 路径类型识别列表 */
  path_type: string[]
}
  • end_of_line: 行尾风格,默认 'lf'
    • 用于决定换行符采用 '\n' 还是 '\r\n'
  • max_cache_size: 缓存大小限制
    • 插件采用了 LRU Cache,缓存文件排序后的结果
  • path_type: 路径类型识别列表
    • 用于指定分组

核心逻辑

此处仅展示了最简单的将导入语句按照长短排序

export const sortImportsRule = {
  meta: {
    type: 'suggestion',
    docs: {
      description: '导入语句按照指定规则排序',
      category: 'Stylistic Issues',
      recommended: false
    },
    fixable: 'code'
  },
  create(context) {
    return {
      Program(node) {
        const sourceCode = context.getSourceCode()

        // 筛选出所有导入声明
        const importDeclarations = node.body.filter((node) => node.type === 'ImportDeclaration')
        if (importDeclarations.length === 0) return

        // 获取当前导入代码块
        const start = importDeclarations[0].range[0]
        const end = importDeclarations[importDeclarations.length - 1].range[1]
        const currentText = sourceCode.text.slice(start, end)

        // 生成排序后的导入代码块
        const group = [...importDeclarations]
        group.forEach((node, index) => {
          group[index].processedText = sourceCode.getText(node)
        }
        group.sort((a, b) => a.processedText.length - b.processedText.length)
        const newImports = group.map((node) => node.processedText).join('\n')

        // 如果当前导入代码块不等于排序后的导入代码块,则重新排序,进行修复
        if (currentText !== newImports) {
          context.report({
            node: importDeclarations[0],
            message: '导入语句未按照排序规则进行排序',
            fix(fixer) {
              return fixer.replaceTextRange([start, end], newImports)
            }
          })
        }
      }
    }
  }
}

最后

感兴趣的可移步源码