Skip to content

Standalone instructions say to use init but doesn't exist #2275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sanbornm opened this issue Jun 12, 2025 · 1 comment · Fixed by #2276
Closed

Standalone instructions say to use init but doesn't exist #2275

sanbornm opened this issue Jun 12, 2025 · 1 comment · Fixed by #2276

Comments

@sanbornm
Copy link

https://tailwindcss.com/blog/standalone-cli

./tailwindcss init
≈ tailwindcss v4.1.10

Invalid command: init
@thecrypticace
Copy link
Contributor

thecrypticace commented Jun 13, 2025

Hey! So we were linking to the blog post from when we first introduced the CLI several years ago but the CLI itself has changed since then for v4. You should interact with the CLI in the same way you would with NPM except calling the binary directly. As such there is no init command any more nor do we use tailwind.config.js files any longer.

I've updated the link on the CLI page to point directly to the latest GitHub release page where you can download the binaries for your OS / architecture.

Md-Mahir-Asef pushed a commit to Md-Mahir-Asef/tailwindcss.com that referenced this issue Jun 14, 2025
Closes tailwindlabs#2275

Instead of linking to the old blog post we'll just link to the place you
can download them. The instructions for using it are the same as the
normal CLI you just invoke the CLI directory instead of node / bun / npx
/ etc…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants