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

@zh2s/eslint-config-fsd

v1.0.1

Published

Eslint flat config for fsd methodology

Readme

@zh2s/eslint-config-fsd

Strict, modern, and customizable ESLint config for Feature-Sliced Design (FSD) — fully rewritten in TypeScript, enhanced with numeric layer ordering, and built for ESLint 9 with flat config support.

This ESLint configuration package extends the official @feature-sliced/eslint-config with practical improvements tailored for real-world TypeScript projects following the Feature-Sliced Design methodology.

✨ Features

  • Written in TypeScript — full type safety and maintainability
  • 🔢 Numeric layer prefixes — enforces FSD structure like 1-app, 2-pages, 3-widgets, 4-feature, 5-entities, 6-shared etc., for correct filesystem sorting
  • 🧱 ESLint 9 + Flat Config — native support for the modern flat configuration format (eslint.config.js)
  • 🧩 Modular ruleset — use the full config or import only what you need:
    • publicApi — validates proper public API exports (index.ts)
    • importOrder — enforces consistent import ordering and grouping
    • layersSlices — restricts illegal cross-layer/slice dependencies (with numeric layer awareness)
  • 📦 Up-to-date dependencies — all plugins and peer deps are regularly updated

📦 Installation

npm install --save-dev @zh2s/eslint-config-fsd

🛠️ Usage

Full configuration

import fsdEslintConfig from "@zh2s/eslint-config-fsd";

export default [
  fsdEslintConfig.flatConfig,
  // Add your project-specific overrides here if needed
];

Compose your own config

import { ESLint, Linter } from 'eslint'; // for layersSlices rules
import fsdEslintConfig from "@zh2s/eslint-config-fsd";
import importPlugin from 'eslint-plugin-import'; // for publicApi rules
import boundaries from 'eslint-plugin-boundaries'; // for layersSlices rules

const boundariesPlugin = boundaries as unknown as ESLint.Plugin;

export default [
  // your eslint configuration
  importPlugin.flatConfigs.recommended, // for publicApi and importOrder rules
  {
    plugins: { 
      ...fsdEslintConfig.plugins // for layersSlices rules
    }, 
    settings: {
      ...fsdEslintConfig.settings,  // for layersSlices rules
    },
    rules: {
      ...fsdEslintConfig.rules.publicApi,
      ...fsdEslintConfig.rules.layersSlices,
      ...fsdEslintConfig.rules.importOrder,
   }
  }
];

⚠️ Note

Please note that when using separate rules, you will need to manually import importPlugin and boundaries. Please review the example above carefully it shows the correct configuration.

📁 Expected Project Structure

src/
├── 1-app/
├── 2-pages/
├── 3-widgets/
├── 4-features/
├── 5-entities/
└── 6-shared/