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

@void-platforms/wow-talents

v0.0.1-alpha.7

Published

WoW talent snapshots + parsers + a tiny React renderer.

Downloads

95

Readme

@void-platforms/wow-talents

ALPHA: Rapid iteration phase. APIs, data formats, and visuals will change without notice. Expect breaking changes between alpha versions.

npm i @void-platforms/wow-talents@alpha

React Components

import { Render } from '@void-platforms/wow-talents'
;<Render
  talents={'<build string>'}
  snapshot='latest'
  config={{
    showTreeHeader: true,
    treeHeaderLabelClassName: 'text-red-500',
    treeHeaderPointsClassName: 'text-blue-500',
    nodeSize: 'md',
    nodeGap: 'md'
  }}
/>

Data Access (Node.js only)

import { getSpecIndex, getSpecTreeData } from '@void-platforms/wow-talents'

const specs = getSpecIndex()
const tree = getSpecTreeData('latest', 854, 577)

Note: This package is alpha; internal data shapes and rendering details may change.

Data from Blizzard's Game Data API.

Styling and Tailwind

This package does not automatically import Tailwind for consumers. You have two options:

If your app already uses Tailwind

  • Ensure your Tailwind build scans this package's source so utilities are generated. Add this package to your content globs (or safelist) in your Tailwind config.

    Examples:

    • Tailwind v3 config (framework-managed):

      // tailwind.config.js
      module.exports = {
        content: [
          './src/**/*.{js,ts,jsx,tsx}',
          './node_modules/@void-platforms/wow-talents/**/*.{js,ts,jsx,tsx}'
        ]
        // ...
      }
    • Tailwind v4 CLI flags:

      tailwindcss \
        --content "src/**/*.{js,ts,jsx,tsx,html}" \
        --content "node_modules/@void-platforms/wow-talents/**/*.{js,ts,jsx,tsx}"
  • Alternatively, import this package's precompiled stylesheet (see below) to avoid adjusting your content globs.

  • You can customize parts of the UI via props in config (e.g., treeHeaderLabelClassName, treeHeaderPointsClassName). These accept your own Tailwind classes from your app's config.

If your app does not use Tailwind

  • Import the precompiled stylesheet provided by this package:
import '@void-platforms/wow-talents/styles.css'

or include it in HTML:

<link
  rel="stylesheet"
  href="/node_modules/@void-platforms/wow-talents/dist/styles.css"
/>
  • This stylesheet includes Tailwind styles necessary for the renderer. It currently includes Tailwind's base/components/utilities, which may apply global resets (preflight). If that is undesirable, consider isolating the renderer (e.g., in a dedicated container or shadow root) or adjusting your app's CSS order.

Notes

  • The library intentionally avoids importing its own globals.css for consumers, to prevent double-injecting Tailwind and overriding host styles.
  • If you need a no-preflight stylesheet variant, please open an issue — we can ship an additional build without Tailwind base if needed.