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

@isbatak/panda-turbopack

v0.2.0

Published

Turbopack loader and Next.js config wrapper for Panda CSS v2: codegen, CSS injection and source transforms

Readme

@isbatak/panda-turbopack

Panda CSS v2 for Next.js on Turbopack, without the Panda CLI. It runs codegen, injects the generated CSS into your stylesheet, and rewrites css(), recipes, patterns and JSX style props into static class names at build time: the Turbopack counterpart of @pandacss/webpack.

Installation

pnpm add -D @isbatak/panda-turbopack @pandacss/dev

Next.js

Wrap your config:

import { withPandaCss } from "@isbatak/panda-turbopack/next"

export default withPandaCss(nextConfig)

Declare Panda's layers in a global stylesheet and import it from your root layout. The generated CSS is appended to it:

@layer reset, base, tokens, recipes, utilities;

next dev and next build need nothing else. The wrapper accepts a config object or a config function, so it composes with other wrappers.

Options

| Option | Default | Description | | ------------ | ------------------------------- | ------------------------------------------------------------------------------------ | | include | ["*.{jsx,tsx,js,mjs,ts,mts}"] | Turbopack rule globs whose modules are transformed. node_modules is never touched. | | cwd | process.cwd() | Project root the Panda config is discovered from. | | configPath | discovered upward from cwd | Explicit Panda config file, relative to cwd. |

How it works

  • When Next.js loads the config, withPandaCss runs codegen into your outdir and writes the runtime behind the virtual @pandacss-internal/css module to .panda/internal-css.mjs, aliasing the import to it because Turbopack only resolves files on disk. Add .panda to .gitignore.
  • It adds Turbopack rules that run @isbatak/panda-turbopack/loader on every include glob and on *.css.
  • On scripts, the loader calls transformSource from @pandacss/transformer.
  • On a stylesheet that declares Panda's layers, the loader extracts styles from your sources and appends the generated CSS. It registers the sources, their directories, the config and the design system as dependencies, so next dev updates the CSS when you edit or add a file. Config changes rerun codegen.
  • Like the Panda CLI in watch mode, next dev keeps styles you stop using until the server restarts.
  • Design-system and stylesheet diagnostics are reported as Turbopack warnings.

Without Next.js, use the pieces from the root entry: codegen, createTurbopackRules and mergeTurbopackRules.

License

MIT