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

next-preactx

v1.0.1

Published

Plugin to enable Preact@>10 to a next project

Readme

Next and Preact X

There are a couple of original lines of code in here, almost all is repurposed from the official next-preact package and Jason Millers next-preact-demo.

This plugin exists for 3 reasons:

  • The official plugin is currently incompatible with the latest version of Preact (this has been fixed up, but is currently unreleased)
  • Adds support for Preact devtools
  • Adds a flag to allow an easier way to use Preact only in production.

If you aren’t interested in running React in dev and Preact in production then consider using npm aliases as it is by far the easiest solution (see Jason Millers demo.)

Getting Started

npm i -D next-preactx
npm i -S preact

Add the plugin to your next.config.js:

const withPreact = require('next-preactx')({
  enabled: process.env.NODE_ENV === 'production'
})

module.exports = withPreact({
  // Config options
})

To ensure that Preact also renders on the server you have to make sure you are setting up Preact aliases before starting your service.

This can either be done by creating a custom server for next to use and requiring next-preactx/alias within that entry script (as shown in the official plugin) or creating a custom javascript script to start the process:

// start.js

require('next-preactx/alias')()
require('next/dist/bin/next')

License

MIT