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

@openuiai/next

v16.3.0

Published

OpenNext.js - A development-focused fork of Next.js with Bun support

Readme

This is a modified fork of Next.js optimized for runtime flexibility and self-hosted deployments.

Why This Fork?

Run Next.js anywhere, your way. This fork removes vendor lock-in and gives you the freedom to choose your runtime and bundler:

  • Bun Runtime — Run your entire Next.js app on Bun for blazing-fast startup, native TypeScript, and up to 4x faster installs
  • Rspack Bundler — Drop-in Webpack alternative with significantly faster build times
  • Self-Hosted First — Optimized for your own infrastructure, not only Vercel
  • Production Ready — All build processes passing, TypeScript fully supported

Run Next.js on Bun

Drop-in Bun compatibility. No configuration needed—use bun instead of node:

bun install          # 4x faster than npm
bun run dev          # Native TypeScript, instant startup
bun run build        # Production builds
bun run start        # Production server on Bun

Why Bun?

| Benefit | What You Get | |---------|--------------| | Instant Startup | Bun's optimized runtime starts in milliseconds | | Native TypeScript | No transpilation step—run .ts files directly | | 4x Faster Installs | bun install leaves npm/yarn/pnpm in the dust | | Lower Memory | JavaScriptCore engine uses less memory than V8 | | Faster Processes | Bun.spawn() outperforms Node.js child_process |

Full Compatibility

This fork includes a comprehensive adapter layer that makes Next.js work seamlessly on Bun:

  • Automatic Runtime Detection — Detects Bun/Node.js and optimizes accordingly
  • Process Adapter — Uses Bun.spawn() for all child processes
  • AsyncLocalStorage — Full support with Bun-specific optimizations
  • Module Loading — Leverages Bun's native TypeScript support

Bun Limitations

Transparency matters. Here's what to know:

| Feature | Status | Notes | |---------|--------|-------| | Core Next.js | ✅ Full | Pages, App Router, API routes all work | | AsyncLocalStorage | ✅ Full | Server Actions, rendering context preserved | | Child Processes | ✅ Full | Uses faster Bun.spawn() under the hood | | Source Maps | ⚠️ Graceful fallback | Stack traces work; programmatic resolution limited | | node:crypto | ⚠️ Partial | Some methods unavailable; Web Crypto works | | node:vm | ⚠️ Limited | Edge cases may differ from Node.js | | Complex IPC | ⚠️ Partial | For heavy IPC, consider Node.js |


Use Rspack Instead of Webpack

Get faster builds with Rspack—a Rust-based Webpack-compatible bundler:

# Just set the environment variable
NEXT_RSPACK=1 bun run dev
NEXT_RSPACK=1 bun run build

Rspack provides significantly faster build times while maintaining Webpack compatibility. Experimental but functional.


Current Status

| Component | Status | |-----------|--------| | Build System | ✅ All processes passing | | Bun Runtime | ✅ Full Bun 1.x support | | Rspack Bundler | ✅ Experimental, functional | | TypeScript | ✅ All declaration errors resolved | | Webpack | ✅ Production-ready (default) |


Documentation

Getting Started

Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful JavaScript tooling for fast builds.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Community

The OpenNext.js community can be found on GitHub Discussions where you can ask questions, voice ideas, and share your projects with other people.

Do note that our Code of Conduct applies to all community channels. Users are highly encouraged to read and adhere to it to avoid repercussions.

Contributing

Contributions to OpenNext.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing.

Good First Issues:

We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process.


Security

If you believe you have found a security vulnerability in OpenNext.js, we encourage you to responsibly disclose this and NOT open a public issue.

Please report security issues via GitHub Security Advisories.