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

@hatkom/lint-tools

v1.2.0

Published

Dead-code lint tools for NestJS + GraphQL monorepos: find unused GraphQL fields and unused service methods.

Downloads

502

Readme

@hatkom/lint-tools

Dead-code lint tools for NestJS + GraphQL monorepos. Two Bun CLIs that fail CI when the codebase carries unused server surface area.

Expected monorepo structure

These tools are convention-based, not configurable. They assume the standard layout below and resolve every path relative to the directory you run them from (process.cwd()), which must be the monorepo root. There is no config file — if your repo deviates from this layout, the tools will not find the right files.

<repo root>/                      ← run the CLIs here
├── apps/
│   ├── api/                      ← the one NestJS GraphQL API
│   │   ├── schema.gql            ← generated SDL (regenerate before linting)
│   │   ├── tsconfig.json         ← used by ts-morph to load the project
│   │   └── src/
│   │       ├── **/*.resolver.ts  ← @Query / @Mutation / @ResolveField scanned
│   │       └── **/*.service.ts   ← @Injectable() services scanned
│   └── <frontend>/               ← any number of frontends
│       ├── graphql-env.ts        ← marks an app as a GraphQL consumer
│       └── src/**/*.{ts,tsx}     ← scanned for selected fields

Conventions baked in:

  • The API app is always apps/api; it is excluded from frontend discovery.
  • Frontend apps are auto-discovered: any apps/* directory containing a graphql-env.ts (so adding a new frontend needs no config change).
  • GraphQL model class names map to schema types by stripping a trailing Model suffix (e.g. ConversationModelConversation).

Tools

A single lint-tools binary runs every check below in sequence and exits 1 if any of them report dead code.

Unused GraphQL fields

Finds GraphQL surface area no frontend ever selects: root @Query/@Mutation, @ResolveField, and orphan object types. Since every consumer lives in the monorepo, anything unselected is dead. Items behind @ApiKeyAuth (and the types reachable from them) are skipped — external API consumers are invisible from inside the repo.

Reads apps/api/schema.gql, runs graphql-inspector coverage against the discovered frontend apps, then cross-references resolver decorators. Exits 1 on any unused item, or if a resolver entry can't be parsed (so dead fields can't slip through silently).

Requires a fresh apps/api/schema.gql — generate the schema first.

Unused service methods

Finds public methods / arrow-function properties on @Injectable() NestJS services with zero call sites (via ts-morph reference analysis). Skips private members, decorated members (framework-invoked), and NestJS lifecycle hooks. Annotate an intentional keeper with a leading // dead-code-ignore-next-line comment. Exits 1 on any unused member.

Usage

bun add -D @hatkom/lint-tools
// package.json
{
  "scripts": {
    "lint:dead-code": "lint-tools"
  }
}

Ships with a #!/usr/bin/env bun shebang and uses Bun runtime APIs — run it with Bun.