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

uniwind-plugin-next

v1.2.0

Published

Compatibility plugin for using Uniwind with Next.js

Readme

uniwind-plugin-next

This is an unofficial plugin, and is not affiliated with Uniwind or Next.js.

Uniwind config plugin for Next.js. Note that only Webpack-based projects are supported, there are no plans to support Turbopack-based projects.

Example

See a fully working example project here: Demo (Source)

Compatibility

See the table below for tested versions of uniwind-plugin-next and corresponding versions of uniwind. Other versions of uniwind may work, but are not guaranteed to.

Tested on Next 16.1, but other versions will likely work fine.

| uniwind-plugin-next | Uniwind | |---------------------|---------| | 1.1.x | 1.2.2 | | 1.2.x | 1.2.2 |

Installation & setup

This setup guide assumes you already have a next.js project setup with Tailwind v4

  1. Install uniwind and this plugin. You will probably also need @expo/next-adapter if you don't already have it, to handle react-native web support.
pnpm install uniwind uniwind-plugin-next @expo/next-adapter
  1. Wrap next.js config with withUniwind()
// next.config.ts
import type { NextConfig } from "next";
import { withExpo } from "@expo/next-adapter";
import { withUniwind } from 'uniwind-plugin-next'

const nextConfig: NextConfig = {
    transpilePackages: ['react-native', 'react-native-web'],
};

// Wrap your config with `withUniwind()`
export default withUniwind(withExpo(nextConfig), {
    cssEntryFile: './app/globals.css',
    // Takes the same options as the vite & metro plugins.
    // See https://docs.uniwind.dev/api/metro-config#configuration-options
});
  1. Add the postcss plugin
const config = {
  plugins: {
    'uniwind-plugin-next/postcss': {}, // Add this line
    '@tailwindcss/postcss': {},
  },
};
  1. Add @import 'uniwind'; to the global CSS file (or wherever you @import 'tailwindcss')
/* src/app/globals.css */
@import 'tailwindcss';
@import 'uniwind';
  1. Add suppressHydrationWarning to root <html> tag (in app/layout.tsx by default)
// src/app/layout.tsx
...

return (
    <html lang="en" suppressHydrationWarning>
      ...
    </html>
);
  1. Start the dev server to generate uniwind-types.d.ts. Make sure that it's included in your tsconfig.json's include array.

SSR Considerations

  • This plugin marks all Uniwind web components with 'use client' automatically, so you do not need to do this manually.

  • Be aware that some Uniwind features, such as withUniwind and useResolveClassNames will not work in a server environment, as they rely on accessing window or document.

  • Additional code is required to avoid a flash of unstyled content (FOUC). See the example project for reference.