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

@t18n/unused-strings

v0.0.1

Published

Utilities for detecting unused strings - the main export of this package can be used as a tsserver plugin and it also provides a CLI script for CI/hook integration

Downloads

12

Readme

Provides a script and tsserver plugin for detecting unused localization strings - this can help detect mistakes (e.g. copy paste errors may leave certain keys unused) or to find places where UI used to exist but has been removed and the strings can be cleaned up, reducing the bundle size and the cost to translate the codebase into new languages.

Typescript Language Service plugin

To see the unused strings highlighted in your editor, you can use this package as a Typescript Language Service plugin:

  1. Install this package
  2. Add a plugins config (or add this package to an existing config)
// tsconfig.json
{
    "compilerOptions": { /*...*/ }
    "plugins": [{ "name": "@t18n/unused-strings" }]
}
  1. You'll need to make sure your editor is using the workspace-local copy of Typescript: VSCode, for example, by default uses its own internal copy of typescript, which won't have the plugin installed. VSCode docs for using the workspace version instead

Manual CLI script

This package also installs a t18n-unused-strings script which can be run to check the entire codebase. This can be setup as part of a CI task or git hook

Options

  • -p/--project path to tsconfig - defaults to tsconfig.json in the local directory
  • --silent - disables any output other than reporting the unused strings (by default the output includes a count of how many strings were checked and how many unused strings were found)
  • --no-color - disables colored output (may be a good idea for CI builds)

Caveats / Ignoring

This detects whether localization keys have been used based on TS's reference tracking - it's the equivalent of using VSCode's "find references" on each string in each localization file. This works the most common usages but will fail to find cases where the localization string is only used by it's string path - e.g. renderString("foo.bar.baz") - and dynamic lookup patterns - e.g. t.someObject[someDynamicKey].

For these sort of cases, you can add // t18n-ignore-unused comments above a string (or an entire sub-object of strings) to ignore those strings from the checking