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

@b4run/core

v0.12.0

Published

Low-level B4.run APIs for route discovery, configuration, state resolution, and type generation.

Readme

@b4run/core

Low-level B4.run APIs for configuration, capabilities, route discovery, state resolution, and type generation.

Use this when: You are building B4.run integrations or tooling below the author-facing SDK. Direct route authors should use @b4run/sdk instead.

Install

pnpm add @b4run/core

Example

The root export includes the typed configuration helper and pure type renderers:

import { config, renderB4Types } from "@b4run/core"

export const appConfig = config({
  build: { targets: ["node"] },
})

export const declarations = renderB4Types({ appRoot: "/app", routes: [] }, [])

Runtime and stability

  • @b4run/core is an edge-safe, low-level integration surface.
  • @b4run/core/node is a Node-only, low-level surface for filesystem discovery and compiler-backed extraction.
  • @b4run/core/internal/compiler is Node-only and internal. Application and integration code must not depend on it.

Importing /node registers the disk-backed b4.config.ts loader. The root stays free of that filesystem-loader edge so static runtimes can seed configuration instead.

Related

  • @b4run/sdk — author-facing agents, tools, middleware, and route contracts.
  • @b4run/cli — route discovery, type generation, development, and builds.
  • Core API reference — complete exports and surface boundaries.
  • Routes guide — B4.run's application and filesystem route model.

Maturity and support

This package is pre-1.0 and releases in B4.run's fixed package group. Review the changelog before upgrading. For support, open an issue.

License

MIT. See the repository license.