Skip to content

gluestack-ui v5 reaches stable with Tailwind CSS v4 and NativeWind v5

updated

The gluestack-ui team has announced the stable release of gluestack-ui v5. Following an alpha/preview phase, the release is described as production-ready, with full support for Tailwind CSS v4, NativeWind v5, deep Expo integration and a streamlined developer experience.

Native-first focus

With v5, the project is shifting its focus entirely to native mobile performance, building on NativeWind v5 (which uses Tailwind CSS v4) and Expo Router. As part of this change, the library footprint has been simplified:

  • Next.js support dropped: Next.js and universal monorepo adapters have been deprecated so the team can focus on React Native and Expo.
  • Expo Router first: Stable integrations with Expo Router are available out of the box.

CSS-first theming with Tailwind CSS v4

Tailwind CSS v4 uses a CSS-first setup that removes tailwind.config.js entirely. Design tokens now live in CSS files using @layer theme definitions, covering colors, typography, border-radii and dark mode overrides:

@layer theme {
  :root {
    --primary: 23 23 23;
    --background: 255 255 255;
  }
  @media (prefers-color-scheme: dark) {
    :root {
      --primary: 255 245 245;
    }
  }
}

@theme inline {
  --color-primary: rgb(var(--primary));
}

Redesigned CLI

The CLI initialization process has been redesigned to be faster, cleaner and strictly non-interactive when necessary. A new Expo and gluestack-ui v5 project can be created with:

npm create gluestack@latest

Existing v4 codebases can use the dedicated upgrade utility:

npx gluestack-ui upgrade

The utility guides users through updating package dependencies, migrating styling to CSS-first variables, setting up PostCSS and configuring Metro builds.

Upgrade notes

  • CSS variables: Design tokens must live in global.css instead of tailwind.config.js.
  • lightningcss: lightningcss should be pinned to 1.30.1 in resolutions/overrides to avoid build-time Metro compilation errors.
  • Re-adding components: After upgrading, components should be re-added via the CLI to get their stable v5 implementations:
npx gluestack-ui add button accordion modal

The team thanked the community for feedback during the alpha and preview stages and pointed developers to the updated Quick Start Guide.

Source: gluestack.io