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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@digicroz/jwt

v1.0.1

Published

Production-grade JWT utilities with complete type safety, timing-safe verification, and error handling without throwing. Fully typed, tested, and optimized for modern TypeScript projects.

Readme

@digicroz/jwt

Production-grade JWT utilities with complete type safety, zero thrown errors, and timing-safe verification.

npm version npm downloads TypeScript Test Coverage MIT License

A modern, type-safe JWT library for Node.js and TypeScript. Built with security-first design, comprehensive type inference, and production-ready error handling. Never throws errors—always returns a Result type for predictable error handling.

🌟 Features

  • 🔒 Type-Safe: Full TypeScript support with generic payload types
  • 🚫 No Throw Errors: All operations return Result<T> (success | error)
  • ⏱️ Timing-Safe: Protection against timing attacks on token verification
  • 🧪 Fully Tested: 79 tests with 82% coverage
  • ⚡ Production-Ready: Error types, detailed diagnostics, and error chaining
  • 📦 Single Dependency: Only depends on jsonwebtoken
  • 🌐 Universal: Works in Node.js and modern browsers
  • 📝 Well Documented: Comprehensive JSDoc and examples

🎯 Why @digicroz/jwt?

Problem: Traditional JWT Libraries

// Old way - Throws errors, poor type safety
try {
  const payload = await jwtVerifyAsync(token, secret)
  // payload type is unknown!
} catch (err) {
  // Handle multiple error types
}

Solution: @digicroz/jwt

// New way - Type-safe, no thrown errors
const result = await jwtVerify<CustomPayload>(token, secret)

if (result.success) {
  // result.data is typed as CustomPayload!
  console.log(result.data.userId)
} else {
  // Handle specific error types
  console.error(`${result.error.type}: ${result.error.message}`)
}

📦 Installation

npm install @digicroz/jwt

🚀 Quick Start

Verify JWT Token

import { jwtVerify } from "@digicroz/jwt"

// Define your payload type
interface AuthPayload {
  userId: string
  email: string
  role: "admin" | "user"
}

const result = await jwtVerify<AuthPayload>(token, secret)

if (result.success) {
  console.log(`User: ${result.data.userId}`)
} else {
  console.error(`Verification failed: ${result.error.type}`)
}

Sign JWT Token

import { jwtSign } from "@digicroz/jwt"

const payload = { userId: "123", role: "admin" }

const result = jwtSign(payload, secret, {
  expiresIn: "1h",
  issuer: "my-app",
})

if (result.success) {
  console.log(`Token: ${result.data}`)
} else {
  console.error(`Signing failed: ${result.error.message}`)
}

Decode JWT Token

import { jwtDecode } from "@digicroz/jwt"

// Decode without verification - inspect token contents
const result = jwtDecode<AuthPayload>(token)

if (result.success) {
  console.log(result.data) // Payload without verification
} else {
  console.error("Invalid token structure")
}

📚 API Reference

jwtVerify<T>(token, secret, options?)

Verify and decode a JWT token asynchronously.

const result = await jwtVerify<PayloadType>(token, secret, {
  algorithms: ["HS256"],
  issuer: "my-app",
  audience: "my-api",
  ignoreExpiration: false,
  clockTolerance: 0,
})

Returns: Promise<Result<T>>

jwtSign<T>(payload, secret, options?)

Sign and create a JWT token synchronously.

const result = jwtSign(payload, secret, {
  expiresIn: "24h",
  issuer: "my-app",
  subject: "user-auth",
  audience: "my-api",
  algorithm: "HS256",
})

Returns: Result<string>

jwtDecode<T>(token, options?)

Decode a JWT token without verification.

const result = jwtDecode<PayloadType>(token, {
  complete: false,
})

Returns: Result<T>

🛡️ Error Handling

Error Types

import { JwtErrorType } from "@digicroz/jwt"

enum JwtErrorType {
  INVALID_TOKEN = "INVALID_TOKEN",
  EXPIRED_TOKEN = "EXPIRED_TOKEN",
  INVALID_SIGNATURE = "INVALID_SIGNATURE",
  MALFORMED_TOKEN = "MALFORMED_TOKEN",
  INVALID_ALGORITHM = "INVALID_ALGORITHM",
  VERIFICATION_FAILED = "VERIFICATION_FAILED",
  SIGNING_FAILED = "SIGNING_FAILED",
  INVALID_SECRET = "INVALID_SECRET",
  UNKNOWN_ERROR = "UNKNOWN_ERROR",
}

Error Handling Patterns

// ✅ BEST DX: Direct equality check
const result = await jwtVerify(token, secret)
if (result.success === false) {
  // TypeScript knows result.error exists here
  console.error(`Error: ${result.error.message}`)
}

// ✅ ALSO GOOD: Check success === true
if (result.success === true) {
  // TypeScript knows result.data exists here
  console.log(result.data)
}

// ✅ ALTERNATIVE: Using type guards
import { isSuccess, isError } from "@digicroz/jwt"

if (isError(result)) {
  console.error(result.error.type)
} else if (isSuccess(result)) {
  console.log(result.data)
}

// ✅ FOR COMPLEX LOGIC: Specific error handling
if (result.success === false) {
  switch (result.error.type) {
    case JwtErrorType.EXPIRED_TOKEN:
      // Handle expired token
      break
    case JwtErrorType.INVALID_SIGNATURE:
      // Handle invalid signature
      break
    default:
    // Handle other errors
  }
}

// ❌ DON'T USE: Negation pattern (!result.success)
// TypeScript can't narrow the type properly with negation
// if (!result.success) {
//   console.error(result.error) // TS Error!
// }

🔐 Security Features

Timing-Safe Comparison

Protects against timing attacks:

import { timingSafeEqual } from "@digicroz/jwt/utils"

const isEqual = timingSafeEqual(secret1, secret2)

Token Structure Validation

Quick structural validation before full verification:

import { isValidTokenStructure } from "@digicroz/jwt/utils"

if (!isValidTokenStructure(token)) {
  console.error("Invalid token format")
}

📋 Usage Examples

Express Middleware

import { jwtVerify, JwtErrorType } from "@digicroz/jwt"

export async function authMiddleware(req, res, next) {
  const token = req.headers.authorization?.split(" ")[1]

  if (!token) {
    return res.status(401).json({ error: "Missing token" })
  }

  const result = await jwtVerify(token, process.env.JWT_SECRET)

  if (!result.success) {
    if (result.error.type === JwtErrorType.EXPIRED_TOKEN) {
      return res.status(401).json({ error: "Token expired" })
    }
    return res.status(401).json({ error: "Invalid token" })
  }

  req.user = result.data
  next()
}

Refresh Token Flow

const refreshResult = await jwtVerify(refreshToken, process.env.REFRESH_SECRET)

if (refreshResult.success) {
  // Issue new access token
  const newToken = jwtSign(
    { userId: refreshResult.data.userId },
    process.env.JWT_SECRET,
    { expiresIn: "1h" }
  )

  if (newToken.success) {
    return res.json({ accessToken: newToken.data })
  }
}

return res.status(401).json({ error: "Token refresh failed" })

🧪 Testing

Run the test suite:

# Run all tests
npm run test

# Run with coverage
npm run test:coverage

# Watch mode
npm run test:watch

# UI mode
npm run test:ui

📈 Performance

  • No thrown errors: Eliminates overhead of exception handling
  • Timing-safe verification: Constant-time comparison prevents timing attacks
  • Tree-shakeable: Only import what you need
  • Lightweight: Single dependency (jsonwebtoken)

🔄 Migration from jwtVerifyAsync

Before (Old approach):

try {
  const payload = await jwtVerifyAsync(token, secret)
} catch (err) {
  // Handle error
}

After (New approach):

const result = await jwtVerify(token, secret)
if (result.success) {
  const payload = result.data
}

📝 API Types

Result Type

type Result<T> =
  | { success: true; data: T }
  | { success: false; error: JwtError }

JwtPayload Interface

interface JwtPayload {
  [key: string]: unknown
  iat?: number // Issued at
  exp?: number // Expiration time
  nbf?: number // Not before
  iss?: string // Issuer
  sub?: string // Subject
  aud?: string | string[] // Audience
  jti?: string // JWT ID
}

🆘 Troubleshooting

TypeScript Error: "Type does not satisfy constraint 'JwtPayload'"

Your payload type must have an index signature:

// ✅ Correct
interface AuthPayload extends Record<string, unknown> {
  userId: string
}

// ❌ Wrong
interface AuthPayload {
  userId: string
}

"Invalid token" Error Even with Valid Token

Check these common issues:

  1. Wrong secret: Ensure the secret matches the one used to sign
  2. Expired token: Check expiration time with jwtDecode()
  3. Malformed token: Verify token has 3 parts separated by dots
  4. Clock skew: Use clockTolerance option for synchronization issues

📄 License

MIT © Adarsh Hatkar

🤝 Contributing

Contributions welcome! Please open an issue or submit a PR.

🔗 Links