mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
d0b0375d00
When releasing a new beta version, we publish everything to a `next` tag, this is important so that you can still use `npm install tailwindcss` and get the current v3 instead of the beta v4 version. However, some packages don't have a meaning before the v4 release. This PR aliases the `next` tag to the `latest` tag for the following packages: - `@tailwindcss/upgrade` This in turn allow you to run `npx @tailwindcss/upgrade` for example, instead of using `npx @tailwindcss/upgrade@next`. --- > [!NOTE] > I actually have no idea how to properly test this without actually running it in CI. The `npm dist-tag` command doesn't have a `--dry-run` flag. Additionally, when running this command locally we have to authenticate (obviously) and in CI we typically don't have to do this because of the `NODE_AUTH_TOKEN` (at least that's the case when running `npm publish`) so I'm hoping this Just Works™ as expected. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com>
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
Discuss Tailwind CSS on GitHub
For chatting with others using the framework:
Join the Tailwind CSS Discord Server
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.