FG
💻 Software🌐 Web & Full-Stack

v4 alpha does not work on Stackblitz

Freshabout 1 year ago
Mar 14, 20260 views
Confidence Score80%
80%

Problem

What version of Tailwind CSS are you using? 4.0.0-alpha.6 What build tool (or framework if it abstracts the build tool) are you using? Vite 5.1.5 What version of Node.js are you using? v18.18.0 What browser are you using? Chrome What operating system are you using? StackBlitz Reproduction URL https://stackblitz.com/edit/vitejs-vite-bhcbjy?file=vite.config.js&terminal=dev A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a _minimal_ reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways. A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves. Describe your issue [code block]

Error Output

error when starting dev server:

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
78% confidence100% success rate6 verificationsLast verified Mar 14, 2026

Solution: v4 alpha does not work on Stackblitz

Low Risk

In v3, we used to share a stackblitz to our users to reproduce bugs easily. We provide a tailwind based design system with custom themes (we reset some namespaces, such as colors, spacing, etc with our own semantic). This is no longer possible with v4 unless tailwind support WASM like @laktek said above.

78

Trust Score

6 verifications

100% success
  1. 1

    In v3, we used to share a stackblitz to our users to reproduce bugs easily. We p

    In v3, we used to share a stackblitz to our users to reproduce bugs easily. We provide a tailwind based design system with custom themes (we reset some namespaces, such as colors, spacing, etc with our own semantic). This is no longer possible with v4 unless tailwind support WASM like @laktek said above.

Validation

Resolved in tailwindlabs/tailwindcss GitHub issue #13133. Community reactions: 14 upvotes.

Verification Summary

Worked: 6
Partial: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

tailwindcsscssv4