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

ts-hover-text

v1.0.0

Published

Get TypeScript hover text (QuickInfo) for test assertions.

Readme

ts-hover-text

Get TypeScript hover text (QuickInfo) for a symbol in a code string. Use this to test TypeScript type inference in your tests.

Installation

pnpm add -D ts-hover-text
# or
npm i -D ts-hover-text

Quick Start

import { tsHoverText } from 'ts-hover-text'

const getHoverText = tsHoverText({ sourceRoot: 'src' })

test('my type test', () => {
  const hover = getHoverText('const x: number = 1', 'x')
  expect(hover).toEqual(['const x: number'])
})

API

tsHoverText(options?)

Create a configured getHoverText function. Call this once per test file.

Options:

  • sourceRoot - Directory for resolving imports, relative to your project root (default: 'src')
  • tsConfigPath - Path to tsconfig.json (default: 'tsconfig.json')
  • trimmedLines - Return array of trimmed lines (default: true), or raw string (false)
  • compilerOptions - Override TypeScript settings

getHoverText(code, symbolName)

Get hover text for a symbol in your code string.

Parameters:

  • code - TypeScript code to analyze
  • symbolName - Identifier to get hover info for

Returns:

  • string[] - Trimmed lines (default)
  • string - Raw hover text (when trimmedLines: false)

Imports

Imports in your code resolve relative to sourceRoot, which is relative to your project root (where package.json is). For example:

// With sourceRoot: 'src'
getHoverText('import { Foo } from "./Foo"\nconst x = Foo', 'x')
// Resolves ./Foo to <project>/src/Foo.ts

Performance

The first call parses TypeScript lib and source directory files and takes around a second. Subsequent calls are usually around 50ms.

Examples

Test type inference:

/* eslint-disable @stylistic/indent */
test('object type inference', () => {
  const hover = getHoverText('const obj: { a: string; b: number }', 'obj')
  expect(hover).toEqual([
    'const obj: {',
      'a: string;',
      'b: number;',
    '}',
  ])
})

Test with imports:

// test/fixture.ts: export const foo = 'hello'
const getHoverText = tsHoverText({ sourceRoot: 'test' })

test('resolves imports', () => {
  const hover = getHoverText(
    'import { foo } from "./fixture"\nconst x = foo',
    'x'
  )
  expect(hover).toEqual(['const x: "hello"'])
})