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

@vafast/bearer

v0.0.4

Published

Middleware for Vafast for retrieving Bearer token

Readme

@vafast/bearer

Middleware for Vafast for retrieving Bearer token.

This middleware is for retrieving a Bearer token specified in RFC6750.

This middleware DOES NOT handle authentication validation for your server, rather the middleware leaves the decision for developers to apply logic for handle validation check themself.

Installation

bun add @vafast/bearer

Example

import { Server, createHandler } from 'vafast'
import { bearer } from '@vafast/bearer'

// Define routes
const routes = [
  {
    method: 'GET',
    path: '/sign',
    handler: createHandler((req: any) => {
      const token = req.bearer
      if (!token) {
        return new Response(
          JSON.stringify({ error: 'Unauthorized' }),
          {
            status: 400,
            headers: {
              'Content-Type': 'application/json',
              'WWW-Authenticate': 'Bearer realm="sign", error="invalid_request"'
            }
          }
        )
      }
      return new Response(JSON.stringify({ token }), {
        headers: { 'Content-Type': 'application/json' }
      })
    }),
    middleware: [bearer()] // Add bearer middleware
  }
]

// Create server with bearer middleware
const server = new Server(routes)

// Export for Bun/Workers
export default {
  fetch: (req: Request) => server.fetch(req)
}

API

This middleware decorates bearer into the request object.

bearer

Extracted bearer token according to RFC6750, is either string or undefined.

If is undefined, means that there's no token provided.

Config

Below is the configurable property for customizing the Bearer middleware.

Extract

Custom extractor for retrieving tokens when the API doesn't compliant with RFC6750.

/**
 * If the API doesn't compliant with RFC6750
 * The key for extracting the token is configurable
 */
extract: {
    /**
     * Determined which fields to be identified as Bearer token
     *
     * @default access_token
     */
    body?: string
    /**
     * Determined which fields to be identified as Bearer token
     *
     * @default access_token
     */
    query?: string
    /**
     * Determined which type of Authentication should be Bearer token
     *
     * @default Bearer
     */
    header?: string
}

Features

  • ✅ RFC6750 compliant
  • ✅ Extract from Authorization header
  • ✅ Extract from query parameters
  • ✅ Extract from request body
  • ✅ Customizable field names
  • ✅ TypeScript support
  • ✅ Bun and Node.js compatible
  • ✅ Edge runtime ready