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

@rodrick-hirebus/blindspot-report

v1.0.8

Published

Blindspot Report Viewer Component

Downloads

13

Readme

Project Structure & Code Organization

Package Manager

  • Use pnpm for all package installations and management

Core Libraries and Versions

  • React: ^18.x.x
  • React DOM: ^18.x.x
  • TypeScript: ^5.x.x
  • Tailwind CSS: ^3.x.x
  • shadcn/ui: Latest components
  • Zod: ^3.x.x
  • TanStack Router: ^1.x.x
  • Tanstack Query: ^5.x.x
  • Zustand: ^4.x.x

Naming Conventions

  • kebab-case - for all folders/files
  • _kebab-case - for feature domain's specific common modules
  • -kebab-case - for route domain's specific common modules
  • PascalCase - for classes and types
  • snake_case - for database tables and columns
  • camelCase - for functions, zod schemas and etc.

Common Modules

  • assets - for assets
  • components - for components
  • constants - for constants
  • contexts - for react context api
  • data - for data access layer (e.g. api, database)
  • hooks - for custom hooks, tanstack query and mutation
  • lib - for 3rd party integrations libraries
  • services - for business logic and orchestration of data access layer (Only if necessary)
  • stores - for stores (e.g. zustand)
  • types - for types
  • utils - for utilities

Domain Folders

  • src - main source code and shared common modules
  • src/routes - main router folder
  • src/features - main features folder (Only if necessary)

Shared Modules Structure

Shared modules follow this structure:

src/
├── assets/                 # Shared assets module
├── components/             # Shared dumb components module
│   └── ui/                 # UI components (button, input, etc.)
├── constants/              # Shared constants module
├── contexts/               # Shared react context api module
├── data/                   # Shared data access layer module (e.g. API functions, database)
├── hooks/                  # Shared custom hooks, tanstack query and mutation
│   ├── use-[custom].ts  # Shared custom hook
│   └── query/              # TanStack Query hooks
│       └── [entity]/  # TanStack Query entity folder
│           ├── use-[entity]-query.ts     # Shared react-query query
│           └── use-[entity]-mutation.ts  # Shared react-query mutation
├── lib/                    # Shared 3rd party integrations
├── services/               # Shared business logic
├── stores/                 # Shared state stores (e.g. zustand)
├── types/                  # Shared types
└── utils/                  # Shared utilities

Routes Domain Structure - Default

When creating new page/route files, follow this structure:

src/routes/<route-name>/
├── index.tsx               # Route's index page
├── -components/            # Route's components
├── -constants/             # Route's constants
├── -contexts/              # Route's react context API
├── -hooks/                 # Route's hooks
├── -types/                 # Route's types
└── -utils/                 # Route's utilities

Feature Domain Structure - Optional

When creating new feature files, follow this structure:

src/features/<feature-name>/
├── _assets/                # Feature's assets
├── _components/            # Feature's components
├── _constants/             # Feature's constants
├── _contexts/              # Feature's react context API
├── _data/                  # Feature's data access layer
├── _hooks/                 # Feature's custom hooks, tanstack query and mutation
├── _lib/                   # Feature's 3rd party integrations
├── _services/              # Feature's business logic
├── _stores/                # Feature's state stores (e.g. zustand)
├── _types/                 # Feature's types
└── _utils/                 # Feature's utilities