The Tailwind blog posted a post “Tailwind is joining Shopify”: the team is moving to Shopify. The discussion collected 1055 votes. I don’t mention the amount and terms of the deal - there is no reason for them, and there’s even less sense in coming up with numbers for a deal than for a benchmark.
The reaction in work chats is the same everywhere: “we’re sitting on this now, what should we do?” I answer in parts.
What costs you nothing
The code that is already in node_modules will not go anywhere. An open license is not revoked retroactively: released versions remain released, and if the new owner one day takes the project in the wrong direction, the community is left with a fork - a mechanic that has worked on the web more than once.
Your markup will not go anywhere either. Tailwind's value comes from habit: the classes are already written in thousands of your templates, and rewriting them is more expensive than surviving any change of ownership. No buyer comes and takes a line from you. class="flex items-center gap-2" —it's just text in your repository.
What to check this week
You need to look at what lives not on your disk, but on other people’s servers.
Paid team products. Component sets, login access, subscription conditions - this can be changed by one decision of the new owner. If you are tied to them, find out what you have downloaded locally and what is only available from your personal account, and download.
Versions. The exact version is in the manifest, the lock file is in the repository, the assembly in CI is installed strictly from the lock file. Hygiene for any occasion, but it’s in weeks like these that you can see who doesn’t have it.
Plugins and harness. Third-party plugins, presets, class generators around the framework live in separate repositories and individual people. A change in the owner of the kernel hits them earlier than the kernel itself: the first thing a single maintainer loses is the motivation to push for compatibility with someone else’s roadmap.
Repository activity. The only honest indicator available to you from the outside: the frequency of commits, the speed of response to issues, who closes them after the transaction. Set yourself a reminder every quarter - not to read the announcements, but to open the commit chart and the list of recent merges.
My reading: Absorbing a tool you use for free rarely breaks the build tomorrow. It changes the roadmap: the team has resources and, at the same time, other people’s priorities, and the next major release will also solve the tasks of the new owner. There is only one practical consequence for you - move to major versions without haste, after reading the list of changes and understanding whose task this release solves.
And separately. News of this size is a good reason to write down once how many critical dependencies you have, behind which there is one small team. Usually there are more of them than it seems from memory, and after such a revision, Tailwind turns out to be far from the worst line on the list.