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

@noctcore/eslint-plugin-architecture

v0.2.0

Published

Framework-agnostic folder-per-component and feature-boundary architecture ESLint rules.

Readme

@noctcore/eslint-plugin-architecture

Framework-agnostic folder-per-component and feature-boundary architecture rules. Flat-config only, ESLint 9+.

Install

bun add -D @noctcore/eslint-plugin-architecture   # or npm i -D / pnpm add -D

Use

// eslint.config.js
import architecture from '@noctcore/eslint-plugin-architecture';

export default [
  architecture.configs.recommended,
];

Or wire rules individually:

import architecture from '@noctcore/eslint-plugin-architecture';

export default [
  {
    plugins: { 'noctcore-architecture': architecture },
    rules: {
      'noctcore-architecture/component-folder-structure': ['error', { componentRoot: 'components' }],
      'noctcore-architecture/no-cross-feature-imports': ['error', { alias: '@/components' }],
      'noctcore-architecture/index-must-reexport-default': 'error',
    },
  },
];

Every rule anchors on a configurable directory segment (default components) rather than an absolute path, so it behaves the same whether ESLint runs from the repo root or per-package, on POSIX or Windows. Several rules inspect files on disk (sibling sets, barrel siblings, colocated tests), so run ESLint against real file paths, not virtual sources.

Rules

🔧 = autofixable · 💡 = provides an editor suggestion.

| Rule | Description | 🔧 | | --- | --- | --- | | barrel-purity | A barrel (index.ts / index.tsx) must contain only re-exports — no local declarations, side effects, or default-exported values. | | | colocated-test-required | A source file matching an include glob must have a colocated *.test.* / *.spec.* sibling on disk. Off until configured. | | | component-folder-structure | A component entry file must ship its full sibling set (hooks, types, story, test, barrel) on disk. | | | filename-matches-export | A file's basename must match its primary export (default export, or the sole named export). | 💡 | | index-must-reexport-default | A component folder's index.ts must re-export the sibling default named after the folder. | | | max-import-depth | A relative import may not climb more than max parent levels (default 3); autofixed to a path alias when one is configured. | 🔧 | | no-cross-feature-imports | A file in one feature may not import runtime code from another feature. | |