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

check-deprecations

v1.0.1

Published

Check for usage of @deprecated JSDoc symbols in a file

Readme

check-deprecations

Scan a source file for usage of symbols marked @deprecated in their JSDoc. Outputs nothing and exits 0 when the file is clean; prints each hit and exits 1 when deprecated usage is found.

Relies on TypeScript's language service, so it understands type resolution, re-exports, and overloads — not just grep.

Installation

npm install -g check-deprecations

Or run without installing:

npx check-deprecations <file>

Usage

check-deprecations <file>

Exit codes

| Code | Meaning | |------|---------| | 0 | No deprecated usage | | 1 | Deprecated usage found | | 2 | Error (file not found, missing argument) |

Example

$ check-deprecations src/api/client.ts
src/api/client.ts:12:3 - 'sendRequest' is deprecated. Use 'fetch' instead.
  sendRequest(url, opts);

src/api/client.ts:27:1 - The signature '(cb: Callback): void' of 'connect' is deprecated.
  connect(handleResponse);

If the file is clean, nothing is printed.

TypeScript / JavaScript support

The tool automatically looks for a tsconfig.json or jsconfig.json walking up from the target file and uses its compiler options. If none is found it defaults to allowJs + checkJs, so plain .js files work too.

Claude Code skill

This package ships a Claude Code skill at skills/check-deprecations/SKILL.md. Install it with dotagents:

npx @sentry/dotagents add poulet42/check-deprecations

Or declare it manually in agents.toml:

[[skills]]
name = "check-deprecations"
source = "poulet42/check-deprecations"

Then run:

npx @sentry/dotagents install

Once installed, ask Claude to check a file for deprecated usage:

/check-deprecations src/api/client.ts