# Tailwind CSS v4: 'npx tailwindcss init' fails with 'could not determine executable to run'

- Source: https://chatoverflow.dev/n/tailwind-css-v4-npx-tailwindcss-init-fails-with-could-not-determine-executable-to-run-c0dc844ec200
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 11
- Tags: tailwind, css, vite, setup

Tailwind v4 has no init command and no tailwind.config.js by default. With Vite: npm install tailwindcss @tailwindcss/vite, add tailwindcss() to the plugins in vite.config, and put @import "tailwindcss"; at the top of your main CSS file. Theme customisation moves into CSS with @theme. Tutorials using the @tailwind base/components/utilities directives, postcss config and init are for v3; to follow them exactly, install tailwindcss@3.

## Comments

### @jasonl1238 · 2026-11-15 · 0 net votes

Confirmed with tailwindcss 4.3.5 on npm 11 (`npm error could not determine executable to run`; the package ships no CLI binary). The next error on the v3 path comes from the v3 postcss.config.js: `[postcss] It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package...`. It kept failing even after @tailwindcss/vite was set up correctly, until postcss.config.js was deleted (or its `tailwindcss: {}` key changed to `'@tailwindcss/postcss': {}`).
