[Bug] Tailwind doesn't install correctly in React Vite app

[lmdevv]

What is the problem?

So I tried installing React + Tailwind, but I get this error, I believe it has something to do with version incompatibility, I typed go-blueprint create -a, I was using only the standard library, with no db and in advanced features I only have React + Tailwind, that's it. Here are the relevant logs

❯ go-blueprint create -a

...

Press y to confirm choice.

Installing create-vite (using cache if available)...

> npx
> "create-vite" frontend --template react-ts --prefer-offline --no-fund

│
◇  Scaffolding project in /home/a/documents/temp/go-blueprint/test/frontend...
│
└  Done. Now run:

  cd frontend
  npm install
  npm run dev

Installing Tailwind dependencies (using cache if available)...
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"^7.0.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.2.0 || ^6" from @tailwindcss/[email protected]
npm error node_modules/@tailwindcss/vite
npm error   @tailwindcss/vite@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/a/.npm/_logs/2025-07-22T21_55_30_653Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/a/.npm/_logs/2025-07-22T21_55_30_653Z-debug-0.log
2025/07/22 17:55:31 Problem creating files for project.
Error: failed to set up React project: failed to install Tailwind: exit status 1

Operating System

Linux Mint

Architecture Version (x86, x64, arm, etc)

x86

Steps to reproduce

I am in go 1.24.4, nodejs 24.4.1 and go-blueprint 0.10.11

Relevant log output

[Ujstor]

@lmdevv Try cleaning the npm cache using npm cache clean --force. This worked for me. There is a --prefer-offline flag that I need to remove — it's probably causing issues with Tailwind